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 Mabula,
I was trying to process some O3 recording but i get every time the same "java" notification (see attacht files).
For these recoriding i was using the Zwo Asi 071mc-c.
This is wat i was doing:
First tab,
Set te bayer pattern to RGGB,
Check: Force CFA
Algorithm: Oxygen III
Then, Loaded about 20 files (6 files of 300 sec. and the rest of 600 sec)
Loaded only BPM and Master Bias.
Push then the calibrate, this is oke,
Push then the Analyse stars, this is also oke,
but when i try to register the files ik do get every time the Java notification.
Also the files wil not be registerd.
Am i doing something wrong?
Jan-Willem
Hi Jan-Willem,
Thank you for reporting this.
It's not a problem with the O3 debayer algorithm. It happens due to a problem in 3) star analysis. This problem has been solved in the upcoming version 1.056.
See here for details:
FIXED, registration, if star analysis only found very little stars in a frame (less than 12) a null pointer exception would be thrown in registration, due to a boolean that was not set in reporting back registration status internally. This is fixed, the null pointer exception/java error is gone. Was triggered by several users in version 1.055 due to the change in the detect above noise level kappa values and calculation of the dispersion of the data. Screenshot of the particular error that was triggered and a screenshot, in case of failed detection, showing that the user is warned now.
The attached screenhot shows the IB.a error, the same as you encounter.
The problem lies in the default detect above noise level: kappa value. In 1.056 this value will be set automatically to solve this inconvenience. For now, you will be able to solve this, by lowering the detect above noise level kappa value in 3) before starting star analysis. Make sure that enough stars are detected in star analysis before proceeding with registration. Enough would be to have at least 100 stars per frame detected.
Let me know if this solves it for now 😉
Kind regards,
Mabula
Hi Mabula,
Thanx for the explanation. I dit not know this was the problem. I will try it your way.
Kind regards,
Jan-Willem
