Roon Running Very Slow, Lag Moving between screens

[connor]

Hi @Duncan_Andison,

You’re correct and we’re working to improve both the experience of support and the perception of the onlooker of Community. @Suedkiez is correct that we’re a small team undergoing massive transition to better support a growing user base. These promised changes have yet to come to fruition, but there is enormous movement behind the scenes. Here’s where things stand in your case:

The symptoms you’ve reported can emerge from three mechanisms in the context of the current public builds of Roon - the first is a known vulnerability with the Remoting protocol for which we’ve been development improvements. When inquiring about Play History, it was in pursuit of evidence that you were encountering this issue, although it was not a direct A/B test. This fix is undergoing testing over in Early Access - if you’re interested in moving your Core to the test branch to see if it remedies these performance issues in your own environment, please follow these steps.

Neglecting to post an update on this thread was my failure - not out of malice of oversight, but simply the volume of work requiring my attention. For that, the team apologizes, but gives our assurance we’re not unaware of the issue nor choosing to underserve our users. Behind Community, there’s a concerted and professional effort to triage technical reports into actionable steps for developers so the product can improve. Our users deserve to know when we’re working on problems that affect us all - response time, and more importantly, response efficacy, are something we aim to improve.

Some more notes to pass on from diagnostic reports:

1. Your subdirectory taxonomy and the ratio of tracks to folders within is taxing RoonServer’s indexing process. That’s a verbose way to say that you have a large number of tracks stored in places where RoonServer is only expecting 10-20. See this post for more clarity:

@connor

Roon expects subdirectories to be loosely structured according to a general music taxonomy, something similar in ratio to Artist - Album - Track. While flexible in its handling, Roon will currently struggle when a directory is taxonomized too far outside that expected structure. To give an example, a single folder containing (possibly hundreds of) live performances of one jazz standard by one artist across two dozen albums isn’t a far-fetched taxonomy. However, under certain conditions, building that directory:subdirectory ratio can bottleneck Roon’s backend processes.

This probably is not the single cause for your issues, but it’s likely contributing. If you have “track dump” folders containing hundreds or thousands of artists, it might be worth subdividing them in some way.

2. Network connectivity. RoonServer is noting connection refusals with the iPad, preceding dropouts of that Remote and Zone. Changes coming in Early Access might also help with this, but variably. There are prebuffer timeouts with Qobuz in logs - this is an upstream connectivity issue likely unrelated to throughput and network speed, and more likely resulting from network filtering or DNS issues in the router’s connection to Qobuz.

What happens if you sign out of Qobuz on the ROCK and play only local music?

3. We don’t have firm evidence you’re experiencing the issue for which we’ve just released a fix in Early Access. However, it’s quite likely a contributing factor. This fix will be released to the public build of Roon soon, if you don’t want to switch to the test branch.

That’s all I have at the moment, unfortunately. Hopefully, these notes provide some context and leave you feeling supported, not abandoned.