Derek wrote:citguy wrote:Hi Paul. You can always use the corrected and uncorrected playback buttons to compare your processed and unprocessed tracks. I suspect you may have over processe a bit going for zero clicks. You know, one set of play back buttons plays only the current screen and the other set starts from the beginning of the track or tracks if "all tracks" are displayed below.
Stan
I would concur absolutely with this. It is not usually a good idea to keep reprocessing until the detected clicks drop to zero. This is because of the problem of 'false positives' The process of discriminating between clicks and music is never perfect and therefore, the more times you process, the more is the likelihood that you will pick up a lot of false positives. This may be what is causing the dull sound you are reporting.
I thionk the best approach is to process once and then to audition as citguy suggests. Only re-process if there are still audible clicks to be removed. And even then, it is better to remove them manually or to mark a block around them and use Block-SuperScan. That way it is only the region immediately around then rogue click that will be reprocessed.
Having said all that, another user has reported that he successfully does what you do but at detection threshold 2. If you do decide to do multiple superscans, then threshold 2 is to be preferred as the likelihood if false prositive is much reduced.
.
~~~~~~~~
Derek....let me clarify that a little. I scan first at a setting of 2. Then I audition and then superscan only if there are still audible clicks. After the first superscan I do the same again. I NEVER aim for 0 clicks, more in the region of fewer than 20 to 30, or so. My point was that I have never found it necessary to use a click detection setting higher than 2 to produce the desired result. The only filter I use is the rumble filter since I solved the hum problem at its source by proper grounding etc.