I was reading from the beginning of this chat and saw where you thought you had a memory leak problem with deep sky stacker and your images.
do you know if this issue has been resolved in DSS?
you also mentioned a jumper you had to put in to fix a power up issue on the camera.
Do you know if this Has this been “fixed”in the newer release cameras?
One other item , in reading through your comments you mentioned Dr Qiu
“He also suggested that a luminance filter might be needed since the QHY247C does not contain its own IR cut filter.”
so are you using a filter all the time to help with the color balance?
Sorry for the delay. Not sure why I missed your posts here. First off, thanks for the comments on the website and observatory. As far as the gain setting, while I haven't had the chance to go through a full image process since I switched (been working on observatory automation and am way behind on the little bit of content I have actually been able to capture), the whole point of these new cameras is that they're supposed to be extremely low noise so that you can run them at high gain without a problem. The issue with all of my low gain work was that I had to stretch them so much I still ended up with a lot of noise that was hard to get rid of. I'm hoping operating at a higher gain will improve that. The only issue is that I am up against stars and galaxy cores, etc. being blown out. I could wish that the 247C sensor had deeper well depth.
As far as DSS, recently the project was taken over (and I think made public domain) so we finally have a new V4.x in both 32 and 64 bit. I haven't used it much, but that appears to have addressed the memory problems.
I would certainly suggest contacting QHYCCD to confirm that the USB startup problem has been fixed. One would assume it has, but since I seem to recall you didn't get yours brand new, you might want to check what serial number, etc. has the fix. Of course if you never go fully automated, it might not bother you. The problem was if the USB was powered up before the camera hardware. Unplugging and replugging the USB is the basic fix that I'd originally worked around with a modified USB hub. I believe the internal jumper they had me add just holds the USB chip in reset until the 12V powers up, which would solve the problem as well.
And yes, I'm using an IR cut filter now (was using just a sky glow filter I had). I still have to be sure I turn my observatory cameras off as their IR led rings still will affect my background light pollution, but without the filter it was a mess. I'm rural enough that I'm not sure how much IR light pollution I get otherwise, and I'm using an SCT, so I shouldn't get much dispersion from any strong IR sources, although the EDGE does contain a lens at the back in addition to the corrector. I don't think the filter does anything for color balance, other than just ensuring I don't have IR (which depending on the filter material in the Bayer matrix might end up as colors other than red). For example, when I was testing the ASI290MC for my all-sky camera, it turned out that didn't have an IR filter either (check out the relative QE graphs -- all pixels are letting a lot of light through at 800 nm), making trees look REALLY funky! Since I wasn't able to get a full hemisphere FOV with that sensor it might not have mattered, but that was just one more problem...