@antigrunge2 Can't argue with DCS products. John is a sales guy, keep that in mind. This quote is out of context. An external clock is useful 'maybe' to synchronize multiple boxes which i am not aware of any needs for doing so in HiFi. There are difficulties with that too.
Again, clocking is not complicated, with the caveat that I am not designing DACs at DCS ;-). One can go to Renesas or Analog Device and buy a a chip of a few dollars that produces a clock with with jitter in the range of a few hundreds femto second. This is another audio mystery to me. I have no idea what is going on in a DCS clock box. The engineer in me says that a 2$ chip right by the DAC is better/cheaper solution if the goal is to present the original bits to the DAC, but what do i know?
I'd try a DCS DAC any day, dont get me wrong (Although i'd buy a Tambaqui in the spot if it would come to used market), but i really, really do not like the external Clock business. Same a the Networking stuff, there is no engineering explanation for it. The gobbledygook from John Quick isn't it. I can speak gobbledygook but i prefer English.
This has zero applicability to Ethernet. THERE IS NO CLOCK GOING ON Ethernet CABLES. I dont know how else to say that. 1000baseT Ethernet has 8 wires, in 4 twisted pair, and they all carry data using the 4 pairs. Every frame, carrying a data packet (typically less than 1500 bytes) starts with a fixed 8 bytes of data that the receiver uses to synchronize its clock to decode the payload. Ethernet 're-clocker' aren't more of a thing than dry water, sorry, there has to be a line somewhere. USB ire-clocker is a different matter, I would not be caught dead buying one, that's a different conversation, but at least there is something to talk about there (there is an actual clock ;-)).