I have rebooted multiple times. All my local content is playing fine. I also confirmed i can access and play Qobuz directly through their web player. It was working fine before christmas and nothing has changed since then
Thanks for the hint! Tried this and also cleared my cache to be sure it was starting from a clean state. No luck. I get the album info and art, but when i hit play the progress bar just sweeps right and left (lighter blue color on Roon’s dark background).
It worked so well before Christmas and the only thing thats changed is the date?!
If logging out didn’t work, perhaps ‘disable’ on the same screen would work. If this also doesn’t work I would suggest logging out of Qobuz and changing your password through the Qobuz website, then attempting to log in again. Apologies if this seems convoluted and unnecessary, you’d be surprised how little changes affect the Roon Core.
Just to confirm here, is the SonicTransporter or the Macbook acting as the Core here? If the Macbook is acting just as a Roon Client (while the SonicTransporter is the Core), is there any change in behavior if you temporarily host the Roon Core on the Macbook?
I would first make a Backup of your Roon database and then try setting the Macbook as the Core by opening the Roon App on the Macbook going to Roon Settings -> General -> Disconnect -> on the "Choose your Core" screen -> Use this PC.
Thanks all! I will attempt the PW reset as suggested. Noris… the MacBook Pro is the CORE. The STi5 is the client where i host the actual music files… i.e. it is direct attacthed storage, connected to my MacBook.
Wow… this is quite stubborn. Still no luck. Disabled, changed pw on Qobuz, exited Qobuz to eliminate any interference, back into Roon. changed pw there… still the same silence with the progress bar strobing back and forth and all the album art/etc, like i’m a normal subscriber?
If you navigate in Roon to Settings -> General do you see the SonicTransporter listed as the Core or the Macbook?
If the behavior is still the same after trying different quality versions, the follow-up step would be to take a look at logs. To make sure we have the proper information to analyze, please try reproducing the issue and note the exact local time + date + track you experience this behavior with. Afterwards, please send me a copy of your logs via Dropbox / Google Drive / Send.firefox.com by using these instructions. Thanks!
Getting the logs over the SonicTransporter is a bit trickier than getting them from the MacBook in that case. Let’s go down this troubleshooting avenue first to verify if the behavior is Core-related or Account/Network related:
You can only have one active Core at time, but you are free to un-autorize and re-authorize different Cores as often as you’d like.
This is good, but unfortunately this specific log file doesn’t show what happens when you play Qobuz tracks. There should be an additional 19 log files in the same folder you found the first one, can you please upload the rest of the logs?