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?
@jji666 i have to disagree on this point.like @audphile1 I’d found Roon stalling on various tracks over the past few weeks (e.g, Baba O’Riley and Steely Dan’s Peg,, surely two of the most available tracks any where); when it happens i go to JPLAY and the track plays with no problem. Qobuz is not the problem. |
I think the current Roon operating system has reached the point of becoming what is called “technical debt”. It’s where it’s no longer feasible to continue to apply patches as the foundation itself cannot support bugs/defect fixes and new features. |
You know, Roon reminds me of Tesla. Over the years 2018-2022 Tesla bogged down the car with all these useless features, easter eggs, games that 80% of the owners didn’t use or care about, and all of a sudden the computer wouldn’t do the basic functions without issues. The car would crash constantly. The built in browser would not even load. And there was no choice; many wanted to go back to the basic software without any of the bells and whistles, but no go. The released patch after patch only to create 3 more issues with every supposed fix. After a while the majority would not allow the car to update because it would be more broken than before, but then the company would not take even longer to realize what the patch had broken. The audio system always seemed to take a back seat to games by the way, even basic album art doesn’t show to this day. And then the solution was a new "optional" computer upgrade, only because the threat of class action lawsuits because the "upgraded" car was becoming unusable. There was also a flash drive that was failing, that was repaired by a recall as it was a safety item. For those who didn’t want to buy a new computer the old software was re-coded by John Carmack so the car would work without crashing constantly: Roon should do what Tesla didn’t, offer a "lite" version without all the dsp, ARC, and convolution crap and focus on sound quality as the primary objective. And charge less money for it. If someone wants more features and bells and whistles, pretty graphics for their streamer screens and to be able to play it in their car they can pay more for it. |
Speaking of JPLAY, check out the impressive list of manufacturers now JPLAY-certified, it’s honestly tempting me to pick up one of those streamers and ditch ROON altogether. What streamer are you using to stream music? Agree with you on lite version of ROON, Let’s see how ROON shows up on April 20th… |
This thread has been helpful to me as I’ve been experiencing Qobuz issues in both of my systems and was wondering if T+A (DAC/streaming client hardware) had done a software update that didn’t go well. Like many of you, I can be playing an album and it will just stop - and for good measure there’s some hassle in getting it going again. My hardware unfortunately doesn’t support JPLAY (I tried and communicated at length with Marcin at JPLAY). I’d need to send in my units to T+A for an upgrade to their G3 streaming client architecture. Sigh. For those curious, most users report that JPLAY sounds significantly better than Roon - there’s a fair amount of discussion on this at audiophilestyle. Regarding specific tracks being affected - it seems likely that there are a multitude of servers involved and that we’d be accessing different ones depending on our location and time. That we’d have different experiences on a specific track isn’t surprising given how much traffic they must handle globally. In any case - a cluster that will hopefully be resolved soon. I’m not ready to go back to Tidal for a variety of reasons. |
