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.
Why is APP analyzing frames for LNC when "No LNC" has been chosen? This takes a very long time. I can't remember this happening before.
Edit:
Even not directly related, this happened with the same dataset after I had saved the splitted and calibrated light files. I pressed Integrate to run the full process and the error occurred.
There after I realized that a process was running in the console window, looked like some form of calibration.Ā
I decided to shut APP down and start again.
It shouldn't indeed, is this happening all the time for you now?
@vincent-mod I'm not sure, but I think so. At least it has happened a couple of times. I have a huge stack processing right now that will probably take all night, but I'll keep an eye out for this.
@vincent-mod I can now confirm that this happens on every integration as the image shows.
When this integration finishes I will restart the computer and run a small test just to be sure that there is not some hick-up in the system somewhere.
Yes, it happens to me too...
Ā
Mmm, that is weird, thanks for notifying us I will pass this on to Mabula.
Ah wait, I think what the console mentions above is something else actually. LNC rejection parameters is different from the LNC normalization correction. That shouldn't take place when switched to "no LNC". I've asked Mabula for a bit of extra clarification.
And this is indeed the case. So Local Normalization Rejection, as the console mentions, is an outlier rejection algorithm (unique to APP). Local Normalization Correction is for correcting gradients. I agree, can be confusing as the names are very similar. š
Thanks for the clarification. Really got me confused at least. Is this new to 1.083? I can't remember seeing this before.Ā
It may just be my imagination, but has there been any other changes to the integration module lately? Especially on the part of the process where APP says Integrating pixels, and is counting. As I remember it, it used to be faster. But it is probably just me being impatient. 😀Ā
No it shouldn't be changed really. Maybe there is more output now in the console about it, in general the speed of APP has improved quite a bit since the previous versions. š
