Hi Seth, I appreciate you reaching out to us about this!
I head up the Technical Support team at Roon and would be happy to give some insight into what you’re seeing and offer to help you get this resolved.
First, I wanted to address that pattern that you’ve noticed on Community when it comes to issues with Qobuz playback. While for a majority of our user base Qobuz playback works fine, there are definitely more reports that streaming Qobuz hi-res content fails compared to any other type of content. While this is true, it also isn’t unexpected.
Qobuz hi-res streaming is more demanding than streaming any other type of content and it means that the Core and the network need to be up to the task. Because it is more demanding it tends to expose issues in the local environment more than any other type of content.
When we start troubleshooting, though, we are careful to not make assumptions. We always ask for certain details about your setup and some common troubleshooting steps (rebooting, trying different endpoints, lowering streaming quality, etc.) because this ensures that we are coming at the problem with all of the necessary information.
We have regular meetings with both our QA team and our senior development team to review issues that come up and make sure that there aren’t underlying problems in the software and, when there are, we make sure they are tracked and resolved. Tracking and resolving these types of issues can only be done if we have all of the appropriate information.
Upon reading your post I went back and looked at the last couple months (Since July 1st) of “Qobuz Failures” reported to the support team. When filtering the results to only show reports since July 1st, we found there to be roughly 12 reports. Of those 12, only 6 of them were specific to Qobuz playback problems. 2 were fixed by resolving networking issues, 1 was resolved by switching from an underpowered Core, 1 was an account-specific issue that we are investigating, and the last 2 are still under investigation.
That’s not to say there aren’t issues with our Qobuz implementation currently — We have recently identified that there are some cases where tracks are no longer available from Qobuz (both in the Qobuz app and in Roon) but for albums in your library we aren’t properly showing the Unavailable indicator. We have a ticket in about this and our QA team is currently investigating this further.
To summarize all of the above: We investigate each report thoroughly, loop in our senior technical staff, and do our best to resolve customer issues either by making changes to our application where necessary or by helping to identify environmental issues.
I’d be happy to take a look into your specific issue, either here or we can take it private if you’d prefer, but ultimately the best way for us to identify the issue is to investigate your report thoroughly. I’m confident we can get you up and running one way or another
If you have any questions please don’t hesitate to reach out!