Jump to content
IGNORED

Audio Grade Router and Switches in RMAF with SOtM


Recommended Posts

 

 

 

4 hours ago, d_elm said:

If a data stream stays in the digital domain then clock jitter is handled by the circuit design.  It is when the data stream is processed by a DAC the upstream handling can become important for the generated analog signal.  In the thread I linked to many people describe their findings.  One finding is that good upstream clocks make a difference but only if not followed by a bad clock.

 

All I see is a thread full of people that don't understand how buffered systems, clock domain boundaries, FiFo buffering works.

 

So if we use your assertion that it's cumulative clocks then what about all the clocks on the routers between here and www.tidal.com

 

Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           ########.cinci.rr.com [192.168.0.117]
                                0/ 100 =  0%   |
  1    1ms     0/ 100 =  0%     0/ 100 =  0%  192.168.0.1
                                0/ 100 =  0%   |
  2    8ms     0/ 100 =  0%     0/ 100 =  0%  142.254.147.213
                                0/ 100 =  0%   |
  3    9ms     0/ 100 =  0%     0/ 100 =  0%  be63.lsvnkyfb01h.midwest.rr.com [74.128.8.17]
                                0/ 100 =  0%   |
  4   13ms     0/ 100 =  0%     0/ 100 =  0%  be20.lsvqkydb01r.midwest.rr.com [65.29.31.24]
                                0/ 100 =  0%   |
  5   25ms     0/ 100 =  0%     0/ 100 =  0%  be24.clevohek01r.midwest.rr.com [65.189.140.166]
                                0/ 100 =  0%   |
  6   32ms     0/ 100 =  0%     0/ 100 =  0%  bu-ether17.vinnva0510w-bcr00.tbone.rr.com [66.109.6.70]
                                0/ 100 =  0%   |
  7   30ms     0/ 100 =  0%     0/ 100 =  0%  0.ae1.pr1.dca20.tbone.rr.com [107.14.17.210]
                                0/ 100 =  0%   |
  8   29ms     0/ 100 =  0%     0/ 100 =  0%  24.27.236.44
 

 

But yet I've read posts about how Tidal sounds just as good as playing a local file. 

 

I'll come out to anyone's setup and take a .wav file and make one copy local storage, another over a network and using foobar ABX plug in show you that this is 100% bullshit. 

 

I'll give you $2000 if you can hit 18/20  and if you can't just pay my travel expenses. 

Link to comment

I think I get what @plissken and others are saying ... I'm no expert, but makes sense to me. There is some debate on other threads that lead to the notion that effects of leakage current could manage to 'jump' ethernet transformers and potentially could end up as 'noise' downstream. So, no effect of the music signal, as demonstrated, but possible effects on say, the DAC. I am sceptical about high priced mods to switches, but is this what it is they are trying to address? Apologies, if my point is not very clear.

Main System: NAS or QOBUZ > BlueSound Node 2i > Schiit Gungnir MultiBit > PYST XLR > Schiit Mjolnir 2 or Gilmore Lite MK2

 

Office System: iMac > Audirvana > Schiit EITR + Audiophonics LPS25 > Metrum FLINT NOS DAC (DAC TWO chips) > Schiit Magni 3+ > Aeon Flow Open

 

Loudspeaker System: NAIM Muso Gen 2

Link to comment
56 minutes ago, ismewor said:

Yes, it sure make a huge different if it done right, that is why we are now tracing to replace the clock on the mobo. 

perhaps one of the main contributors to simultaneous switching noise (the main background noise of any microprocessor based system) is DDR memory, that's why DDR3 has spread spectrum ability. The clocks on PC's are critical, the routing of the clocks is critical, changing one is not just plugging another clock in on the end of a piece of wire... The chances are the length of wire and possible return path discontinuity will add as many problems as it is supposed to solve. Why do we put clocks as close to the input pins as possible, shortest routing (except DDR3+ where the clock is the longest signal, but routed as a diff pair with minimum skew, 0.25mm), minimal vias, minimal impedance changes in the signal path... 

Unless the system is designed to be operated by a master clock, but that requires a whole system exercise in clock distribution... With clock buffers etc.

Link to comment
1 minute ago, marce said:

Why do we put clocks as close to the input pins as possible, shortest routing (except DDR3+ where the clock is the longest signal, but routed as a diff pair with minimum skew, 0.25mm), minimal vias, minimal impedance changes in the signal path... 

I agree and that is very true. 

DigitalDac: Chord DAVE, Amp: MC275 Mono, Preamp: FirstSound, Source: Esoteric K01X, Cable: TaraLab GME interconnect,
CASSOtM Trifecta Mod 75ohm MCI, TheLinearSolution TCXO Router

Analog: SME 20/2, SME V, Skala, Esoteric C03 Phono

 
Link to comment
7 minutes ago, marce said:

perhaps one of the main contributors to simultaneous switching noise (the main background noise of any microprocessor based system) is DDR memory, that's why DDR3 has spread spectrum ability.

 

I went into perfmon on a Windows 10 machine with almost everything that I could disable process wise, well disabled, I showed all the caching operations that was still going on.

 

There is just a ton of system activity.

 

Quote

The clocks on PC's are critical, the routing of the clocks is critical, changing one is not just plugging another clock in on the end of a piece of wire... The chances are the length of wire and possible return path discontinuity will add as many problems as it is supposed to solve. Why do we put clocks as close to the input pins as possible, shortest routing (except DDR3+ where the clock is the longest signal, but routed as a diff pair with minimum skew, 0.25mm), minimal vias, minimal impedance changes in the signal path... 

 

I pointed this out in another thread when they showed modified switches with a TXCO on a separate assembly with what looked to be about 16 inches of round trip lead wire. 

 

 

