Mure Denoise

[rdryfoos]

I am getting weird readings when I try to use the darkbiasnoise estimator script.  It worked fine for the STT-8300 and Mure Denoise has been an integral part of my work flow.  However, when I try to use this noise estimator script on darks taken with my new ASI 1600mm cool camera-I get the same estimate for noise that I got for darks taken with STT-8300: 26.99, with an offset of 760.  When I try to use Muredenoise--it does not work--it actually makes the image worse- I set the gain at the gain derived using the FlarSNREistimator script.  I only use  Variance Scale of .6, so minimal effect, and still, it blows up the image.

My concern is how could 2 30 min darks from the STT-8300 have the same noise as 2 2min darks from the ASI 1600 cooled to -20.  There is no way the estimated noise should be identical in 2 wildly different cameras with very different exposure lengths.

I love Mure Denoise--but cannot use it now and I do not know why.  Any ideas?
Thanks,
rodd

[rdryfoos]

This is perplexing to me--won't mure denoise work with cmos?

[1DegreeN]

I've used MureDenoise with images from my QHY163M - same sensor as your ASI 1600 but different circuitry. DarkBiasNoise script yields temporal noise of e.g. 41 for 1 minute darks at -10. When you say that MureDenoise blows up the image - have you tried enabling 24 bit STF? I also found some of my RGB images posterized by MureDenoise but switching to 24 bit STF was the answer.

[rdryfoos]

I've used MureDenoise with images from my QHY163M - same sensor as your ASI 1600 but different circuitry. DarkBiasNoise script yields temporal noise of e.g. 41 for 1 minute darks at -10. When you say that MureDenoise blows up the image - have you tried enabling 24 bit STF? I also found some of my RGB images posterized by MureDenoise but switching to 24 bit STF was the answer.

I have not tried that.  I will have to fiddle.  Its weird though that I get the same noise estimate for both cameras, regargless of sub length.