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 - probably doing something wrong here but I can't get past Normalisation when trying to work with data shot with an OSC and Mono (using latest 1.083.3 stable release). I've split the OSC data into separate RGB channels and then load these as separate session from the RGB data captured with my mono camera. I've selected its not the same camera/optics but regardless whether I chose Normal or Mosaic registration when it gets to Normalisation it fails. One set of data was shot at 510mm FL and the other at 410mm FL so not extermely different. Latest error is:
Encountered error in module:
ImageNormalizer
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)
Any ideas? Am I doing something that is not possible?
Yep, this is due to APP not being able to process both mono and RGB at the same time. We are going to make this possible. Would indeed be nice if this was more obvious instead of giving an error. Anyway, you can combine them, but you need to first create mono R, G and B files using the "split channels" option in tab 2.
Hi Vincent - thanks for the quick reply but as stated I did split the channels in tab 2. I then loaded these as R,G and B as session 1 and then loaded R, G and B as session 2 from my mono camera.
Solved it - I had the Force Bayer checked on the 0 tab. AFter switching that off all went through. Maybe something to add a check for in future rather than crashing. Thanks anyway.
Woops, I totally skipped over that you already did that. Must be because this is such a re-occurring question. Apologies. 🙂
