ASSUME will make an ASS of U and ME! The baddie in Under Siege 2 puts it better but I cannot write that in a public forum.However, I assumed(never assume.....) that there would probably be a manufacturers preferred matrix that utilised the sensor the best?
There is no preferred matrix. The sensor manufacturer dictates how the grid is layed out. Different camera models from the same vendor will vary as the sensors change. Camera vendor info is not important - what matters is how the processing software reads the matrix (ROW-order).
I come across many different makes/models of camera for testing and helping people at the local astro club. What works for me is Auto i.e. never force the pattern & let the capture and processing software handle everything.I have been forcing mine to be RGGB, so what should be the best approach ?
The example below shows the capture & process of Jupiter using a ZWO ASI120MC. Captured as SER at RAW8. Throughout the capture and processing I never once thought about what the Bayer pattern is.
- Capture.JPG (73.54 KiB) Viewed 686 times
Playback the SER file in SER Player (from the PIP website). Note the GRBG at bottom right.
- SER_Player.JPG (29.39 KiB) Viewed 686 times
Drag and drop the SER file onto the Open button in Autostakkert. Note that Colour is set to Auto Detect (by default) and GRGB is detected.
- AS-1.JPG (80.61 KiB) Viewed 686 times
- AS-2.JPG (51.88 KiB) Viewed 686 times
Load into Registax 6. The green cast can be sorted using RGB Balance and Auto Balance.
- RS-1.JPG (50.49 KiB) Viewed 686 times
- RS-2.JPG (45.5 KiB) Viewed 686 times
Maybe this will help clarify for you. Give the easy route a try and see what happens.
The image is poor because Jupiter was at 15° for me last year.
The only time I have ever had to be concerned about the Bayer pattern was when I had some FITS frames which had been captured by an ASCOM driver (that was with a ZWO ASI 2600MC camera) and because of the driver, no Bayer pattern had been written to the FITS headers.
Dave