This indeed seems to be the case.
Hey @George_Herman,
We appreciate your follow-through in trying to pin down the issue here!
We can provide some of this! Iād like to re-share what @connor mentioned a few days ago:
Hereās an example of an unwanted stoppage in playback from your Roon Server:
Trace: [prebuffer] ready 652800/1920000 (34%) @ 0/391 sec
Debug: FTMSI-B ti/AAD1598E download status: FirstBlockRetrieved accessTimeout:True
Trace: [Living Room] [Lossless, 24/192 TIDAL FLAC => 24/192] [2% buf] [PLAYING @ 0:00] Cheese Cake - Dexter Gordon
Warn: [Living Room] [zoneplayer/raat] Failed to prepare AURALiC ARIES_G2 in 15000ms. Giving up
Warn: [Living Room] [zoneplayer/raat] failed to setup any endpoints..giving up
Info: [audio/env] [zoneplayer -> stream] All streams were disposed
Iād lean on what others have commented on in the thread - we need to investigate how to allocate additional bandwidth to your Roon Server machine. Not only is your server not properly buffering the track, itās also timing out on sending any playback information to your Aries G2.
My apologies if this has already been mentioned, and Iāve glazed over it - but do you run into the same issues no matter the output? Even from the system output of your iPhone or iPad?
This was a problem some else had mentioned as well. I had 30Mbps for the past 2 years, and never had any problems. I upgraded to 360Mbps in the last 4 months (per recommendations) and it made no difference. In addition, I measure 361Mbps with ping of 5 ms. This change made no difference on the problem.
This seems to indicate a 15 sec timeout. Is this a result of not receiving the information from Tidal or from the Aries not receiving the information?
Thanks!
We see on the third line that some buffering is happening which means the server is receiving data from Tidal.
Trace: [Living Room] [Lossless, 24/192 TIDAL FLAC => 24/192] [2% buf]
So I think the issue exists between the server and the Aries.
OKā¦ Iāll move the server and Aries on to the same switch.
OKā¦ when I moved the server and the Aries on to the same switch it played fine for more than 2 hours. Then I went to a playlist from Roon and it told be none of the selections were available from Roon. I tried multiple playlists and also tried individual albums. All were reported as not available. Then powered cycled the server and still had the problem. When I power cycled the Aries and it then worked.
Can someone look at what maybe causing this issue. It must be different than the one previously reported. Thanks!
George,
I do hope youāre moving slowly but surely towards a (wider) solution: it certainly looks that way .
Remember that Playlists created in Roon are attached to a profile, so what happens when you export a playlist from the Aries environment, rename it and actually re-import it into the environment which appears in all other respects appears to be working as expected?
I had said that I tried individuals albums and had the same error. The playlist I played was one that Tidal owned. I was playing one of the My Mix playlists under āWhatās Newā.
I also ran into the same problem as before last night.
Hi @George_Herman,
Thanks for the updates!
Were you able to test my prior question above? Any issues outside using the Aries device?
Are you still seeing unavailable tracks in your library? If you navigate to Roon Server>Storage, are your watched folders still properly synced?
What did you ask in the previous question? I have numerous different devices connected to the same network and havenāt experience any issues with them. The server and Aries are connected together using the same switch. These are the only devices on the switch.
When I said it gave me a message about being unavailable, it gave me this error on every song with it was on Tidal or local.
Iām currently moving the files over to a SSD from HDD. I should be completed this operation later today.
The move to SSD is complete. I still have to same problem as before.
Hi @George_Herman,
This thread has accumulated too many responses for technical support to effectively provide support. We need to start with a basic test, because throughout the responses, thereās no evidence RoonServer has yet established a reliable enough connection to the internet to 1) play back high resolution content from streaming services or 2) reliably process changes with Valence and metadata servers.
As an effective test, bypass this Audio SW-8 switch entirely. Connect your RoonServer machine and the affected endpoint directly to the main, upstream router via a hardwired ethernet connection. Then reproduce the issues youāre having with playback and weāll see what logs show.
We already eliminated the Audio SW-8 switch entirely. It had no impact on the problem. As I said at the start, this setup was working for years with no problems. The only changes I made was moving to a Google WiFI from Orbi, and increasing the AT&T speed from 30 Mbps to 300 Mbps. If you feel that this is a Google WiFi issue, I need to exact error that is being seen. I have 4 access points (Wifi router, and 3 WiFi points) connect via the Google mesh WiFi. There are laptops that are running Zoom, Youtube, and Netflix on the network with every combination of WiFi connections without any errors. This could very well be an issue that Roon is not handling errors from the Google WiFi correctly. Are there any known issue around using Google WiFi, As for connecting points via a direct connect, the distance is an issue,ā¦ and the reason why Iām using a mesh network.
I think I missed this earlier. I just rebuilt my DB, but I donāt see the playlists that I created.
How do I get those back?
By restoring a backup of your database If you have one available.
But if you want to find out whether the issue is caused by database corruption, I would wait. Restoring a backup will restore corrupt files as well and you will have exactly the same state as before.
I would first check for a while whether all is working smoothly with the fresh and new database.
Well, it seems that I have the issue as before. It seems to have stopped twice in less than an hour. Can you check to see if it is the same error?
This means you have ruled out database corruption as the cause of the problem. Assuming you did not restore a backup and tested it long enough.
I guess then it boils down to connection issues within your mesh network.
Iām sorry, but Iām only having problems with Roon. This means that you are not responding to errors correctly. I use the mesh for streaming all sorts of streaming services and donāt have a problem. I also have a Sonos system that uses Tidal and supports 5 zones that works without any errors.
The reference you sent me is I am having problems with Google Wifi, which I am not. Everything reports are working perfectly. The Internet and mesh networks are not perfect devices. They will get errors for various reasons. It is expected that there the certain errors that might not the be retried. This is normal and there is an assumption that the application would take to appropriate action. The fact that this stops in the middle of a song and all it takes is for me to hit continue tells me that you are not handling errors correctly. Can you give me the root (tcp/ip) error we are seeing on the Roon server? How do we go about addressing this error?
Dear @George_Herman
I am just a Roon user like you trying to get to the bottom of this matter.
Unfortunately, now I can only tell you that I donāt have issues with Roon.
However, I do know exactly this behavior as described, when Iām almost - not yet completely, out of the range of my WiFi network, in the garden.
I hope that support will be able to resolve your issue.