MAY 4 2026: APP 2.0.0-beta44 has been released !
New improved internal memory controls should now work on all computers
May 1 2026: APP 2.0.0-beta43 has been released !
Improved internal memory controls (much more stable and faster on big datasets), fixed CPU image viewer, fixed Narrowband extraction demosaic algortihms.
Apr 29 2026 APP 2.0.0-beta42 has been released !
New improved Normalization engine, Fixed random crashes in integration, fixed RGB Combine & Calibrate Star Colors, fixed Narrowband extraction algorithms, new development platform with performance gains, bug fixes in the tools, etc...
Apr 14 2026: Google Pay, Apple Pay & WeChat Pay added as payment options
Update on the 2.0.0 release & the full manual
We are getting close to the 2.0.0 stable release and the full manual. The manual will soon become available on the website and also in PDF format. Both versions will be identical and once released, will start to follow the APP release cycle and thus will stay up-to-date to the latest APP version.
Once 2.0.0 is released, the price for APP will increase. Owner's license holders will not need to pay an upgrade fee to use 2.0.0, neither do Renter's license holders.
Hello
As part of the processing of RGB images, I integrated Blue 120s and 240s.
When I tried two methods, the attached image was displayed in B.
A: Six Blue120s light, 20 flats, 20 dark, 20 darkflat, 20 bias were integrated without multi -session processing. 20 dark and 20 darkflat of 120s were used. After the 120s light processing, six Blue240s light were integrated. 20 dark and 20 darkflat of 240s were used. I used 20 same flat and 20 same bias as 120S .
B: Using multi -session processing, I checked Blue120S Light in Session 1.
I checked light of Blue 240s in session 2.
I checked flats in session 1 and 2.
I checked dark of 120s in session 1, and dark of 240s in session 2.
I checked darkflat and bias in session 1 and 2.
I thought that if I separated the session, each session would be processed independently, but it seems different.
The strange thing is that when light are three in B, the attached image was not displayed.
Therefore, the processing was performed automatically until the end.
The APP version is 1.083.4 for Windows.
The tab setting is the initial value except for the attached images.
Different sessions are meant for the use of different calibration data you may have per session (usually flats). Looking at the above dialog it shows that you have a master darkflat of 120s exposure, that seems incorrect I think. Did you mix up a darkflat exposure with a dark?
@vincent-mod
Thank you for your answer.
I want to get a good understanding of multi-session processing, so I ask the following questions.
1. Does multi-session processing use session A's calibration file for session B? That is, for other than session A.
2. Can I specify the session to apply them when loading the calibration files on the LOAD tab?
That's all, thank you.
Hello
Interestingly, the A process doesn't show a popup.
Although the light frame and calibration frame are all the same as B.
@mo-mo Using the same flats in multiple sessions isn't working well in 1.083-4 and earlier versions. Please try 2.0.0-beta2 and see if it works there.
@momo: The straightest way to get rid of this error is to take new darkflats (basically Darks with 2.5s exposure). They'll correspond to the Flats just as the darks would correspond to the lights. Each pair requires same exposure / ISO and ideally same temperature (around2°C difference is OK for Darks, the margin is higher for darkflats)
cheers,
jochen
I understand that the same FLAT cannot be used in multiple sessions.
Until the Beta version is official, I'll work with Method A.
Thank you
