SuperQ wrote: > Yes, I know all about getting bit errors across the network. TCP > checksums and ethernet frame CRCs can be corrupted in subtle ways > especially when your switch is doing vlan tranlations and the frame > checksums are being recalculated. This type of thing doesn't happen on > home user networks so it's not really as big a deal. We're also talking > about very very low bandwidth rates of only a megabit or so.
I've seen it for simple TCP traffic (e.g. NFS) across a single simple IP router; but at likely considerably higher bandwidth, agreed. > The point of all this is the % chance of this happening in a an audio > stream AND not being completely obvious as garbled/static frames is so > low it's not worth talking about. Un-caught corruption in the > IP/packet level will likely cause completely obvious garbled audio > output. agreed. If anything, the far bigger problem comes from copying your ripped files across the network from one store to another, and getting (silent) corruption en route. That can be avoided by using a copy mechanism incorporating its own, more secure, checksum/digest, e.g. SSL, SSH, encrypted NFS, etc. And of course this applies to all types of files. but I'm getting a bit OT, apologies. cheers, calum. _______________________________________________ audiophiles mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/audiophiles
