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 team,
Loaded all my lights, darks, flats & dark flats as usual but for some reason whenever I reach step 5 it crashes and I get this message.
Encountered error in module: CalculateScaleInCropworker
Error Message
java.lang.NullpointerException
Cause:
null
s.a(unknown Source)
s.doInBackground (unknownSource)
javax.swing.Swingworker$1.call(swingworker.java.295)
java.util.concurrent.FutureTask.run(FutureTask.java:266)
I've run this four times on two different machines (macs) with the latest version of the App installed.
Very frustrating, can you help?
cheers
Andy
Sorry for the inconvenience. What APP version are you using?
@vincent-mod
Hi Vincent, as stated in my op, I’m using the latest version App 1.075
cheers
Ah right, I overlooked the "latest version" part. What I notice is that many crashes seem to be related to the data itself. Could you perhaps try this again without calibration data? And then add them separately to see which data is causing it? I can then ask you to upload that and will pass it on to Mabula.
Ok, took a while to get it done but it eventually worked. Seems a master dark flat was the issue. Good call to work through it that way. Thanks!
Superb! I think this is the cause many times, it would be nice if APP could somehow recognize this better, but at least you got it sorted. Interesting to know if you saw anything weird with that frame?
