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,
I wanted to integrate data from two different instruments. Different scopes and different cameras with different formats and resolutions. I followed a tutorial here:
However, when I came to the integration part I had this error message:
Encountered error in module:
Integrator
Error message:
java.lang.ArrayIndexOutOfBoundsException: Index 1 out of bounds for length 1
Cause:
Index 1 out of bounds for length 1
rD.a(Unknown Source)
rD.doInBackground(Unknown Source)
java.desktop/javax.swing.SwingWorker$1.call(Unknown Source)
java.base/java.util.concurrent.FutureTask.run(Unknown Source)
Â
I am running the 2.0.0 beta 6 version. According to the tutorial this integration should work, but it didn't.
However, the images were also of different types, one was OSC color, and the other was mono. Could it be that
this is the reason for the crash?
Regards
Ulf Granlund
Â
Â
Could you try to first separate the OSC data into mono channels? This can be done by selecting "split channels" in tab 2 (all the way down) and then save those. Load in the split frames as mono and add the other mono data and try again.
Hi, thanks, yes splitting the color image in channels does make it possible to integrate them separately, as well as the mono nb data. But the only way I can see to put it all toghether is to use RGB combination. This means that I can not get the advantages from a local normalization correction when integrating data from different instruments with different image sizes and orientation. The tutorial I mentioned show the great advantages of this. But it uses only color images. Is there a way to get local normalization while working with both color data and nb mono data from several different intstruments?
Â
And, secondly, while it may not be possible to integrate mixed types of data, I think APP should say this in some other way then the "Out of bounds" error. Â
You can actually, if you have all mono data you can load those in again as lights and just process all those together. Easiest is to have those calibrated first with their own calibration data (in the case of different sensors).
