For quite some time I've used the combination of CCDStack and PixInsight. I do basic initial processing in CCDStack where I find it easier, then DBE, calibration and other processing in PixInsight.
For some reason all of a sudden any LRGB .FIT files from CCStack I load in PixInsight are coming up "blank" - like a photoshop file when it's transparent. See first attached image.
If I do a STF, it shows as per the second attachment. In this you can see a small amount of the detail of the image.
In CCDStack it shows as per the third attachment.
Any ideas what's changed? I'm quite sure there's not been any CCDStack update, but there have been PixInsight updates. But I'm not sure if some setting has reverted in one program or the other?
If I persist with the files in PixInsight I end up with issues, and nothing in the files when they are saved etc.
What first pops into my head is, what bit depth are you saving them from CCD Stack? I know that if I save a file from Maxim DL in 32-bit, PixInsight really doesn't like it. Same goes the other way too! When transferring between PI and Maxim I can only work in 16-bit.
Check the compatability of your output file in CCDStack to ensure it matches PixInsight as I believe they have moved to a new format although they say FITS is still supported, or something like that . It was a while ago that I seen this pop up on my screen.
The FITS standard doesn't specify the range of values that should be used for floating point values. PixInsight uses the range 0..1 and from memory CCDStack uses something like 0..65535. By default, PI will normally rescale data from a CCDStack file and do something sensible with it - at least that's always been my experience. Check your FITS file preferences in PI (Format Explorer>FITS>Edit Preferences.) If you change the "How to proceed" setting to "Ask on out of range read values" then PI will tell you the range of data values when you open a file that doesn't match the PI convention. The "Action" setting should be to "Rescale image on out-of-range" values.
I don't believe that this behaviour has changed in PI recently. It's very fundamental stuff. Most likely is that your FITS preferences have changed.
FITS loading transparent/checkboard in PI
