Ethernet Clocking


i had previously reported that adding an Antelope 10m rubidium clock to the Etherregen results in major tightening of soundstage and location of individual instruments. To my great surprise adding filtering on the BNC 75 Ohms connection between clock and Etherregen results in substantial additional benefits. The filter used is a Mini-Circuits BLP-10.7-75+ DCto11MHZ model.

We are only beginning to understand how to maintain clean clocking on digital connections, it is of paramount importance to SQ.

antigrunge2

@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 ;-)). 

“Ethernet ’re-clocker’ aren’t more of a thing than dry water,”

@lmcmalo

You may choose to believe that or try one of the audio grade switches and report your findings. I believe your system is good enough to render any subtle changes with a switch like Silent Angel. If you choose not to be open minded, we understand that too! After all you can lead a horse to water, but you can’t make it drink.

 

@imcmalo,

 

you’ll forgive me when I believe what I hear rather than what you postulate. This is getting old fast and I distinctly feel that old @cakyol is hiding behind this new moniker. Read the full quote and you’ll see why it’s there

I’d say let’s all welcome @lmcmalo here. We may disagree in several topics, but he seems completely ingenious in what he says and appears to have a very good technical understanding and hands on experience, audio or not. 
 

Let’s not confuse him with typical troll like individuals like the usual @cakyol dude who say NOTHING makes a difference. Not the same

The quote from DCS refers to their Bartok streamer/dac and specifically addresses the superior integrity achievable through external clocks. Likewise John Swenson, designer of the Etherregen specifically refers to improvements achievable through superior clocking. More importantly the benefits as I described in my post are clearly audible. To negate all this by postulating principle based ‘knowledge’ as a network engineer don’t impress me much. Obviously @thyname is entitled to his own view.