Quote:
|
Originally Posted by StanleyB1
How does a flipped bit sound, and how many continuous flipped bits would have to be strung together before anyone could pinpoint it with certain accuracy?
|
Going on some pretty wild-ass assumptions here, but...
Assuming that a FLAC file is 16 bits/48kHz (typical audio content), and that the bitstream is a bit at a time, 16 bits per audio "frame", 48000 audio "frames" per second.
Then if you had 1 flipped bit, it would corrupt a single audio frame, which would sound "bad" for 1/48000 of a second. 1/48000 is roughly 1/50000 which is 0.02 milliseconds or 20 microseconds. If you flipped multiple bits in a row, it is possible that they all lie within the same audio "frame" and thus only one frame would still be corrupted. Or, if you had a steady stream of corrupted bits spaced around 16 bits apart for many bits you would start corrupting multiple audio frames, resulting in a sound "error" lasting multiple frames of 20 microseconds each.
How many 20 microsecond bad frames would you need? No clue, but i'm guessing probably a lot.
Note that this does not take into account error-correcting protocols in wireless transmissions and buffering, where a flipped bit (or bad packet) can be detected and resent without interrupting the flow of data due to the buffer. I'm not 100% positive but there's no way any multimedia streaming device (i.e. squeezebox or Airport Express) is operating without a buffer, and while I don't know the details of the 802.11 spec but I am pretty sure there must be some kind of error checking/error correcting code built into the protocol.
Ruahrc