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.
Hi all,
I've switched from APT to NINA mostly for the automated focussing function. The issue I'm having is the way it references the bayer matrix and the havoc its wreaking with calibration and the colours from my ASI533 OSC not displaying correctly. I've tested the data in PixInsight and it debayers correctly so it appears its the way either NINA combined APP are processing the matrix.
Other than using PI (which I detest for everything except post processing) are there any suggestions for me to try?
Thanks
Gary.
@gary-neilsonicloud-com Hi Gary. Are you using calibration frames from APT with lights from NINA? If yes then that may very well be the issue and you may need to retake the calibration frames with NINA. If you already did do that then something else is going on. What Bayer info is stored in the fits headers of the NINA data?
@wvreeven Hi Wouter ..... I tried both flats from APT and NINA with the same outcome. I'll do some more darks and bias through NINA to see if it makes a difference. Great idea as it never occurred to me doh!
NINA properly gives RGGB in the camera tab and the header. There are also lines for X/Y bayer pattern offsets of 0/0 in the header. On the NINA forum there is some discussion of where the reference is written in NINA (top left writing down) and read (bottom left reading up) from imaging software. So it may get the pattern reversed?
I ran NINA subs last night with the RGGB expressed (rather than auto) but I doubt it will solve the problem. I'm wondering if faking the pattern in NINA to match the read reference in APP i.e change it in NINA to GBRG or something like that. I've tried forcing this in APP but it didn't correct the problem.
I may have been a bit harsh bashing Pix 😉 .... the program is great but the convenience of APP is wonderful. I still use Pix for the final tweaking of the image using its very powerful processes so the two apps compliment (at least for me) very well :).
So a couple of things to try then are new calibration frames and fiddling with the pattern definition. I'll report back.
Cheers
Gary
@gary-neilsonicloud-com Hi Gary, OK we will await the results of your tests then. Fingers crossed that it goes well now 🙂
@wvreeven turns out it was the other calibration frames causing the issues. Once I had a consistent set produced in NINA then APP processed everything just fine. Now I just have to rebuild all of my library!
@gary-neilsonicloud-com Good to know that you were able to solve the issue. Good luck rebuilding your library. Especially with darks that can be a very time consuming task!
