bits is bits


Being a retired IT tech, Iʻm a "bits is bits" guy. I keep seeing people rank different  streaming services against each other and I have to say, Iʻm mystified. Modern recordings are all digital masters and remastered. If two different hi-res streaming services, say Qobuz and Tidal, have the same track available, why would one sound different from the other, let alone better?

 

The stream is being fed over TCP/IP from the source, and I see no reason that it you were to do a cksum on the same file/track being delivered by either streaming service, that they would exactly match.  So why do people claim better sound from one streaming source over the other.  Iʻm assuming they are both full resolution sources, not mp3.

russbutton

I don't get why someone would have multiple streaming services and use each one independently. Based on reports that each streaming service has unique sound qualities, and the idea your streaming setup should be optimized for each player, this doesn't make sense. I have my entire music library on one server, this include Tidal and Qobuz, Roon provides the music player so there is no unique or differentiated sound from my Qobuz or Tidal music files. I've also optimized my streaming setup for Roon and Roon only. 

 

I'm not going to debate whether these streaming services offer unique sound qualities since I don't use their music player software. I'd only say a music file is bits is bits, the differentiated sound quality would be due to the music player software these services offer and how your streaming equipment interacts or works with them.

“Most audiophiles have come around by now to the realization that TCP is indeed bit-perfect - period.”
@devinplombier 

This part of the equation was never in doubt ~ the bits get there just fine. It’s what happens after that where things truly get interesting.  

As you pointed out, the issue revolves around parasitic noise propagating through conductive cabling, potentially coupling into the analog stages of components with insufficient isolation or grounding design, resulting in audible artifacts.  

The key is finding an isolation device that intelligently removes parasitic noise before those bits ever reach your streamer or server. Do that, and you’re golden.

@lalitk 

Doesn't a run of SFP fiber between listening room and utility room serve that purpose?

For the sake of completeness, the SFP converter on the system side should probably be equipped with a low-noise power supply, since it is located on the "sensitive" (read: non-isolated) side of the fiber run.

“Doesn’t a run of SFP fiber between listening room and utility room serve that purpose?”
@devinplombier 

Yes, it would. I personally didn’t care for using SFP fiber and converters in my system. For context, my streamer doesn’t have a native SFP port, so I ran a fiber optic link with converters on both ends between the router and the streamer. The result, though technically clean, made the sound feel sterile and dry. 

I settled a while ago on Telegartner Opt Bridge. It converts incoming copper (Ethernet) to an internal optical domain, then back to copper, thereby breaking ground-loops and removing parasitic noise. I am also using a LHY LPS to power the Opt Bridge. 

@sns I am streaming MQA from Tidal. Not everything was replaced. 
 

 

devinplombier

1,064 posts

 

@lalitk 

Doesn't a run of SFP fiber between listening room and utility room serve that purpose?

No. Most streamers use RJ45 connection. That long run of fiber will end with a fiber to copper converter and you are back to copper going into your streamer. Which isn’t the end of the world. Isolating it well and using good quality cables is easy. 
Let’s not overthink the cable aspect too much. Quality of recordings and a playback chain as well as room acoustics play a much bigger role than copper or fiber.
Don’t sweat it too much.