Roon Issues - Not able to play certain tracks
I have been running into this issue when Roon is in the radio mode where spontaneously it runs into a track it can’t play. It just sits there trying to play it.
When I go to that album and attempt to manually play that same track on Qobuz the result is the same - it won’t play. Plays other tracks from the albums just fine.
If I go back to Roon radio and skip that track the next song is played no issues.
No such problems with Tidal.
I have rebooted the Roon Nucleus One, rebooted my network, rebooted my DAC.
Even signed out of streaming services and signed back in. No bueno. This is in addition to it being sluggish and requiring an almost daily reboot to maintain sound quality and proper operating speed. Now this…
Anyone else with this problem?
Qobuz is foobar lately. Doesn’t matter whether using Qobuz via Roon or Qobuz Connect. There’s a long support thread about it on Roon Labs Community forums. Tracks work one day, and not the next. I was just playing the DG album of Yo-Yo Ma/BSO Shostakovich Cello Concertos. It got all the way to the very last mvt of the album without issue, and then it stalled. After that I was unable to play any track from the album. Rinse and repeat. |
@curiousjim No, it’s not a Roon thing. When I have a track that won’t play I can duplicate the problem using Qobuz Connect, bypassing Roon entirely. Roon has already stated they are in communication with Qobuz and it’s a problem on Qobuz’s back end. Just because you haven’t had the issue yet doesn’t mean you won’t. It depends on tracks you select and the timing of it. It’s all hit and miss. Apparently, Qobuz is changing their streaming cloud infrastructure and having growing pains. Edit: I just proved it to myself again. A track I was playing on Qobuz/Roon stalled and refused to play unexpectedly. When I play it on Qobuz Connect, it also refuses to play, but just goes to the next track instead. So the only thing you might be able to blame Roon for is not handling Qobuz' fail gracefully, but that's an API problem. The root cause is still clearly on Qobuz's backend, since it occurs with their own APIs as well. |