Link to comment
15 minutes ago, plissken said:

 

 

 

I pointed this out in another thread when they showed modified switches with a TXCO on a separate assembly with what looked to be about 16 inches of round trip lead wire. 

 

 

The 1ns rule...

Some rule of thumb:

http://www.hottconsultants.com/techtips/rulesofthumb.html

So an 8" run even if it was stripline (cables will differ, but will still be between 0.1-0.3ns)) would add about 0.2ns propagation delay, are we going to get pico second jitter figures with that length, and how closely coupled was the return path and finally what about the cable capacitance effecting the clock, longer cable higher C, add the extra inductance and you get filtering of the high frequency content of any wave, add the receiver and transmitters capabilities into the equation and you have fun...

Link to comment

.

1 hour ago, plissken said:

 

 

 

 

All I see is a thread full of people that don't understand how buffered systems, clock domain boundaries, FiFo buffering works.

 

So if we use your assertion that it's cumulative clocks then what about all the clocks on the routers between here and www.tidal.com

 

Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           ########.cinci.rr.com [192.168.0.117]
                                0/ 100 =  0%   |
  1    1ms     0/ 100 =  0%     0/ 100 =  0%  192.168.0.1
                                0/ 100 =  0%   |
  2    8ms     0/ 100 =  0%     0/ 100 =  0%  142.254.147.213
                                0/ 100 =  0%   |
  3    9ms     0/ 100 =  0%     0/ 100 =  0%  be63.lsvnkyfb01h.midwest.rr.com [74.128.8.17]
                                0/ 100 =  0%   |
  4   13ms     0/ 100 =  0%     0/ 100 =  0%  be20.lsvqkydb01r.midwest.rr.com [65.29.31.24]
                                0/ 100 =  0%   |
  5   25ms     0/ 100 =  0%     0/ 100 =  0%  be24.clevohek01r.midwest.rr.com [65.189.140.166]
                                0/ 100 =  0%   |
  6   32ms     0/ 100 =  0%     0/ 100 =  0%  bu-ether17.vinnva0510w-bcr00.tbone.rr.com [66.109.6.70]
                                0/ 100 =  0%   |
  7   30ms     0/ 100 =  0%     0/ 100 =  0%  0.ae1.pr1.dca20.tbone.rr.com [107.14.17.210]
                                0/ 100 =  0%   |
  8   29ms     0/ 100 =  0%     0/ 100 =  0%  24.27.236.44
 

 

But yet I've read posts about how Tidal sounds just as good as playing a local file. 

 

I'll come out to anyone's setup and take a .wav file and make one copy local storage, another over a network and using foobar ABX plug in show you that this is 100% bullshit. 

 

I'll give you $2000 if you can hit 18/20  and if you can't just pay my travel expenses. 

 

 

...and what happens when packets arrive out of order? Changing out switch clocks and caps is crazy! The power supply used by a switch might make a difference....but this is getting out of hand.

Link to comment
17 minutes ago, Speed Racer said:

.

 

 

...and what happens when packets arrive out of order? Changing out switch clocks and caps is crazy! The power supply used by a switch might make a difference....but this is getting out of hand.

Just a question, what happens to noise generated by the switch (or downstream FMC), either from power or clock ?  I hear it downstream in my DAC.

Link to comment
24 minutes ago, d_elm said:

Just a question, what happens to noise generated by the switch (or downstream FMC), either from power or clock ?  I hear it downstream in my DAC.

 

Years ago I took a TRS to XLR cable. On the XLR side I floated Ground (pin 1). You could hear mouse movement, HD access, Cache fill (using a RAM Disk). 

 

It was a system that was purposefully designed incompetently.  You should do the same thing with your DAC that I did with my cable: I fixed it. In my case it was to solder pin 1 backup. In your case it would most likely be a new DAC. 

Link to comment

This is what we call Audiophile world :D

DigitalDac: Chord DAVE, Amp: MC275 Mono, Preamp: FirstSound, Source: Esoteric K01X, Cable: TaraLab GME interconnect,
CASSOtM Trifecta Mod 75ohm MCI, TheLinearSolution TCXO Router

Analog: SME 20/2, SME V, Skala, Esoteric C03 Phono

 
Link to comment
7 hours ago, plissken said:

Bottom line is the OP asked a question and has gotten into a huff because the answers don't fit the preconceived answer they already had when they asked the question. 

 

 

He should have posted in a "safe space" like the tweaker thread

Link to comment
On 10/24/2017 at 2:37 PM, d_elm said:

Just a question, what happens to noise generated by the switch (or downstream FMC), either from power or clock ?  I hear it downstream in my DAC.

Well, I would say not many notice of that. and you should be graceful for it. If you don't mind point out your setup will see if there something it can be done to isolate it. 

DigitalDac: Chord DAVE, Amp: MC275 Mono, Preamp: FirstSound, Source: Esoteric K01X, Cable: TaraLab GME interconnect,
CASSOtM Trifecta Mod 75ohm MCI, TheLinearSolution TCXO Router

Analog: SME 20/2, SME V, Skala, Esoteric C03 Phono

 
Link to comment

Just got my TCXO router from the linear solution tonight. Wow, I was surprise by the packaging and craftsmanship of this company. Been busy and I’ll try to compare with my current router with LPS along with SOtM Trifecta. Hopefully I can get some  critical listening done over the weekend. 

1B546D9E-2A66-4579-9B81-BF8F2183873A.jpeg

DigitalDac: Chord DAVE, Amp: MC275 Mono, Preamp: FirstSound, Source: Esoteric K01X, Cable: TaraLab GME interconnect,
CASSOtM Trifecta Mod 75ohm MCI, TheLinearSolution TCXO Router

Analog: SME 20/2, SME V, Skala, Esoteric C03 Phono

 
Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...