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.
Hello,
I'm a bit confused about (batch) crop.
First, I load a FITS image into the tool and crop it. I then get a FITS file that matches the crop I made... provided it is reloaded back into APP.
If I load the same 'cropped' image into another software such as SIRIL or SetiAstroSuite, etc., then I'm back with the original larger file!
Why is that? Did APP simply modify a viewport specification in the fits header so that it now displays and works with the reduced extent?
Gil
Hi Gil
In PixInsight I have the crop. Are you sure, you load the correct file into SIRIL ?
The cropped version has the letters „….crop.fits“ at the end?
Best regards.
Michael
Hi Michael,
Very good point. I don't have PixInsight so you may be right on that. Do you have Siril? Do you have SetiAstroSuite?
Point well taken, Michael.
I went back and redid the flow and... there is NO PROBLEM with APP. The crop is reflected correctly in Siril etc.
I know I renamed some files: the problem is surely behind the screen or the keyboard, as they say...
Thanks for righting me. I'll be more careful, next time.
Cheers
G
No problem @museceleste, glad that the issue is solved 🙂 !
Thanks Michael for helping out here @michaelacg !
Mabula
