If the cable is not properly shielded, the power being carried so near will affect the data movement. Remember data is also being carried as mild electrical current. If there is interference, the data will also get affected. When I said bleeding, I did not mean that the power will move into the cables carrying data. If that happens, it is short-circuiting. What I meant was interference and corruption of data.
Thad, if you do an analysis of data transmission between any two computers connected on a LAN, you will see data losses. In the days of Novell, we used to actually analyse this on-line, regularly. I am not sure anyone bothers any more. If you look at torrents, for example, they constantly display 'wasted' data through 'hashfails'. As one member said, it may be less, but it cannot be denied that there is data loss in digital transmission.
Cheers
Venkat,
Sorry to chime in at such a late stage but I think two different issues are being confused here. The data losses that you are talking about are because of packet collisions created due to the same network/cable/data path being shared by multiple hosts. In today's switched Ethernet LANs, this is eliminated. The reason you still get data loss on the Internet is because of the fact that everything is not "circuit" switched in the path from the other computer to yours. This has NOTHING to do with how a particular cable (Ethernet or USB) carries its individual data bits.
Regarding the discussion about interference, the whole point of "Certifying" something to a standard means that all these factors have been measured, analysed, and adhered to. If a cable advertises itself as USB 2.0, it automatically implies that it is capable of supporting the required bandwidth for 2.0 data rates, it has power and shielding protection to do so (which is also specified in the hardware standard for USB 2.0) and that it adheres to the clock specifications of the standard. Of course, if the manufacturer has lied about what the cable does, there is no way of knowing. And that is why all of us prefer to go for a branded cable ( as you and Thad and others have pointed out), because we are paying for the reassurance of quality, NOT because the branded cable has any better data transmission (or audio) qualities, compared to a well-implemented, non-branded cable.
I would also like to point out that unless one has a solid understanding of electromagnetism, which is a subtle and complex phenomenon, one should not try to imagine only current as being the carrier of information, nor should one talk about interference. Unless one understands how EMI occurs, and how much of it is really measurable compared to other sources of noise in the audio chain, all such discussions are superfluous and actually very misleading. I have seen many discussions like this on other forums, where most people are trying to describe electrical properties without having any idea about Maxwell's Laws, which is what a cable acts according to, as a short transmission line. And at the distances we are talking about (Laptop to DAC, DAC to Amp etc.), these effects have to be measured before saying they are causing noise.
Sid, just to add a bit of information to the cable discussion:
We "audiophiles" deride any other standard except pure analog for passing "exact" signals between components. In particular, because most "audiophiles" (and here I mean the Stereophile generation) come from an analog circuits background, they have a difficult time understanding computer-based audio, which is why they convert that misgiving into misleading skepticism about anything digital/computer-based. This is based on my reading many of their articles, and seeing the subtle msgs interspersed.
So, to help solidify their digital nightmares (along with anybody else who still thinks digital is inferior/dangerous/lossy/poorly understood), remember that the next time you fly the Airbus A380, one of the most advanced, safe, and beautiful machines to fly through our skies thus far, you are trusting your life to the Ethernet standard, because the A380 avionics bus is Ethernet- and UDP/IP- based! (Search for "Ethernet" in the link below)
Airbus A380
My point is, if Airbus engineers who deal with EMI, losses, and noise on MILES of cable, which are designed to carry millions of passengers safely,
use and trust the standard Ethernet (along with UDP/IP!) through years of experience, I think as "audiophiles", we should be a little humble and recognise that a few nanoseconds of jitter on a USB cable (if it even exists) will not spoil our lives or our music enjoyment. Our ears are not that sensitive compared to the sensitivity needed by stability control algorithms on a massive airplane, which require much more precision, and much less jitter than the average audio replication chain.
-Jinx.