Qobuz still messed up

@gumbedamit there are multiple issues here. 
1. when there was a problem with qobuz it was related to the files they were serving to the streaming device that use Roon, jplay or native streamer software. The files were corrupted and they acknowledged the issue is on their side. This, however, has been resolved. At least I haven’t experienced issues in weeks now

2. network issues folks are having. You don’t need to hardwire to main router. A properly set up reliable mesh network will do just fine. I use eero and I never had network issues and it’s been years. 

@audphile1 I lead a group of Network engineers in  a top 5 financial institution.  Just giving you some context of my background. 

During any troubleshooting,  you start from bare rock, then add pieces in one by one. For me, Qobuz telling me there was an issue wouldn't stop me from troubleshooting on my own. It's like taking your car to a mechanic and telling then to change your radiator because your car is overheating,  only to find out it was the thermostat all along. Qobuz acknowledging a problem doesn't mean it's your problem.  For me, I would go back to the basics and test to make sure it's really a problem with Qobuz, to me, that would mean eliminating everything and just play Qobuz through my phone and see if the problem still exists. 

Listen to the Music 

@audphile1 Qobuz only streams Flac, there is embedded metadata;

Header info, Vorbis, etc, which is encrypted by TLS which has its own error correction.  You mentioned jplay, is that not a Windows audio engine. 

I only use Qobuz for streaming on my stereo system,  not familiar with the other's topology so I can't speak to that.  If the problem doesn't exist streaming directly to your phone, is it a Qobuz issue or a system issue?

Listen to the Music 

@gumbedamit 
 

I lead a group of Network engineers in  a top 5 financial institution.  Just giving you some context of my background
 

I’m very happy for you!

Files corrupted in cloud platforms due to cloud storage migration has nothing to do with network. And nothing to do with home network either. Understanding how network works and understanding software engineering is two completely different things. When qobuz says they have corrupted files after the migration, and the problem is worldwide with users not being able to play the exact same tracks, you are more than welcome to begin troubleshooting your home network. My advice is - work smarter, not harder. 

What is being described now with isolated cases of music streaming dropouts, are indeed most likely network issues. 
 

Jplay is not a Windows audio engine. It does not require any specific platform to run on. It is a control application that connects to your renderer using upnp and directs it to qobuz or tidal files you want to stream. 
There is no processing involved whatsoever. 

@audphile1 for me at least I doubt it’s a network issue as the renderers in question are hardwired to my Ubiquiti Cloud Gateway Fiber router (one directly and one via a Ubiquiti 2.5g switch) and all diagnostics to the clients show no network latency or jitter to speak of (<2ms), and download and upload ISP speeds to the modem are >950Mbps with 2ms latency; and speed from the router is consistently in the ~500-690 Mbps download and >800Mbps upload with latency of 4-8ms and jitter 2-7 ms.  

Also the fact that the same tracks play all the way through on TIDAL suggests to me the stopping mid-track events i have been experiencing are a Qobuz issue, but as long as I can side step it, i am not going to worry about it for now.