June 24 2026 APP 2.0.0-beta46 has been released !
Improved internal memory configuration (lower ! memory usage), fixed beta45 startup issue, fixed Set Save Directory & 2-panel mosaics.
May 27 2026 APP 2.0.0-beta45 has been released !
Fully Multi-Threaded LNC, many improvements for the registration engine, platform upgrade, and further tuning of internal memory consumption and memory release back to OS.
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.
Just trying to get my head round a suitable workflow for the following data set:
Data recorded on two separate nights:
- First night was RGB using an OSC camera.
- Second night was H-alpha using same OSC camera.
Would I load all data and step through to Register and then save registered frames and open the registered frames from the two data sets separately to integrate using the appropriate Debayer method? Is there a different/better way of doing this in a single process with both data sets loaded - I couldn't find a way to select two different Debayer algorithms to enable this to work?
Thanks,
Dan
Hi Dan, apologies for the delay, both me and Mabula had super busy weeks.
You can process the H-alpha on its own and go all the way to the end result, then doing the same for the OSC data and load the resulting final stacks back into APP and register them together (with selecting the multiple-filter option to let APP know which is the H-alpha data). This can then be blended in with the combine tool.
