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.
hello,
Â
when combining data done with different focal lengths APP seem to keep the resolution of the shorter focal length. I thought when setting in "4" to the corresponding sub frame I could influence this. Tried and it did not work out
Â
so how can I achieve this: APP takes the resolution of the longer focal length thus less arcsec/pixels to the data instead of downsclaing these to the lower resolution of the shorter focal length stacks?
below you see a test combination where I combined Ha data with a 6200mm sensor of 3 different telescopes, focal length 400, 550 and 640 mm
e.
Â
Hi @elgol,
There are different factors involved that decide which reference frame would be chose automatically. In your case, you can simply set the reference before reigstration to one of the files with the highest resolution. Did you try this?
Mabula
@elgol, so then it should work fine, didn't it? The scale will be preserved of the reference frame if scale factor in 6) Integrate is set to 1.0.
Â
