Core: Ubuntu Linux Core i3 / Roon 1.8 build 778.
Client is MacOS Catalina 10.15.7 running Roon 1.8 778.
Network Details (Including networking gear model/manufacturer and if on WiFi/Ethernet)
Wifi & switches / Ubiquiti
Audio Devices (Specify what device you’re using and its connection type - USB/HDMI/etc.)
USB → Schiit Bifrost 2
Description Of Issue
Very regularly, although not always, if I browse and pick “Play Now” for an artist I get an error saying Tidal isn’t available and limiting to local library.
However, if I pick an album from that artist and “Play Now” it plays that album, and then of course switches to Roon Radio or whatever and starts playing other artists. But I just want to play that one artist and various songs across multiple albums.
Please accept my apology for the very delayed reply . I was hoping this wouldn’t be the case - we’re still catching up with all the open threads.
Around the time you posted, our Roon Radio services were down. Tidal has had some issues too. I was wondering, is this something you’re still experiencing? We’d love to help
Well, this is a problem which went on for weeks. Lately I’ve given up playing artists and just switching to albums, because it doesn’t work reliably enough.
Anyways, I just test it now (8:15pm Pacific) and it worked for the first few artists and then…
Editing to add: For some reason Roon + Tidal really does not like John Coltrane. Almost certainly will cause this bug to happen. What is worse is that Roon always ends up picking up my wife’s Harry Connick Jr. library instead!
Can you please reproduce the issue, note the exact local time + date + artist/track with the error then use these instructions to send us a log set for review? Thanks!
Hate to be annoying @rebeka, but it’s a week since I sent @noris info and haven’t heard back. Just so we’re all on the same page, this ticket has now been open for a month.
Apologies for the delay on this and thank you again for sending the logs over. We are checking with the QA team regarding your case and as soon as we have more info to share, we will let you know, thanks in advance for your patience here!
Apologies for the delay here! I spoke to the team regarding this one and made a few changes server-side, can you please confirm if you’re still seeing this issue at the present time? Thanks!
Did a quick test and it actually worked! So yeah, that’s a huge improvement. Will try again a few more times over the next few days and let you know how it goes.
. I was hoping this wouldn’t be the case - we’re still catching up with all the open threads.
. The reason you haven’t heard back from 