Re: usb and firewire
This is true. USB requires more CPU-level processing of data, and is thus less reliable for high-bandwidth "streaming" operations. Of course, USB has its own "built-in chipset" too, but the USB architecture requires an OS driver to interpret USB signals as they come in, while the FireWire chipset handles basic IO all by itself.
This is, BTW, why you see a bit more push towards USB 2.0 on the marketplace:
1) It "looks" faster than FireWire (480Mbps vs 400Mbps), and in reality is "close enough" most of the time.
2) The device-side chips are cheaper because more processing is done on the host (computer) side. Saving $0.10 per device might not seem like a lot (heck, i for one would gladly pay a buck or two more for a Firewire port instead of USB 2.0!), but it adds up over millions of units ...
Originally posted by jayscheuerle
My limited understanding is that USB uses your computer's processor to processinformation, while Firewire has its own built-in chipset.
That's why Firewire's more expensive and why in situations where a steady stream is necessary (video work) it is the preferred choice... - j
This is true. USB requires more CPU-level processing of data, and is thus less reliable for high-bandwidth "streaming" operations. Of course, USB has its own "built-in chipset" too, but the USB architecture requires an OS driver to interpret USB signals as they come in, while the FireWire chipset handles basic IO all by itself.
This is, BTW, why you see a bit more push towards USB 2.0 on the marketplace:
1) It "looks" faster than FireWire (480Mbps vs 400Mbps), and in reality is "close enough" most of the time.
2) The device-side chips are cheaper because more processing is done on the host (computer) side. Saving $0.10 per device might not seem like a lot (heck, i for one would gladly pay a buck or two more for a Firewire port instead of USB 2.0!), but it adds up over millions of units ...