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, I have updated to the latest version and I have tried to load more data from another session, using the multi session process as normal but when I run the calibration session it crashes and closes? Ive restarted multiple times but the same keeps happening. Ive changed the target data and loaded other frames and it still crashes with no error message?? As always, these are NEF frames from a Nikon and Ive never had this problem before updating to the new version?
Regards
Richie
Hi Richie @richielisa,
On which operating system does this occur? On what hardware (CPU, memory, HDD) ? Please give as much details as you can.
How much memory is allocated to APP with the CFG button?
Maybe you can share the data on which this happens so we can have a look?
You can upload it here:
https://ariesprodstor.astropixelprocessor.com:7001/
username & password : appuser
Make a folder with your name and let me know once uploaded 😉
Mabula
Hi,
its on Windows 10 and Ive tried to use the internal Hard drive and an external one. If I only use 1 lot of data it seems to be fine but multiple sessions aren't working as normal for me. 6GB of Ram is used on CFG. APP closes abruptly and I cant even see open the file with any of my applications for some reason?
Hi Richard @richielisa,
So if you load only 1 session it works okay?
The behaviour sounds like a fatal crash when one of the NEFs is being loaded. Could it be that one of the NEF frames is damaged?
I guess it crashes each time when you load a certain set of NEF frames, right? One of those NEFs might be bad... do upload them as I suggested if you want me to have a look.
Mabula
Hi Mabula, yes, always the same point by the looks of things.
I will upload all the files if I can. Theres a few!
Regards
Rich
Should be uploaded now Mabula.
Dear Richard @richielisa,
Thank you very much for uploading 😉 As I suspected, one of your NEF frames is corrupt. It's this one: \Bode Galaxy\Bode Session 2\Darks\DSC_4188.nef
Just by looking at the file size relative to the other NEF frames, you will see that something is not right.
APP should not fatally crash in this case, so I am fixing this problem now so APP will report next time that such a file is corrupt. I will try to release a fixed version as soon as possible 😉
Mabula
Hi Mabula,
I removed the file and ran APP again but its crashed again?
Regards
Richie
Hi Richard @richielisa,
Probably there are more corrupt files?
The console panel is showing on which frame it fails. But there is a lot of information there so you need to study it a little bit.
I have checked all your data now and found these 2 frames to be bad/corrupt, both are darks:
\Bode Galaxy\Bode Session 1\Darks\DSC_4079.nef
\Bode Galaxy\Bode Session 2\Darks\DSC_4188.nef
The rest of the frames seem fine 😉
Mabula
Hi Mabula,
That seems to have sorted it. Im passed the calibration stage, where it was failing before.
Not being computer savvy I couldnt see what was wrong with those files. If its possible could APP have something built in that would identify corrupt files so tgey can be removed. It would save hours of frustration.
Thanks again mate.
Regards
Richie
Hi Mabula,
That seems to have sorted it. Im passed the calibration stage, where it was failing before.
Not being computer savvy I couldnt see what was wrong with those files. If its possible could APP have something built in that would identify corrupt files so tgey can be removed. It would save hours of frustration.
Thanks again mate.
Regards
Richie
Yes Richie,
I have already fixed it ;-), the next APP version will detect the corruption and will tell you which frame(s) are not good. It will not crash anymore.
Mabula
You are a star mate. Thanks!
