Where did you find it, exactly?The clocking on the Ultra is very stable, as Amir's review on ASR shows us. Not absolutely top of the class, but better than most other devices he's measured.
Where did you find it, exactly?The clocking on the Ultra is very stable, as Amir's review on ASR shows us. Not absolutely top of the class, but better than most other devices he's measured.
In my experience... you just shouldn't be using or owning equipment which has an unstable clock in the first place. It's a sign of poor engineering.
The clocking on the Ultra is very stable, as Amir's review on ASR shows us. Not absolutely top of the class, but better than most other devices he's measured.
Just s commonly seen j- test plot. What's spectacular on it?
I believe @574stereo 's point is that the jitter is low enough to be transparent and not an audible level of concern.Just s commonly seen j- test plot. What's spectacular on it?
Just a nit - but the USB is only asynchronous if the device on the other end supports asynchronous. Most modern DACs do support that but it is not clear if the converter here does.Talking about re-clocking only make sense for the S/PDIF interfaces.
The USB connection is asynchronous and don't include any audio clock. The receiving device always have to provide its own clock.
USB is always a asynchronous package transfer (frames). There are different modes used for audio data (Isochronous, Interrupt, and Control) but it will never include an audio sampling clock.Just a nit - but the USB is only asynchronous if the device on the other end support asynchronous. Most modern DACs do support that but it is not clear if the converter here does.
In computer audio terms, Aynchronous USB means that the DAC (or receiving device) controls the timing. Not all DACs can do that. In those cases, the Ultra uses synchronous transfer, which means it controls the timing. Wiim has confirmed that the Ultra uses synchronous or asynchronous transfer depending on the capability of the receiving device.USB is always a asynchronous package transfer (frames). There are different modes used for audio data (Isochronous, Interrupt, and Control) but it will never include an audio sampling clock.
For real-time audio the Isochronous transfer is used for the data (no error retry).
In the USB audio only isochronous transfer is used for audio data. For this transfer 3 modes are available - asynchronous, synchronous and adaptive.USB is always a asynchronous package transfer (frames). There are different modes used for audio data (Isochronous, Interrupt, and Control) but it will never include an audio sampling clock.
For real-time audio the Isochronous transfer is used for the data (no error retry).
Thanks for confirming what I said.In the USB audio only isochronous transfer is used for audio data. For this transfer 3 modes are available - asynchronous, synchronous and adaptive.
Correct when we talk about how audio data transfer is scheduled but this thread is about re-clocking and compared to S/PDIF, USB is asynchronous and the receiving device always definers the sampling clock.In the USB audio only isochronous transfer is used for audio data. For this transfer 3 modes are available - asynchronous, synchronous and adaptive.
It doesn't matter. Compared to spdif both are isochronous. And both are "clocked" by the host if usb synchronous mode is used. It becomes different when asynchronous mode is used instead - transfer pace is controlled by the receiver.Correct when we talk about how audio data transfer is scheduled but this thread is about re-clocking and compared to S/PDIF, USB is asynchronous and the receiving device always definers the sampling clock.
I don't agree. You are mixing up sample rate clocking (that can cause the jitter we want to minimize) and usb data frame transfer.It doesn't matter. Compared to spdif both are isochronous. And both are "clocked" by the host if usb synchronous mode is used. It becomes different when asynchronous mode is used instead - transfer pace is controlled by the receiver.