Quote:
Originally posted by Upp3rd0G
I assume you are talking about E12 and E22 errors, because an E32 errors flags the whole frame as erroneous.
|
At least Plextools use C2 info at the sample level. I don't remember if it's a special function for Plextools.
Quote:
Originally posted by BobHere
The hold interpolation is where there are 2 or more consecutive errored samples. In this case the last good value is held in subsequent samples up till and including the second last bad sample, the value for the last bad sample is the linear interpolation between the held value and first good value.
|
Example with the Yamaha CRW3200 EWK reading a damaged version (green) of a CDR (red) :
Zooming into the blue mark :
Quote:
Originally posted by BobHere
Most good high fidelity players actually reinterpolate hold interpolations using much more complex schemes to reduce the hash.
|
The Yamaha CDX860 (450 €, 1991) doesn't seem too complex :
Zooming
It is the same as the CD ROM drive, but the linear interpolation runs for 9 samples instead of 2.
I looked for a muted part in my current test files, but I didn't find any.
Quote:
Originally posted by Upp3rd0G
Assumption3 - let us use a simple majority voting logic to determine which value is correct. If the drive does not interpolate, the results would be 3 votes for 26 and 1 vote for everything else, thus the winner is 26 - the correct value. If the drive interpolates it will be 3 votes for 26 and 5 votes for 32. 32 wins - the wrong value.
|
That's what I wanted to say from the beginning, but I stand corrected.
Andre explained that such a case is very rare. In reality, the comparison are made in 15876 samples (27 sectors). In this range, when an error occur, it is caused by a place difficult to read. There will be likely many wrong samples because of this. The idea is that when the same range is re-read, there will be about the same amount of wrong samples, but not necessarily exactly at the same place. Some that were wrong the first time will be right, and some that were right will be wrong.
Re-reading, EAC will not keep
the sample coming more than 8 times, but the
15876 samples coming more than 8 times. This will only occur if the range is error free, exept in the rare case where only one or two samples are wrong.
That's why I think that the more is compared, the most secure is it.
Example : reading the whole track twice and comparing CRCs is a bit more secure that reading once in secure mode, because, everything else staying the same (no C2), more than 27 sectors are compared (the whole track indeed).