Rerurn to Romy the Cat's Site

Well, I admit that I was clueless on the subject but I was intrigued and I consulted my engineering recourses.  It turned out that what I proposed above was not exactly accurate: for instance regular computers do not use I2S bas interface…

To make the long story short: For a computer the USB port is a devise of the same hierarchy as sound card and there is not different for a computer to where output stream: to a driver on the sound card or to the driver the sit behind the USP port designation. With identical drivers used the ASE/EDU interface has fundamentally lower jitter interface, where the min jitter for USB is not even included in the USB standard. So, with identical design (more of the time used) the USB has no chance to be superior.

There is a catch however. With proper design, when USB is made not for utilitarian purposes but for high quality transfer, the USB has internal chance to be way more advanced. The ASE/EDU is forward-only interface where stream flows only in one direction with data mixed with clock marks. The USB is full duplex or bi-directional interface where stream flows in both ends. This enables designers to put a clock that might everything on the receiver side (DAC) and let this clock to manage the USB’s and even reader timing. USB sends data in burps by requests of by scheduled timing, this marks all might be managed by receiver side clock. In ASE/EDU the receiver shell recognize the timing marks and PLL or re-clock data. In USB there are no needs for PLL or re-clocking as the data arrives at the marks of the original clock. The USB in this case acts like an elephant that sticks a long trunk to another devise and sucks juice… according to my consultants this USB implementation is the most proper way to do the things. Or course no one knows HOW the USB is managed even if a DAC has USB port…

Rerurn to Romy the Cat's Site