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.
Hi Mabula, APP always sets a Bin1x1 frame as integration reference after star analysis although there are better quality frames in the dataset but in Bin2x2. I then set the frame with the highest quality manually as register reference. The registration is started and when the registration goes through suddenly a different ref. frame is selected. It is then again the Ref. frame of the star analysis and registration starts again from the beginning.
I already tried to force a Bin2x2 reference frame by changing the camera name of the Bin1x1 images in the Fits header and deselecting the Same Camera & Optics. Unfortunately without success, APP selects again a new Ref. frame (the one from the star analysis) and starts the registration from the beginning.
Is it possible to change the behavior of APP in such a way that it is also retained when the reference frame is set manually?
I think it was true in earlier versions of APP.
With kind regards
Hi @minusman,
Indeed, older versions did not show this behaviour. The problem here is that APP then is not able to register all frames when you choose a bin2x2 frame in your dataset. Then it tries a better frame and automatically it chooses a bin1x1 and then all frames get registered I assume?
So after a first registration iteration on your manually chosen reference, APP can not register all frames apparently... and then new behaviour kicks in, where APP tries to find another reference frame on which all frames can be registered.
The question which is most important here is, is the result then not okay with the newly chosen reference? I would think it will make little difference or does it? The field of view will have the image scale of the bin1x1 frames, which is what you want to not lose resolution and the rotation of the field of view can be manipulatied with the options below the register button in 4) Register. So you could rotate 180 degrees to compensate for a pier flip for instance.
Mabula
Hello Mabula, okay then the behavior of APP makes sense. Why I want to get a Bin 2x2 image as reference, because the images taken in Bin 1x1 are unfortunately not the best in the whole dataset. Guiding error and moon phase(half moon). But I did not want to discard the Bin 1 images completely, because a Complete night.
If there is the possibility after the register, so assign a new referenze to normalize. So that later the locale normalization can better adjust the qualitatively worse frames in relation to the qualitatively best frame. If the local normalization works like this.
