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,
when calibrating my files I encounter an error message;
encountered error in module:
NormalizeCFAChannel
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)
Â
Ive not had this before - can anyone help please? I have used a program called Digicam Control to capture the images which is a new process although I have downloaded the files to APP directly from my cameras as usual?
Â
thanks
Richie
Â
Â
There seem to be a few bugs in the normalization routine, Mabula is aware of it and is looking at it carefully for the next version (@Mabula-admin).
Hi Vincent,
Thanks for the reply.
Â
Im just in the middle of rerunning APP and I think I've sussed out the problem.
I did a couple of test pics using a higher ISO than my others and Ive left a couple of the higher ISO ones in. Coupled with one dodgy bias frame it seems that this was the problem. It completely throws APP out.
I will repost in a bit if the process works! Fingers crossed.
That is very interesting, if it turns out to be data related (e.g. the bias frame) it can be very valuable for Mabula to see why it throws APP out and find the bug easily. If you find out, please let Mabula know and upload it to mabula@astropixelprocessor.com with a bit of background as to how you got there. Much appreciated!
UPDATE - the process worked perfectly so it seems that the fact I had some dodgy data in there produced the error message. I had some over zealous Light frames and a stray Bias frame in the mix. When I removed them the process worked flawlessly so hopefully others can benefit from the info. Mabula, hope you pick this up to. Cheers all.
