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 Steven,
I notice you are trying to integrate JPG frames. APP currently can't do this. I haven't implemented this (yet).
I can implement this, but I must warn you that integrating JPG frames is probably something you don't want to do for several reasons. Most important reasons are
- data is compressed (so data is already lost before you start with anything)
- data is most likely not linear anymore.
I can implement the processing of JPG frames up until integration fairly quickly but I really don't suggest using it.
Is there a particular reason why you are trying to process JPGs instead of CR2s/NEFs/TIFFs/FITS ?
The time really depends on what you are trying to do (LNC or a mosaic can take a while) and possibly is related to APP not being able to process JPGs up unitl integration (yet).
Let me know and I'll help you out as good as I can 😉
Kind regards,
Mabula
I would really like to see JPG integration implemented for old data I want to process, taken with pre-RAW cameras. Besides the data we have to process should be allowed even if not ideal, this is the sort of approach we get from PI: being expected to do things "their way". sometimes we just dont have the luxury or capture data at an unepected opportunity so might not have the gear on hand to do everything "properly".
Hi Mabula ,
I had just tested my new samyang lens and thought i would give it a try with APP . Next time i will set my camera on RAW files !
On my pc it is standard RAW ..
Thnkx ,
Steven
I would really like to see JPG integration implemented for old data I want to process, taken with pre-RAW cameras. Besides the data we have to process should be allowed even if not ideal, this is the sort of approach we get from PI: being expected to do things "their way". sometimes we just dont have the luxury or capture data at an unepected opportunity so might not have the gear on hand to do everything "properly".
Hi Steve,
Yes, fair enough and I do agree with you, I will fix this 😉 it's not too hard too implement it actually.
Mabula
Hi Mabula ,
I had just tested my new samyang lens and thought i would give it a try with APP . Next time i will set my camera on RAW files !
On my pc it is standard RAW ..
Thnkx ,
Steven
Hi Steven,
No problem, I will fix the JPG integration, so it's possible just in case ;-), just like Steve argues.
Mabula

