James_I
(The truth is out there but not necessarily here)
1
This isn’t a support request because it’s not bothersome enough to try to troubleshoot. But just in case others are seeing this, you’re not crazy:
—Go to Live Radio.
—Click a Radio Station.
—Click Play.
—Roon says “station does not exist” (paraphrase, I don’t recall exactly) and doesn’t play
—Hit “back”
—Click on same Radio Station again
—Click “Play”
—It Plays. Sometimes it requires one or two more backs and forwards to play.
Roon just seems to lack confidence sometimes?
Similarly, I’d like to see Roon keep trying a radio station once play has been clicked rather than to stop the stream and just sit there whenever the stream is momentarily interrupted. Live Radio just seems to die sometimes and need play to be reclicked for no good reason.
I too confitm this behaviour for, im case belgian radio stations.
And indeed, although it happened sporadically before, it is unfortunately consistent for the last week or do
Dirk
Each morning I check on the thirty odd flac streams that are out there. (I don’t use Roon for this, instead I have a Linux script.) It is quite normal for one or two of those, no more, to fail to connect in the first 4 seconds (my default) first-time. They generally do on a retry.
FWIW, I have noticed no change in the last week. As I said, Roon not involved.
James_I
(The truth is out there but not necessarily here)
10
Well, Roon is involved in the message it pops. What if, every time you called someone that didn’t answer, instead of voicemail you got a “called person does not exist” message from your phone?
Roon could simply say “waiting for stream…keep waiting?” [Yes][No]
Roon’s error messaging is often pretty misleading…not helpful for troubleshooting. This is a great example.
Sorry, I should have been clearer.
What I meant was that Roon is not involved in my tests. As I’m not seeing the issues there, the conclusion is that the issues must have something to do with Roon.
James_I
(The truth is out there but not necessarily here)
12
Ah, got it. Yes, I seem to reach that conclusion a lot.
Personally, I believe there is a serious resource leak issue of some sort where Roon slows itself to non-functionality over the course of hours/days and has to be restarted. Given how long it takes to start up again, the restart requirement is too frequent.
This problem has improved for me over the past day or so.
Edit: Nevermind, it just occurred again with Radio Paradise - Mellow Mix. It really doesn’t seem to matter the station. It’s as if the db that is the list of radio stations is having trouble responding quickly.
WBUR (Boston public radio) seems to regularly have the issue. As in I feel like every time I try to start it, I get that sequence of issues followed by success.strong text
Same here as well, looking at the logs it looks like Roon cloud is saying the stream doesn’t exist a few times i.e until you click out and back into the stream and then it finally comes back with a 200 OK.
In some cases it has taken 5000 mS to come back with a 304 which is “address hasn’t changed, use your cached one” quickly followed by a 404.
I reproduced this this morning with WBUR. I had previously connected via a direct linux connection (interestingly, it took two goes).
Repeated connections were then OK. So, station stream active. As far as I can see, there is no redirection or relay.
Next I tried Roon, and got the error. Tried a different station, then returned, and all OK.
Rebooted my server, and everything still OK. Certainly seems a backend Roon problem.
@dylan, anything changed at the servers? I have logs if you wish.