Mar 28 2026 APP 2.0.0-beta40 will be released in 7 days.
It did take a long time to have the work finished on this and it will have a major performance boost of 30-50% over 2.0.0-beta39 from calibration to integration. We extensively optimized many critical parts of APP. All has been tested to guarantee correct optimizations. Drizzle and image resampling is much faster for instance, those modules have been completely rewritten. Much less memory usage. LNC 2.0 will be released which works much better and faster than LNC in it's current state. And more, all will be added to the release notes in the coming weeks...
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.
Two questions regarding combining OSC images shot with different filters (say, none/RGB and HaO3 for a RGBHOO)
1) is it better to do that with registered or normalized stacks?
2) For HaO3, does it make a difference to run "HaO3 color" and on import into RGB Combine assign R to Ha and G/B to O3, vs running "HaO3 extract Ha" and "HaO3 extract O3" separately and importing separately?
Similarly, is it better to save R, G, B channels separately and import one by one or just import the RGB image and assign R, G, B to those three channels?
TIA
Hi @heylers,
1) I would advise to both reigster and normalize the RGB and HaO3 stacks before loading them into RGB Combine to make them fully compatible
2) That should not be different in both cases 😉 ,the result should be the same.
Mabula
