This is very strange. I haven’t tried it myself but I suppose we can on Monday. It sounds like the problem is only when Mconnect is controlling the Bridge? If you play the same thing on Roon it properly connects and plays right?
The way these things work is what’s confusing me. When you connect to the track on Tidal, either through McConnect or Roon the software is merely connecting the Bridge to a memory location on a server. McConnect and Roon will connect the Bridge to the exact same memory location where the track lives. The difference then is that Roon will be connected to the memory location on Tidal’s server and does the first bit of processing. In the case of McConnect the Bridge is directly tied to that server location without going first through Roon.
So, for whatever reason, it appears Roon is handling the track in a way the Bridge is not. I know that’s not helping fix the problem, but that’s how it works.
I’ll forward this thread to Mark in service so he can try the same thing, though chances are pretty good we won’t be able to fix it right away since a: we don’t control or manage McConnect (if that’s the problem) or b: the Bridge (if it’s the problem) takes some time to fix because it too is managed by outside programmers.
If I had to guess there’s something different with that track that doesn’t both Roon and it does bother the Bridge. It’s unlikely it’s McConnect since it is only connecting the Bridge to the server location to start streaming.
