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.
The QHY163M drivers were updated and installed a second instance of the QHY-Cameras-Capture driver that now is called QHY-Cameras2st-Capture. This is the one that I need to use now for all captures, and it works fine for that.
However, I cannot use my previous master calibration frames that are header tagged with the old camera description. At least that's what I think is going on All of the exposure details are identical to the light frames, so I think that the header has to be the issue.
Is there a solution for this beyond having to generate an entire new calibration library?
Thank you,
Eric
The QHY163M drivers were updated and installed a second instance of the QHY-Cameras-Capture driver that now is called QHY-Cameras2st-Capture. This is the one that I need to use now for all captures, and it works fine for that.
However, I cannot use my previous master calibration frames that are header tagged with the old camera description. At least that's what I think is going on All of the exposure details are identical to the light frames, so I think that the header has to be the issue.
Is there a solution for this beyond having to generate an entire new calibration library?
Thank you,
Eric
Hi Eric (@flywaldo),
I assume the camera name is changed due ot the driver upgrade? Image dimensions haven't changed I hope?
You can use the Batch Modify tool in 9) to adjust your master frames. You need to change the instrument fits tag in the master frames.
- load the master frames to be adjusted.
- in the textfield to the right of instrument, fill in the new camera name exactly like in your new Fits frames.
- click on manipulate header, now the new masters are saved in your working directory.
Let me know if that solves it 😉
Mabula
Mabula
Thank you for the quick reply. After installing the latest version of APP this issue resolved itself. I can now use the old calibration frames with the new light frames.
And the new LN Windsor outlier rejection makes processing even faster, thank you!
How is progress looking on GPU support?
Clear skies,
Eric
Mabula
Thank you for the quick reply. After installing the latest version of APP this issue resolved itself. I can now use the old calibration frames with the new light frames.
And the new LN Windsor outlier rejection makes processing even faster, thank you!
How is progress looking on GPU support?
Clear skies,
Eric
Hi Eric @flywaldo,
You're most welcome 😉
GPU support is being investigated and I have run some tests already. It will take some time before having implemented it though due to a couple of higher priorities. Main priority for APP's next release is a complete upgrade of the calibration engine for instance.
Cheers,
Mabula
