What’s happening?
· Other
Describe the issue
Two Tidal playlists (from Soundiiz) not syncing into Roon
Describe your network setup
Roon core wired
· Other
Two Tidal playlists (from Soundiiz) not syncing into Roon
Roon core wired
Do you mean they are not syncing from Tidal to Roon? Did you do a manual sync of Tidal? Look at the Tidal app and see if they are there.
Hi @RobOK,
Thanks for writing in to us about this problem. I have the same questions as @Jim_F. Once we have those answers we can proceed with troubleshooting!
Yes, I though by writing “Tidal playlist” it was clear , I’m not sure how else to say it, here is more details:
Thanks!
It seems to me, Tidal is seeing something different about these playlist from your normal Tidal playlist. Maybe because they were created by someone else, IDK.
A possible work-around might be to create a new playlist in Tidal and add this playlist to it. Then, see if it will sync with Roon.
Or, maybe do something similar in Spotify before sending to Tidal.
Not a bad idea Jim, thanks! I won’t have time for a few days.
Hi @RobOK ,
Is there any change in behavior if you try to log out/back into TIDAL via Roon Settings → Services? What are the names of the affected playlists? We can enable diagnostics to see if Logs are displaying any errors specific to those playlists.
Sent in PM
Hey @RobOK,
In the meantime, we also wanted to check in and see if @Jim_F’s above workaround made any difference in behavior?
We’d be curious to know if the playlist source plays a role in the issue.
Jumping ahead, I created a new playlist (called “This is a new playlist”) in Tidal and added three songs, it showed up immediately in Roon. Check.
Following the Jim-F suggestion, I created two empty playlists in Tidal and used Soundiiz to transfer songs into these new, empty playlists. Like the original problem, they are NOT showing up in Roon. Very strange. I will PM a screenshot.
Thanks @Benjamin – this seems like a weird edge case, it’s probably not worth Roon developer time if it does not fix any other problem on your end. You can go ahead and close this.
We’ve made a ticket in for our QA team to attempt to reproduce in-house, in which we’ll be able to investigate further.
I’ll go ahead and close this thread for now - thank you for the report @RobOK!
This topic was automatically closed after 19 hours. New replies are no longer allowed.