2. cables
  3. 128927-305

Most Important, Unloved Cable...

Ethernet. I used to say the power cord was the most unloved, but important cable. Now, I update that assessment to the Ethernet cable. Review work forthcoming. 

I can't wait to invite my newer friend who is an engineer who was involved with the construction of Fermilab, the National Accelerator Lab, to hear this! Previously he was an overt mocker; no longer. He decided to try comparing cables and had his mind changed. That's not uncommon, as many of you former skeptics know. :)

I had my biggest doubts about the Ethernet cable. But, I was wrong - SO wrong! I'm so happy I made the decision years ago that I would try things rather than simply flip a coin mentally and decide without experience. It has made all the difference in quality of systems and my enjoyment of them. Reminder; I settled the matter of efficacy of cables years before becoming a reviewer and with my own money, so my enthusiasm for them does not spring from reviewing. Reviewing has allowed me to more fully explore their potential.  

I find fascinating the cognitive dissonance that exists between the skeptical mind in regard to cables and the real world results which can be obtained with them. I'm still shaking my head at this result... profoundly unexpected results way beyond expectation. Anyone who would need an ABX for this should exit the hobby and take up gun shooting, because your hearing would be for crap.  
douglas_schroeder
shadorne's avatar
shadorne
7,477 posts
 
@geoffkait

I don’t recall ever seeing you apologize. And you probably hold the record on audiogon for belittling folks and calling them sarcastic names. Your standard tactic being to insult the person rather than address the points in a discussion.

So I am not sure why you of all people should be affronted and feel you are deserving of an apology for your wee hurt little feelings 😰😰😰

And I suspect you presume too much that you actually speak for "us" - being I suppose all your wee brothers and disciples here on the Gon...
jinjuku's avatar
jinjuku
226 posts
 
Would it be presumptuous of us to expect an apology from jujitsu after his little get together?

Geoff,

Exactly what would I be apologizing for? To date I've at the least used everyone's handle here.

WGutz,

I would like to see if the 3rd weekend in October will work for you 

My plan would be using Rene van Es's exemplar setup when he did a deep dive into the audibility of CAT cabling. I will simplify with a Cisco Switch that takes one input and has two outputs. With the LAG configuration the switch provides a faux MAC address that maps to the ports that are outbound to your Streamer/Computer/Endpoint. 

This will allow the cable to be switched at the Streamer/Computer/Endpoint with out causing an issue from the perspective of the source. 
wgutz
85 posts
 
Please provide a specific day and time as I would like to invite a few of my friends. I feel a simpler approach is to plug in each of the CAT wires directly and thereby avoid any issues of additional elements, such as the wire from the source to the switch.
jinjuku's avatar
jinjuku
226 posts
 
Can you give me the current topology of your networked audio?

The reasons for the switch. For one I’m taking a page out of a setup where there is Router<>Switch<>Switch<> Endpoint.

https://www.extremetech.com/computing/174991-increasing-the-sound-quality-of-your-music-by-switching...

The Cisco is going to allow me or even one of your friends to swap out just at the endpoint device to minimize error.

Let me firm up my schedule and how much time would you need playing around with this prior to evaluating blind?

I can suggest two methods:

If your player has enough buffer just queue up tracks and the cable can be changed/unchanged(that is same cable removed and plugged back in) out at a random interval.

Or

Setup a looping track or a snippet of a track with a 15 second interval track between and the possible swap would happen then.
jinjuku's avatar
jinjuku
226 posts
 
To be clear I'm proposing Source<>Switch<>Client 

That would be like: Tidal<>Router<>Client
More to discover