June 24 2026 APP 2.0.0-beta46 has been released !
Improved internal memory configuration (lower ! memory usage), fixed beta45 startup issue, fixed Set Save Directory & 2-panel mosaics.
May 27 2026 APP 2.0.0-beta45 has been released !
Fully Multi-Threaded LNC, many improvements for the registration engine, platform upgrade, and further tuning of internal memory consumption and memory release back to OS.
Apr 14 2026: Google Pay, Apple Pay & WeChat Pay added as payment options
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 - probably doing something wrong here but I can't get past Normalisation when trying to work with data shot with an OSC and Mono (using latest 1.083.3 stable release). I've split the OSC data into separate RGB channels and then load these as separate session from the RGB data captured with my mono camera. I've selected its not the same camera/optics but regardless whether I chose Normal or Mosaic registration when it gets to Normalisation it fails. One set of data was shot at 510mm FL and the other at 410mm FL so not extermely different. Latest error is:
Encountered error in module:
ImageNormalizer
Error message:
java.lang.ArrayIndexOutOfBoundsException: 1
Cause:
1
n.a(Unknown Source)
n.doInBackground(Unknown Source)
javax.swing.SwingWorker$1.call(SwingWorker.java:295)
java.util.concurrent.FutureTask.run(FutureTask.java:266)
Any ideas? Am I doing something that is not possible?
Yep, this is due to APP not being able to process both mono and RGB at the same time. We are going to make this possible. Would indeed be nice if this was more obvious instead of giving an error. Anyway, you can combine them, but you need to first create mono R, G and B files using the "split channels" option in tab 2.
Hi Vincent - thanks for the quick reply but as stated I did split the channels in tab 2. I then loaded these as R,G and B as session 1 and then loaded R, G and B as session 2 from my mono camera.
Solved it - I had the Force Bayer checked on the 0 tab. AFter switching that off all went through. Maybe something to add a check for in future rather than crashing. Thanks anyway.
Woops, I totally skipped over that you already did that. Must be because this is such a re-occurring question. Apologies. 🙂
