I recently installed Roon Server on my Mac mini and connected both my Tidal and Qobuz accounts.
I’m experiencing a playback problem in which many songs stop after approximately 30–60 seconds when played through Roon.
Both Tidal and Qobuz work perfectly when used independently, including playback through my Aurender W20 and dCS Rossini APEX. The problem appears to occur only when using Roon.
Both streaming subscriptions are active and paid, and I have successfully signed into both services through Roon.
Could you help me identify the cause of this problem? Is this a known issue, and are there specific settings or diagnostic steps I should check?
Diagnostic logs show Tidal’s API serving the thirty-second, low-quality MP3 version for requested content, which should only happen if you’re at a restricted account/subscription tier.
Our cloud account servers confirm that your Roon credentials are registered with Tidal as an INTRO tier account (free tier).
Qobuz, in logs, is returning a subscriber tier and playback seems to be proceeding as expected, although the last visible playback event was two days ago (“Rehab” by Amy Winehouse).
Please sign into Tidal outside of Roon and verify the status of your account, even if you’ve already taken this step. Double-check you’re using the exact same account in Roon. Then sign out of Tidal in Roon, reboot RoonServer, and sign back in after it restarts.
When you reinstalled Roon on this machine, did you fully delete the database and restore from a Backup, or just uninstall/reinstall Roon itself? Logs seem to indicate the current database is brand new or recently restored from a Backup.
Wanted to follow up on this. Have you been able to check your Tidal account outside of Roon, confirm that you are using the same login in Roon, and then sign out of Tidal in Roon, reboot your Roon Sever, and sign back in afterward?
We’d also like to know whether the current database was rebuilt from scratch or restored from a Backup when Roon was reinstalled, since that can help explain the behavior we saw in the logs. Please reply with any update when you are ready.
Please note, if we don’t hear back from you this thread may close automatically soon. If the thread auto-closes and you need further assistance, please submit a reopen support request via the technical support help form below and specify that the issue should be reopened. Thank you.