F
filtersweep
New member
how come a miscalculation or a skipped one results in a "skip" on an audio cd, but could result in a completely corrupt directory structure or inaccessible files on a data cd, if it's all data?
How do you know it is not a surface defect?
All CD players have some error correction involved. This is not to fix 'errors' on the CD itself, but rather 'read errors'- since a CD basically streams the data off the CD (it may also use a buffer if it is 'skip proof') but the idea is to keep reading and reading no matter what happens- so it might interpolate a bit or two here and there, since it isn't going to just stop until it figures out what that bit it sorta read was, or it isn't going to replay that part to 'fix' its read error. Some CD players are simply sloppier than others. Some use oversampling where they basically read the same data a few times and compare the results. When you consider how cheaply most CD players are made, it is a wonder they aren't even sloppier.
On the flip side, even with a fast CD drive, you might install software at only 6 or 8X (that 54X is a theoretical max)- and if it reads your data that much faster than music playback of 1X and had all sorts of errors, much of your software wouldn't even run. There would be nothing logical about an error such that a computer could ever figure out what it *should* be. Of course computers also use checksums and other error correction methods to detect problems, and it isn't always expected to perform "real time" like a stereo component.
Last edited: