I have split your post into it’s own thread so that I can better assist you here. Prior to reviewing diagnostics, we require some more information regarding your setup, can you please let me know the following?
What kind of Core are you using and what are the specs for it?
How does your network setup look like? What is the model/manufacturer of all your networking gear?
Does this same issue occur across multiple endpoints or just one one zone? What is the model/manufacturer of the endpoint(s) in use?
Is this issue affecting both local and TIDAL/Qobuz content or just one and not the other?
Small Green Computer sonicTransporter i7 (Kaby Lake) Roon DSP only server (Core)
This is a generation old and the site doesn’t list the specs of discontinued models, but here are the specs for the current offering…memory and storage are the same (per my memory); the processor is the i7 not i9; otherwise the specs are identical / similar.
Enclosure: Fanless solid aluminum case (completely silent)
Thanks for providing that above information. I have activated diagnostics mode for you account and what this action does is automatically upload a log set to our servers for analysis. I’m reviewing logs now and I do see some interesting clues:
You are getting quite a few Name Resolution Failures. These can be due to your ISP provided DNS servers and I would recommend changing your DNS servers from the ISP provided ones to Google DNS or Cloudflare DNS. Can you please give this a try on your Orbi router and let me know if it helps?
It appears that your Rendu zone was dropping out mid stream and losing connection to the Core. Can you confirm if your Orbi firmware is up to date on the newest firmware? Sometimes I have seen Orbi updates resolve Roon issues, so I would double check this aspect.
Can you confirm if the dropouts only occur on the Rendu zone? If you try outputting to the SonicTransporter’s “System Output” zone, do you experience similar behavior? Even if there is nothing connected, it should be useful as a data point as the track would abruptly stop playback.
Do local tracks exhibit this behavior? You mentioned this affects both TIDAL and Qobuz, but if you have any locally saved tracks, can you check to see if they are also affected? This would help us distinguish if there is an issue with the external network connection or the internal network connection. If you need a few sample tracks to load up into Roon, you can find a few on the 2L Test Bench.
@noris At 4:03 pm and 4:04 pm Central Time I got Playback Failures for Tidal (only). Qobuz is playing without issue. When I tried Tidal again at 4:35 pm I once again got the message “Too Many Failures” “Stopping Playback” with Tidal. Qobuz, once again plays fine.
Did you update the DNS servers yet? I would give that a try to see if it helps.
I’m taking a look at the new diagnostics from your Core and noticing some strange traces, I will ask QA to review but it may take some time to reach their queue. Do let me know if there is any change after the DNS servers are updated.
@noris This should not be about DNS servers, though I will change them if the problems continue. There are no dropouts on any other service I am using and diagnostics on my end (of the network) show no issues at all.
I can log into my Tidal Account directly but not via the Roon Settings > Services Tab.
The message I receive is “Bad user name or password”
As I wrote above, I am able to log into Tidal directly, without any issue.
Please explain why you believe a Login Fail (via Roon) is a DNS issue? Thanks.