Hi again,
Another interesting 'quirk' of the '183MC-Pro is the default (in camera) white balance settings.
There are 2 settings - WB_R and WB_B, which default to 52 and 95, respectively. WB_R is the RED balance, whilst WB_B is the BLUE balance.
With the default values in place, can anyone guess why all my images had a massive blue tint to them?
I've since dropped the WB_B value to 50, and the images look a lot, lot better. I saw a forum post that gave some reasonable values for WB_R and WB_B which I will post below.
Of course, your software may be over-riding this setting, so if you are not getting horrible blue images, then you can ignore this update!
Cheers,
V
Quote:
The reason for this question is info I found in 'Bernd Landmann: Guide to Preprocessing of Raw Data with PixInsight (revised on September 18, 2022)':
If you use an OSC camera of make ZWO, caution is advised when the 'native' camera driver is used: the ZWO Software Development Kit (SDK) enables the user in the image acquisition software to control settings that influence the white balance of a displayed color image. This is achieved by two parameters, WB_R and WB_B, data range 1 to 100, the default values are WB_R = 52 and WB_B = 95. The intensities of the red channel will be multiplied by WB_R/50 and the intensities of the blue channel by WB_B/50. Unfortunately the results of this multiplication are also written to disk in the FITS file. So it is important to set the values of both parameters to 50 and subsequently apply 'Save Config'; only in this way, the real raw intensities will be saved to disk in the FITS files, see [5]. Since the data coming from the camera are saved in FITS files which usually have the data format '16-bit integer', otherwise rounding errors and clipping of high values will arise. Such a complication is generally avoided when the ASCOM camera driver is used instead of the 'native' camera driver.
|