I have enabled diagnostics on your account so our technical staff can get some more insight into what’s going on here. The next time your Core is active a diagnostics report will automatically be generated and uploaded directly to our servers
Once that’s been received, I’ll be sure to update this thread and pass the diagnostics over to the team for further analysis.
The TIDAL error seems to have gone away now. However, the Qobuz login error (see pic above) is still there. Hitting “Retry” a few times clears it, so looks like a timeout of some sort.
Same here, TIDAL and qobuz both fail. Music from SSD plays flawlessly. LUMIN app also works perfectly fine with both, TIDAL and qobuz. The fault is clearly with ROON.
Qobuz issue: times out and shows the message I posted above. After a short while it does log in and if I hit Retry the message goes away and all is fine.
TIDAL issue: Every Roon Core restart requires that I re-autheticate via the web interface. It does not remember the authentication. Moreover, I need to log OUT of TIDAL in Safari, then log back in, for the authentication to happen.
I reboot my Core every day in summer due to thunderstorms and potential lightening strikes.
As It restarts I have also been noticing that Tidal does not auto connect as it used to.
There are currently issues with one of the big internet undersea cables to Africa which I suspect may be involved. The other option is that some streaming services are “saving” bandwidth by dropping HD Resolution on videos eg Netflix. Is Tidal doing something.
Once logged in Tidal works perfectly.
There is a lot going on in the world at the moment !!
as a next step let’s try to refresh RAATServer to see if this helps:
You can generate a new RAATServer instance on your device by following these instructions, but please be aware that this will reset your Roon Settings -> Audio Tab to factory settings and I would advise making a backup of any custom DSP settings you have: