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.
I have a five session project where four of the sessions were shot with the L-eXtreme filter and 1 with just UV/IR. My goal was to end up with three master lights: one for the UV/IR session done with Adaptive Airy Disk and two from the L-eXtreme sessions done with both extract Ha and extract OIII. I have everything neatly loaded into APP with channel/sessions assignments and "integrate per channel" selected, so I was expecting that APP would ask me which sessions I want the chosen algorithm to apply to. Instead it normalizes and integrates all of the channels with the chosen algorithm. So I end up with unwanted integrations of either my L-eXtreme sessions done with AAD or my UV/IR session done with extract Ha or OIII. I realize that changing the algorithm requires re-normalizing, but then I would have expected to have the option for the normalization to be done by channel also. It seems that I'm going to have to deselect lights appropriately for each pass rather than using multi-channel magic. Am I missing something?
No that works like intended, however is indeed not what you want. In your case you need different APP sessions to use the algorithm of your choice and then later register and normalize those results in 1 new session. Good one for me to ask Mabula about though, might be nice to make that easier if possible. The sessions are needed when you have different flats per session for instance, but for the same type of data.
