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.
My system is just hanging trying to calibrate the BPM - see image. It seems to have created all of the Master files before crashing and is non-responsive to "cancel"
This is a 2 session integration:
- Session 1 is straight RGB - 1x1 @300sec.
- Session 2 is LRGB with L 1x1 @900sec and RGB at 2x2 @300sec.
For calibration I have
- Flats and Dark Flats for each set of lights
- Darks for 1x1 and 2x2
- A Bias file for each session
Any thoughts?
Thanks
Jon
Apologies, I posted this in the wrong section but don't seem to be able to move it.
I've had a similar problem. APP hangs at 90% when creating a new BPM. When I removed the request for a new BPM and used an old one everything worked ok. I was going to report this when I could isolate the actual conditions that caused it. However, I haven't been able to reproduce the problem but decided to post this information when I saw midnight_lightning's post. I know it occurred using multi session and multi channel. I kept more detail, including screen shots. However, I'm away from home for a week or so but will send them to you when I return.
Hi Jon @midnight_lightning and Tim @tim,
This is with APP 1.062 right?
I will have a close look at the module that is creating the final bad pixel map, in this case, it seems to wait for something before finalizing. I should be able to find the source of this issue.
Does it always occur if you follow the same routine?
Mabula
Hi, it's happened a couple of times but doesn't always happen, I haven't worked out what scenarios cause it so far - sorry.
Hi Jon @midnight_lightning,
I have corrected the code and thank you very much for bringing this to my attention.
The issue was a synchronization issue in a multi-threaded environment. The code has been adjusted and is now threadsafe. Issues like this are a bit complicated, since they only manifest themselves sometimes.
I will release APP 1.063 with this fix now as soon as possible 😉
Kind regards,
Mabula
Hi Jon @midnight_lightning,
I have corrected the code and thank you very much for bringing this to my attention.
The issue was a synchronization issue in a multi-threaded environment. The code has been adjusted and is now threadsafe. Issues like this are a bit complicated, since they only manifest themselves sometimes.
I will release APP 1.063 with this fix now as soon as possible 😉
Kind regards,
Mabula
And for Tim as well @tim,
I have fixed this problem and will release APP 1.063 with the fix as soon as possible.
Mabula
Thanks Mabula, looking forwards to processing these sessions again. 🙂
