Hello everyone,
it is great to be able to come on the forum for my first time. Thanks.
I am having some strange colouration issues on my DSS stacked lights of certain objects. Just so you know, I use a Skywatcher 8" Quattro and a Canon 650D modified camera, a Hutech LSP filter and Baader coma corrector, all on a NEQ6 pro mount, and an Orion autoguider using PHD. I live in what I would call a pretty light polluted area.
Essentially what is happening is that I will take the stacked image into Pixinsight, perform DBE on it and create a workable file. But as soon as I do a STF stretch on it after this, I can see this weird colouration in the background. Also, these colourations still appear, when I start to do normal processing, [after finishing with DBE and having reset the screen functions]. If I do not do DBE however, it appears fine when stretched.
So, after DBE and resetting, when I up the histogram on it, midtones only, straight away the strange shades of coluration begin to appear in the background. I believe that the 0.25 figure under 'mean' on the statistics is the limit for an image, so as to keep one from overdoing the background, but even at half of this level, I can still see the shades coming through. The problem with dropping the midtones that far, it means that I am not able to treat the object itself with as much midtone as it really needs. I have tried masking it and everything, it seems.
And here is the odd thing about it. This has only occurred really, on globular star cluster images like M3, or on images with relatively small objects in the frame. It seems as though when there is lots of background and not so many stars, it mainly occurs - not so much with objects with lots of nebulosity or a large object like M31. So, my Rosette nebula was ok, comparatively. And the only way to get rid of the strange colouration is to pretty much clip the black point, in order to rid myself of the visual defects. By the way, how does one determine when a black point is clipped or not clipped?! I still really struggle with this....
![smile :)](http://pixinsight.com/forum/Smileys/default/smile.gif)
I was hoping to attach a M3 image here, which is a classic case in point, but I cannot do so due to file size restrictions. Besides one needs a tiff to be honest, to see the problem issue really appear because the jpeg compression loses a lot of it. As that is so I have sent you a screen shot so you can see it for yourself. Maybe I am doing DBE wrong, but that said all the RGB 'peaks' under the histogram all line up during processing, and what I do with DBE seems to work with other objects like the aforementioned M31.
Incidentally, I do not use dithering on my PHD Orion autoguider settings - would that help? If so, what would be a good setting; default on it is 1, but the range is up to 100. By the way I know there are a few dust bunnies on this image, but they make no difference to the issue anyway. I have since cleaned up the sensor. Maybe I was simply using too few flats and biases with these images anyway; which I have improved upon since with more recent objects?
I guess, whilst I am at it, I would like to ask whether a CCD camera would solve these issues, and because I do not want to lose any FOV, I will need a large chip. Which camera would someone recommend, a Starlight Xpress SX-814 Colour or SX 25c? Something cheaper would do!!!
![laughing :D](http://pixinsight.com/forum/Smileys/default/laughing.gif)
I know I have asked a lot here, and I really apologise, but I thank you so much for your time in advance.
Simon
UK