vacuum_tubes
pfm Member
That makes sense. My understanding is a DLNA renderer is pretty dumb. It wants an instruction and location. Go here, play this. It wouldn’t have a clue what an album was. Early ones couldn’t even cope with gapless and glitched, paused or popped if given what I assume is an immediate ‘play’ instruction and location for the next track. MConnect has a ‘gapless to renderer’ option that the DSX understands fine. I think this is a pretty neat solution as it means the control surface isn’t in the data loop, it only monitors and sends follow-up commands.
Problem is that with the mconnect out of the streaming chain you have no buffering/caching available to deal with errors or glitches from Qobuz.
Roon may have helped you, because of the way it handles grouped or multizone playback it streams (RAAT) to the endpoint much more "realtime" as it doesn't allow the client to buffer Had a look at Roon partners page and unfortunately the DSX is not certified so you wouldn't be able to use RAAT.
I'd give Audirvana a trial, that supports DLNA and will buffer the audio before sending it to the DLNA client. That may alleviate the issues having the DSX and Qobuz going direct, as it now sits in the streaming chain.
Also has IMHO the added bonus of sounding much better than Roon or other playback clients/software.
Also I'd try the test of unplugging the NIC on the DSX multiple times to see what sort of buffer it has, if you only tried it once or twice the buffer may well have been close to empty when you unplugged and that's why you only got around 1sec. Try it again but do it at least 10 times and see what you get?