The Astro Pixel Processor Team (Mabula, Vincent & Wouter) wishes you all a very Merry Christmas and a Happy 2021 !!!
The Elephant Trunk Nebula in Hubble palette by Mabula Haverkamp. Takahashi TSA102 @ F/5.6 on an Avalon Linear mount using an asi1600mmc with Astrodon 3nm Ha, SII, OIII filters. Data processed 100% in APP using the soon to be released version 1.083 which will include... a new Star Reducer Tool.
Integration result all black
Hi, i proceded like the same way i used in other shot, loading light, dark, flat, dark flat and bias frames, all settings by defualt, but the final result is a black frame.
That not happening if i uncheck the "neutralize background" in the 5 step (but the result have color and luminance wrong).
I'm also not expert but it sounds like you do not combine. I apologise if I misunderstood you.
Integration result is gray you need to go Tools tab and select Combine RGB. Choose combining style HSO or SHO or LRGB etc then click on "Add Channel". It will open the folder, where integrated files stored. Select Ha-SII-OII or L-R-G-B (whatever) files then click on re-calculate. Colored frame will come. Continiue processing.
the result frame is not BW but is black, no one star and not the nebula image, only black.
If i not add the dark frame (only for test) that not happen.
Do you use some kind of multi-small band filter like L-Extreme? With OSC, (L)RGB or single small band filters like OIII and Ha this shouldn't happen. What camera are you using? How did you take dark, flat and dark flat or bias frames?
Did you ever find a solution for this? I've just had it happen to me too.
Long time user of the software, so I'm quite certain it's not my data. But I did check. No luck, it all looks good.
I did just upgrade to Mac OS to Big Sur. Maybe just coincidence.
What APP version are you using? APP does seem to work on Big Sur (as many now have confirmed) but may still have an issue with somewhat older versions.
1.083 beta 1
i use ASI294MCPRO, and L-enhance filter, i took all calibration frame, like the previuos time on another subject but whitout problems.
I haven't had a chance to try again yet due to the cloudy sky
Like you, the problem seems to be something with the MasterDark. When I leave it out, the image processes just fine. Add it and it goes BLACK.
The MD seems fine to me, but I'll replace it with a different one and see if there is a different result. Maybe it's the file? Would be odd, since this the same MD I've used before...but perhaps it's corrupt somehow.
No change, still black. I'm going to roll back to 1.082 and see if it makes any difference.
This could definitely be an issue with the dark, are your offsets > 0, just as a quick check? Sometimes if there is a tiny bit of light pollution in it, it can also cause all kinds of issues.
I've had the same bug in the past - sometimes I also get an all blue frame.
I've stopped trusting the automatic master frames and always add my own for each run and it seems to work fine.
The MD is quite blue, but I didn't realize how much until I stretched it. Quite likely the problem. I'll make a new one.
I tried with the old frames (august 2020), light, dark, flat, dark flat and all work fine. All default settings.
If i take new dark, at the same exposure time and sensor temperature, the process fails and the final image is black.
It is an odd problem. The MD that has given me issues now, is the same one that I've used since April. That is why I thought it was software related.
After taking new darks, the problem has gone away. I cannot explain it. At least now I know what to check if it happens again.
Very strange indeed. What has changed in the mean time? Did you use different software to take the images in August than now? Was there a driver update in the mean time? Anything else that you can think of?
I use ASI Studio to take the image and precisely ASIImg and ASI294MC PRO camera, the software package is been updated from 1.2.0 to 1.2.1 version at the 18 september 2020, is it possible that this creates this problem?
I am inclined to answer that question with "no" but honestly I am not sure anymore. Perhaps ASI Studio now introduces a different offset for dark or bias frames which causes the problem. I am not familiar with the software so this is a blind guess. Can you check the FITS headers of your images and verify that the offset and other settings (gain etc) are the same in all images?
Difficult to know, but it could definitely be the issue. I've seen more issues with special photo-taking software before, some seem to not follow the standard FITS rules or miss a FITS header that APP needs etc.