Hi,
I think that is down to PixInsight being 'helpful'. The 32 bit fits values go from -2 billion (ish) to +2 billion (ish). SharpCap only uses the positive range, so it kind of makes sense that PI is showing that as starting at 0.5, since it's halfway through the full range of pixel values available. If you open a 32 bit FITS from SharpCap in FitsLiberator, it doesn't show that behaviour - it just reads out the values as expected.
cheers,
Robin
Issue with FITS file generated during Live Stacking
Re: Issue with FITS file generated during Live Stacking
Thanks,
I really feel as a Dumbo right now, even my wife is laughing
I really feel as a Dumbo right now, even my wife is laughing