Tidal login/playback problems

Just to add to the above post, this has also resulted in my being unable to play any of content to any zone. There’s no error message; just no sound and no progress on the playback line. This is for local content; Tidal playback simply skips through all the tracks stating that the track in not available on Tidal

Hello @thompo, I wanted to clarify that last post. So local content to system output isn’t working either now?

Hi @nuwriy That is correct, I was unable to play local content to any system output. Both issues were resolved by rebooting the core

HI @nuwriy, it has happened again. Same symptoms; items being skipped in playback, track loads from local storage but does not play. Also tested with Qobuz and the same error, so not related to Tidal as I originally thought. Please let me know if you need logs or similar to investigate further.

Hello @thompo, sorry to hear that. Does rebooting still resolve the issue? Also, are you still seeing the issue to all endpoints including system output? I’d like to collect diagnostics next time the issue occurs. If you could please reply here with a timestamp (in your local time) next time it occurs as well as the endpoint and track name, that would be appreciated. Thanks!

2 posts were split to a new topic: Core sign in issue

Hi @nuwriy. Issue arose again at 10:30GMT on 12 Nov. No luck playing from Qobuz, Tidal and from local storage.

Each time it is resolved by rebooting the Core. No luck playing to any endpoints, including local system output.

Hello @thompo,

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.

Thanks @nuwriy

1 Like

Hi @nuwriy , this has just reoccurred at 16:49 GMT on 19th November

Hi @nuwriy, I wonder whether you have had a chance to take a look at this? I have had four failures today (15th December), and had to reboot Roonserver on each occasion. This is now becoming a bit of an irritant.


Hi @nuwriy, I assume that all is busy with the next version of Roon, but I am still getting repeated failures which I have not had for the majority of my time with Roon (since day one!). I have another failure today, 29th January at 11:19 GMT.



@support @nuwriy I’m still having this issue with Roon 1.8 and haven’t received any reply to my pervious emails. I understood that diagnostics were being collected but feel that there should be a wealth of data by now.

I love Roon, and am a fan of version 1.8, but having to restart my Roonserver on a continual basis is trying my patience. In addition, I am also continuing to lose contact with my Meridian 218 endpoint. It’s difficult to understand if this is consistent with losing Tidal connectivity.

Please can you let me know either way whether this can be resolved. Otherwise I feel that I will need to start from fresh again and, having used Roon since day one (and Sooloos before that), that is not something I want to do.

Thank you for your response.

Hello @thompo ,

Sincere apologies for the delay in getting back to you here. I am looking over your Roon logs and I am noticing some strange traces here that might be related to your Roon database, can you please try to see if a fresh database also reproduces this issue?

  • Make a Backup of your current Roon Database
  • Exit out of Roon
  • Navigate to your Roon’s Database Location
  • Find the folder that says “RoonServer”
  • Rename the “RoonServer” folder to “RoonServer_old”
  • Reinstall the RoonServer App from our Downloads Page to generate a new RoonServer folder
  • Connect to new database (don’t restore)
  • Verify if issues persist

Hi @noris, thanks for your reply - much appreciated. I will do this today and then experiment. I will revert after the experimentation.

1 Like

Hi @noris. After 12 days of testing this and putting quite a load on the RoonServer, the Tidal login does appear to have been resolved. However, I’m still getting the intermittent drop outs in the zone that comprises of a Meridian 218 endpoint. I haven’t had dropouts in any other zones, Meridian or otherwise, although they are not used as much as the 218 zone. Any thoughts?

Finally, is there any way that I can extract any of the work that I did on my previous library or have I now lost that? Favourites, playlists, even listening history?


Hi @thompo ,

Does this behavior affect both Local and Streaming / Live Radio content or just one type and not the other?

Do other zones such as the System Output on your Mac Mini exhibit the same behavior?

Unfortunately, extracting pieces of your database are not possible, you would have to revert to a Roon Backup that does not exhibit this issue. If you don’t have a backup before the issues started to occur, then continuing with a fresh database is the best path forward.

Hi @noris , thanks for your reply.

Does this behavior affect both Local and Streaming / Live Radio content or just one type and not the other?

Yes, it affects both local and streaming content.

Do other zones such as the System Output on your Mac Mini exhibit the same behavior?

No, the Meridian 218 appears to be the only one that exhibits this behaviour.

Thanks for the response also on the ability to restore parts of my backup. Have made the decision to stick with this new database and a fresh start

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.