*** Please do not post license keys - please report any problems with licensing to 'admin' by private message ***
Please include the following details in any bug report:
* Version of SharpCap
* Camera and other hardware being user
* Operating system version
* Contents of the SharpCap log after the problem has occurred.
[If SharpCap crashes, please send the bug report when prompted instead of including the log]
those trails look like hot (or warm) pixels in the dark not quite matching those in the image frames and therefore leaving darker results which train as the mount drifts slightly.
The most common cause of this is sensor temperature being different between the darks and light frames (although other parameter changes can have the same effect - offset, gain,etc).
Dithering can help reduce this as the dithering movement spreads the problem signal around in a less noticeable way.
Using filters changes the light frames hot pixel values and cannot be correctly substract by the dark frame.
I've modified my masterdark by selecting pixel value ranges and reaffect manually new values. That's better with my 300 newtonian, not perfect, but totaly impossible with my apo.
Unfortunately I can't do dithrering with Sharpcap, because I use EQMOD pulseguiding mode.
Thank you for your reply, and thank for your great software.
When you are using dark subtraction in SharpCap, hot pixels are actually dealt with in a moderately sophisticated way. SharpCap will look at the statistics of the dark frame and calculate a hot pixel level that is (I think) six standard deviations above the mean of the dark frame pixel value. Any pixels above this value are flagged as hot. When a pixel is flagged as hot, SharpCap will take a value from a neighbouring pixel (of the same colour for colour cameras) rather than use the potentially incorrect information from the hot pixel.
Under normal circumstances, the approach above should deal well with hot pixels and with variations between the dark and light frames, but maybe it isn't your case.
