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.
This is the java crash
-----
Encountered error in module:
OverlapBetweenTwoImageObjectsCreatorWorker
Error message:
java.lang.ArrayIndexOutOfBoundsException: 1
Cause:
1
java.awt.image.ComponentSampleModel.getSampleDouble(ComponentSampleModel.java:872)
java.awt.image.Raster.getSampleDouble(Raster.java:1690)
G.a(Unknown Source)
G.doInBackground(Unknown Source)
--------
This happens in Step 5, Normalize, OpenGL 4 mode
In CPU mode there is a similar crash but with less info
----
Encountered error in module:
OverlapBetweenTwoImageObjectsCreatorWorker
Error message:
java.lang.ArrayIndexOutOfBoundsException
Cause:
null
no trace
-----
Thanks for posting the error, could you also provide more details on your system (OS etc), as well as your data workflow that led up to this error? What kind of data are you processing?
Apple Silicon MacBook Air with macOS Monterey 12.1. Both APP 1.083.1 and APP 1.083.2
Four images, one RGB with a Canon 1100d, One h-alpha, one OIII, one h-beta. The RGB one is calibrated, stacked and processed, the narrow band ones are calibrated and stacked.Finding stars works fine. Both setting the RGB and the h-alpha ones as reference frame produce the errors early in phase 4, I did not try the other ones.
The RGB image looks weird in registration mode, a parallelogram with very uneven height. The h-alpha as reference was less distorted.
Ah ok, so you're processing RGB with narrowband data. That is not possible, yet. What you want to do is to first extract the channels from the RGB data to R, G and B mono data. Then you can load those together with the other narrowband data. We do want to make this more obvious then just an error like this. 😉
