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.
I've been attempting to run a multisession LRGB stack several times, without success.
I get as for as about 18% through normalisation then processing is halted my this:
Encountered error in module:
OverlapBetweenTwoImageObjectsCreatorWorker
Error message:
java.lang.ArrayIndexOutOfBoundsException
Cause:
null
no trace
Any clue to what went wrong?
Â
NB - My Luminance and RGB are of dissimilar camera and optics, but I've unchecked the option in registration and set normalization mode to advanced. The same as I always do when processing different image scales.
Â
Thanks
Please follow this to your workflow. I've just figure it that this is not working with an RGB image directly, but you have to split it to channels first.
Â
Â
Please follow this to your workflow. I've just figure it that this is not working with an RGB image directly, but you have to split it to channels first.
Â
Â
Excellent, thanks for that.👍
Any chance the developers could amend a future release to automatically check the "split channels" box when RGB is selected in the multichannel options list?
It would avoid further confusion.
Yes that would indeed be nice. The feature to make this simply possible will come however, if it is implemented that workflow will be a lot simpler. I don't have a specific ETA, but I do know it is on his shortlist.
