UPDATE FROM MABULA
I have had a very rough 2 months unfortunately health wise. I was struck 3x in a row with bacterial infections. The second infection occurred  after a routine hospital checkup and I became very sick. I had to rest and take a lot of antibiotics. Once I was recovering and restarting work 1 month ago, I again became sick. The infection was not yet gone, so even more antibiotics and rest was needed. Needless to say, it took a lot of my energy and I needed a lot of rest.
Finally, the infection is really gone and my energy is coming back step-by-step now and I have started work again. I am terribly sorry to have kept you waiting for support. I will address all outstanding questions and e-mails step-by step and will be on the forum daily from today.
APP 2.0.0-beta47 will come soon as well, a lot of work was already completed before I became very ill, so the release is also nearly ready for you. Beta47 will be much faster actually. Many workflows will be more than 2x faster, mosaics can even be 10x faster than before because registration really received a major boost... all compared to beta46. Â Before I release it, I will make sure that everything is working properly and then I will release it.
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.
