Well i can’t say it gets me excited - i’m long done with fiddling about with stuff like this but we have other members that enjoy this part of the hobby.
The first sensible post I’ve read on this subject for quite a while.
It’s ‘amusing’ reading the thread & I wonder how long & were it will end up, I suspect the same old goat trail dead end as all the ethernet threads.
but Who has the Cisco 2960 white is gigabite mod.cg or poe mod.ttl ???
Hmmm…maybe that’s because as long as they perform to ethernet specifications they really don’t make a difference, since digital audio lives at the application layer, and only frame data lives at the hardware layer where switches and ethernet cables are found?
As with all threads about cables, especially ethernet cables, it will end in tears.
So, as Mrs Merton used to say, let’s start a heated debate.
I’ll go first.
I have AudioQuest posh ethernet cables, but I am seeking help.
I also have a Cisco 2960 switch and the difference is night and day, or is that ‘different league’, I can never remember.
My Nova runs off a Netgear switch and my NDX2 an Apple Time Capsule that doubles as a back up/switch and wireless thingy. All works perfectly.
Hmm, rather missing the point… this is nothing to do with Ethernet data, but more about the electronics that modulate the serial voltages and doing it in a way that minimises ANALOGUE conducted noise.
Several engineering white papers on this in the public domain including specialist analogue componentry to reduce conducted noise which this ‘audiophile’ product makes no mention of…
Now I agree in addressing this, just like Ethernet cables, one can throw money at the audiophile merchants, or simply get a quality suitable switch from the ‘bay for a few tens of pounds.
The area of proper Ethernet frame isolation interests me, and so far has not entered the audiophile market yet… but if you have good network routing and switching design and implementation skills you can achieve it with the right network equipment… and here we are talking routers, not L2 switches.
The alternate is to largely decouple Ethernet / digital transport from the DAC… at the system level a similar outcome can be achieved… and it’s the method I currently do.
hello, what kind of ethernet cables have you connected the time capsule to the modem router? me with a cat.6 but I’m thinking of replacing it with a Melco cat.7 ethernet cable
I recently bought three 1m cat 6a to replace AQ Cinnamon. Very pleased with the results (and made a small profit).
Did you compare to their Cat6?
They recommend Cat6 in preference and claim their Cat5e and Cat6 sound the same, which is not at all what I found, preferring their Cat6, which is fuller, more textured and dynamic and more detailed. God knows why…
I’d definitely go for different league. Night and day would be over the top in this case
No, but the adjectives you use apply nicely to what I’m hearing. Fit and forget now as far as I’m concerned.
I give up… this has been explained more often than I have had hot dinners on this forum … and people still say ‘God knows why’… perhaps it’s easier if we just say it’s magic…
The Time Capsule is connected to my IP (Spark) router by a long run of internally wired (walls and ceiling) Cat 6 Ethernet cable. There’s no practical option to change that.
I have a ubiquiti set up including three switches, I wont be swapping them out any time soon for a perceived difference in the slight texture of a symbol or what ever.
If you want to enjoy your music more, get half cut and turn the volume up.
I have a white 1gb model and a 100mb blue one.
I have a CG but I’m not sure why you are asking.
I guess this is a perfectly acceptable answer in certain audiophile circles
Couldn’t we achieve something similar with port-based traffic control, which I guess is an available feature on Catalyst 3560 ?
Thomas, perhaps you can explain what you are referring to with ‘Port based traffic control’?
Switches do port based traffic manage to of most frames.
There are however broadcast frames, ARP processing, and multicast group frames which can load the port irrespective of unicast data going to the specific host.
Creating a separate subnet from the rest of your network with the appropriate helpers and routing protocol support can reduce the above and consequential processing noise from the host (streamer) network stack and processor.