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.
Mabula,
Â
If you had multi nights of data and from 2 different scopes, how would you suggest stacking them into one integration?
Â
a) Stack each session and create masters, then stack the masters?
b) Save all the calibrated light frames for each session and stack into one integration?
Â
if (a), what do you suggest for integration settings if you had 8 sessions total? Â
if (b) what do you suggest for rejection criteria i.e. adaptive? And, do you pick to stack, say, 50% or 75% of the best frames?
Â
Regards,
Bill
Â
Hi Bill,
What I would do in such a case, would depend on the amount of data basically. If the data of each scope comprises, say, 800 subs or so. I would opt for making masters of those first and then combine it with the second setup. Which would be your a-case. In that case I would load all sessions (given each session has its own calibration data) for 1 scope and use the standard settings APP already has, but with MBB and LNC switched on as it's expected that the background/illumination will vary among sessions. Same for scope 2, then you clear all data and load in the masters for each scope as lights, without calibration data of course and integrate those.
In the b-case and loading everything at once, you make sure to switch off "same camera and optics" and integrate with standard settings as well. That should work fine, MBB and LNC on there as well and you could opt for stacking 90-95% of the frames. That percentage will depend on what you know about the data, do you expect a lot of bad frames due to tracking issues etc, then you could lower that etc.
Â
@vincent-mod  Thanks Vince!!
Â
One more question please.  what if I were to take the reference frame after running the normalized lights tab, and removed the light pollution from this light frame, then reloaded back into APP and set it back to reference.  Would LNC adjust the other light frames to match this light frame with removed gradient?Â
I don't think so necessarily. I would just either let APP choose the reference frame (which should be the best in terms of star shape and/or SNR) or you choose a good one, but LNC should then work just fine and with LP correction your result can then be very even in the background.