That is correct, but strictly speaking that is not jitter but "packet noise".
Agree, but since we are talking about reclocking USB signal, packet clock jitter is the only thing such a reclocker can potentially fix, not sample jitter.
That is correct, but strictly speaking that is not jitter but "packet noise".
Agree, but since we are talking about reclocking USB signal, packet clock jitter is the only thing such a reclocker can potentially fix, not sample jitter.
Jitter is not noise - noise is a frequency domain issue and jitter is a time domain issue.
Jitter is not noise - noise is a frequency domain issue and jitter is a time domain issue.
But, if you meant to write phase noise then yes, that's measured in the frequency domain.
Phase noise is a term related to analog signal, not digital.
Jitter we are talking about is SPDIF jitter coming from timing varations during synchronous data transfer. In analog signal it will manifest itself as a distortion (change of waveform).
USB packet noise is not jitter, it is coming from USB control pulses. From analog signal perspective it is a noise being injected in analog signal.
All valid, but I think this discussion is jumping too much between USB, SPDIF, reclocking and noise in digital and analog. All of these are separate topics, and no generalization cuts across all of them.
Jitter can be anything it wants to be. It can be noise in which case it just raises the floor of the DAC, or sine wave, or square wave or in reality, combination of all of these.SPDIF) Jitter is not noise and it is not related to analog world.
Jitter can be anything it wants to be. It can be noise in which case it just raises the floor of the DAC, or sine wave, or square wave or in reality, combination of all of these.
Uhhh.. But you don't feed SPDIF signal to USB DAC via USB, do you?
USB DACs are typically connected directly to computer running software players which are reading the music files from storage or fetching stream from the Net, so no jitter there. As we said, USB communication is async so no jitter there as well. Once async packets reach USB receiver chip it buffers them and sends them synchronously to a DAC chip via internal link within the device but jitter there is negligible for the reasons I described.
My issue is addressing the evolution of USB receivers and implementation that makes a USB refining device (for S/PDIF or I2S) unnecessary. You all who will say that asynch USB has no issues are wrong in my experience because it was not a be-all solution when it was introduced as a port for DACs a decade or so years ago. I want to know if modern designs have become the be-all port some of you gentlemen say it is.
Whether or not USB async is the 'ultimate' solution isn't the question. Whether or not it needs external reclocking to improve sound quality -- is. And the answer is: it doesn't.
What? That is like asking me to give you a link for 1+1 = 2. How much have you studied this to challenge me this way? Even the Wiki tells you this: https://en.wikipedia.org/wiki/JitterI don't agree with that. Is there a link which supports such wide definition of jitter?
...I realize it can get complicated and it's probably a task to dumb it down and have it make sense to less technical folks. I have some idea that technically proficient members are here because they're technically proficient and seeking empirical data and not to try to explain technicalities to amateurs. Although many like to argue among themselves anyway. I just wish these guys would admit they enjoy arguing with each other.
Are you saying specifically that USB data has no use for external reclocking before it reaches an asynch USB receiver? I understand that USB packets are conveyed in an orderly manner and it's just data to be processed. I'm thinking of that which the USB receiver has produced and is sent to the DAC internally or run out through S/PDIF or somebody's configuration of external I2S (like HDMI).
I should be able to take an asynch USB receiver like this and it will perform as well as my Off Ramp 5? If not, why? I'm not trying to be an ass. I want to learn.
A discussion on this and similar issues deserves a unique thread. ASR is a community with a ton of potential for schooling. Seems a new corner of the forum could be created for schooling, although there would probably be just as much arguing there. I almost feel bad or guilty of something bad for asking about this sort of thing (above). I realize it can get complicated and it's probably a task to dumb it down and have it make sense to less technical folks. I have some idea that technically proficient members are here because they're technically proficient and seeking empirical data and not to try to explain technicalities to amateurs. Although many like to argue among themselves anyway. I just wish these guys would admit they enjoy arguing with each other.
Yes the other thing to consider is that if you are looking at headphone amp capabilities,the RME ADI-2 DAC has that built in, which the Gustard does not... I also would be willing to bet on a better stateside and euro side warranty and repair infrastructure for RME at this time.Buy based on looks and feature set, there is no wrong answer to that question.