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.
Hello everyone,
thats my first post and error.
Since today I keep getting an error message.
I downloaded the latest version.
I load 284 Lights (CR2 format)
50 flats and 25 bias and dark flats.
It's only 1 session.
I don't understand the error. I restarted APP and also reloaded all data.
Can someone help me please?
okay...maybe it has something to do with the data I'm using.
I just loaded data from another galaxy and APP is working normally.
I would still like to know what the error is.
Can you test with the data again that causes the issue? We'll ask for that data if it indeed is the cause to determine the issue.
@vincent-mod
Hey Vincent,
i test it again with the same settings like the other Galaxy. The error comes again at picture 276.
I've attached the dump-consoleOutput.
Mm, I'm seeing a lot of processes that are getting cancelled and an issue with calibration data. Would the cancelling make sense? Are you doing this manually by any chance?
Scratch that, that's due to reprocessing data. It could be a bug in the hot column detection, would you mind uploading a set that generates the issue to our server?
@vincent-mod sure, i will do if i'am back at home.
I checked, that I can open every single Frame in APP without an issue. Before I upload the files I check the exact block it could be.
Thx for help! 👍
