2600MC and Pixinsight Integrated Color

jays_ct

All,
I apologize for what may appear to be a TOTALLY newbie question but has to do with the acquisition software I'm using on OSX and the initial color of an integrated 2600MC image after DeBayering, Registering, and Integration. I saw an older post (2020) about ROWORDER and processing a 2600MC image with a GRGB DeBayer pattern to get a green background integrated image. What I get now is a very blue background using AUTO or RGGB in PI. I wrote the program author and they indicate they're processing RGGB and ROWORDER (Top-Down) out of the FITS header correctly. I'm used to the green looking integrated image to begin processing (auto background elimination). Thanks!!

wvreeven

jays_ct It should be green and not blue so if GRGB works for you then stick to that.

jays_ct

I somewhat expected that it should be green.. Not doubting you, but is that what others experience as well?? Thank you for the quick reply..

Jay S.

wvreeven

jays_ct If it helps, I am one of the moderators of the AstroPixelProcessor forum and all OCS camera owners report that the unprocessed stacks look green.

jays_ct

Sorry to trouble you again on this. More and more I'm finding people who also have a blue background on a DeBayered, Registered and then integrated and stretched image. The default WB for the camera that seems to be the case is WB_R 52 and WB_B 95 ... These can be overwritten several ways to 50/50 (perhaps you have). But why is the default value so pushed to the blue side? Also, if pushing that Blue as much is there the potential for clipping and for negating the ability of the camera to grab other colors more readily, e.g. yellows? Is this a driver issue, native or otherwise? What should be the right WB values during capture if doing Deep Sky?

wvreeven

jays_ct With proper flats the integrated result should look green. With no flats the integrated result will look blue exactly because of the WB_B value of 95. However, both the lights and flats will have that and that should compensate. If it doesn't then the flats are not correct.

As to why the value is set to 95: only ZWO can tell because it is set in the driver. So far I haven't seen a proper explanation though.

jays_ct

?? Flats (I believe) are used for gradients, vignetting, and dust.. I've never heard of a flat being used to correct White Balance?? Is this something you've tried (serious question), both with and without flats on the 2600MC? Also, there has to be some reason why the 52/95 split on the defaults.. Something doesn't sound 100%.. Thanks

Jay S.

wvreeven

I image a lot with an ASI2600MC and always get a green cast, never a blue cast. And yes, I image with ASIAir Pro. I'll try to integrate some of my pics without flats and will post the result here.

jays_ct

Thanks

wvreeven

All my raw images look green despite WB_B = 0.95 and I cannot reproduce this. Not sure what's going on, sorry.

Kring

I just got a ASI2600MC (upgraded from 1600MM), I use PixInsight and have my workflow. Do you want to share one of your raw pics and I can see if my workflow results in blue or green cast? We've had really bad weather so I can't snap my own here in the north east US and doesn't look like it's clearing up anytime soon.

I do know that with PI - I've seen unusual things happen, in most cases it's because a setting was tweaked unknowingly. e.g. if you scroll your mouse wheel it's actually changing sliders/settings that you may not be paying attention to.. if you adjust some settings incorrectly it could produce radical outcomes.

wvreeven

I could give it a try with APP if you like as well.

jays_ct

wvreeven.. Are you using ASCOM? If so, it appears that ASCOM is changing the defaults from 95/52 to 50/50, or perhaps APT is also doing a low level reset of the WB_B and WB_R to 50/50.. What has come to light is that the default is 95/52.. Why is not clear as but at those levels clipping will occur and there is the "potential" for affecting other colors. If no other software, e.g. ASCOM, INDI, within Sharpcap (which has WB sliders) talks to the camera, it will be 95/52 and you will get Blue. In theory, you can subtract the Blue with PI and others, but the clipping will have already occurred..

wvreeven

jays_ct Are you using ASCOM?

Nope. There is no Windows in my home. I use Ekos and ASIAir Pro. With Ekos I indeed can set the white balance but not with ASIAir Pro. Images taken with the ASIAir Pro have a green cast and not a blue cast.

jays_ct

wvreven .. I would venture a guess then and say ASIAir Pro is setting to 50/50. I believe you can check or set in ASICAP.. Clearly you can set it in INDI Advance camera settings. That said, there have been any number of others I've addressed this with that get the Blue screen when the defaults of 52/95 are used.