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.
I'm wondering if I've missed a setting or processing step because when I try to open Light Pollution Correction I just get a blank white image.
System: Mac OS Catalina running APP 1.082 (same issue when trying a previous version)
Data: 144 light subs with usual calibration files over 3 sessions in HSO.
After integration (no problems) I combine the 3 channels into a colour hubble palette image and save the result. This works normally. The resultant file is 980MB.
When I then attempt LPC, the module starts, states it's neutralizing the background and then pops up a blank white image. This is the largest image I've generated and perhaps it is too big for the processing module? I've not run into this with other integrations that generate 750MB files however. I can open each uncombined channel result (327 MB) separately in the module with no problem - tough to see the gradients this way though.
Any advice much appreciated. Thank you.
James
It's marked as solved, is it indeed and could you tell what the solution was?
Of course:
In one of the three imaging sessions the OTA got rotated a little. APP had no problem with the integration but the borders were obviously mal-aligned for the "rotated" session. When entering the LPC module, the DPP auto stretch saw a fair bit of absolute black around the edges and I think the auto stretch drove the data to pure white. I discovered this by fiddling with the controls manually.
I went back and cropped the image to a perfect rectangle and everything worked perfectly! I guess there's a reason you put the crop tool above the LPC tool in the list 😉
Cheers
Ah, ok. 😉 Thanks for letting us know. I do think there might be a data issue though as there shouldn’t be regions that are completely black..
