I tried to convert some image to RGB. That didn’t work in the latest beta but I’m not familiar with Siril. I selected tab conversion and checked option Debayer. The output files are smaller then original. They should be larger.
False alarm. I found the problem. The resulting files where compressed. When opening them in SIRIL only the red channel tab is selected. As soon you click on RGB tab all the colours are fine. The KEYWORDS all interpreted as expected.
Surprise, program AstroImageJ is also storing and reading the FITS header in TIFF. They are using key 50389. Maybe I can convince them to implement the Astro-TIFF specification using ImageDescribtion key 270. That should be a minor mod for them.
AstroImageJ can not read compressed FITS files.
Currently I’m discussing debayering with the main programmer of AstroImageJ. So I’m testing debayering again.
Looking in my collection of FITS files downloaded from nova.astrometry.net (few hunderd files), I found only two files with an XBAYROFF=1 There where many more with XBAYROFF=0. These two where created by SharpCap.
The brightest star in the file linked should be pretty red. Strange enough Pixinsight and Siril make the sky purple. ASTAP and CCDCiel make a greenish sky. So there is a different interpretation!
I found the problem. Sharpcap writes the BAYERPAT with extra spaces at the end. ASTAP didn’t interpretate that correctly. This will be fixed. Now all program show the purple sky so are debayering exactly the same.
For CCDCiel it was difficult to see due to an automatic colour balance and I assume it is working correctly.
So false alarm. Sorry for that.
I noticed that Siril always starts displaying a colour fits in tab Red after startup. Not in tab RGB. Is this intentional? I would expect if naxis3=3 it would display in RGB automatically after startup or just saves the tab position for next run.