Apr 9 2026 APP 2.0.0-beta40 has been released !
It has a major performance boost of 30-50% over 2.0.0-beta39 from calibration to integration, for mosaics even faster! 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. Improved Outlier Rejection with LN 2.0 rejection. macOS CMD+A works now in file chooser ! And more, all will be added to the release notes in the coming hours...
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.
I was creating some calibration masters earlier today when I discovered a bug that is reproducible. I loaded a set of files and produced a series of calibration masters with one type of flat. I then decided to create a different filter master flat. I pressed the 'Clear' button. I then tried to load the new flat frames. At this point, the APP window 'Gathering frame details' appeared, but it got stuck at 'Completed 1%'.
It did this every time I used it. Version 1.054 did not do this to my recollection. It was a bit of a nuisance, since I had to shutdown and startup APP to produce each new Master Flat frame.
Any ideas?
Hi Steve,
Thank you for sharing, I wasn't aware of this. I'll try to duplicate it and fix it.
You can trigger this problem each time?
Mabula
Yes. It does it 100% of the time (for me anyway).
Thank Steve,
Going to fix it 😉
Mabula
Hi Steve,
I have just tried, can't seem to trigger the error here yet.
Does it also happen with only 5 frames for instance? Maybe it has to do with the amount of frames in the file list.
The , " but it got stuck at 'Completed 1%" does indicate where the problem is.
It would help as well if you can post the console output when the problem occurs.
The frame list panel is updated after calibration, and for some reason a boolean value isn't switched and the new frame list updater is waiting for an old one to finish it seems.
Update: yes, this is synchronization issue, think I have found the problem..
Mabula
