Roon 1.6 Feedback Thread

I put together my thoughts on the “perfect” :wink: now playing interface:

Definitely more than one way to do this stuff.

Mmm, it looks like another album view…

Not really what I would want for now playing but ok for a queue screen.

4 posts were split to a new topic: Sluggish performance since update

2 posts were merged into an existing topic: Roon Core chokes up since 1.6 (build 390)

A post was split to a new topic: Sluggish performance on trial

Just to add, Roon works for me much as it always has. It just works. I use a QNAP NAS Running Roon wired to my Meridian and Bluesound zones. It just works.

It seems to me, something must be wrong in the set up if it’s slow.

Hi @Chrislayeruk,

when you’re saying “much as it always has”, does that also mean everything is still as snappy as it used to be? Things work reliably here, too, but not quite as fast as in 1.5.

But unlike you, I use Tidal and Qobuz. Maybe that’s what causes the perceived sluggishness. Nothing dramatic, though.

1 Like

I think 1.6 is more variable in performance than 1.5, for me, but the extra feature of roon radio across Tidal lets me forgive it.

2 Likes

I really haven’t noticed any change in performance with 1.6 either, after the first week when the artwork was updating, though I only have a local library. Do you have sluggishness with local files? Have you changed DNS to 1.1.1.1 or 8.8.8.8 as this may help?

FWIW, I started using Qobuz when 1.6 was released. The Qobuz integration was amazing, but yes, everything seemed a bit sluggish and search in particular.

Well, I decided not to continue my Qobuz subscription. Interestingly, even though my subscription ended, Roon continued to query Qobuz in searches and search was still sluggish. About 2 days ago I removed Qobuz from Roon services. Not surprisingly, Roon search became a good bit faster again. I suspect the same is true for Tidal but have not tested that theory.

So yes, there’s room for improvement with Roon, but I also have very high confidence that the Roon team will continue to do that just as they always have.

1 Like

It seems just as snappy now for me. The only time I have issues is if my RAM 4Gb gets saturated and then a reboot of core fixes this. Not a daily occurrence either.

Occasionally I reboot my iPad app, but I always have done.

I only have Tidal and my physical library.

1 Like

These all seem to be similar issues.

I fear Roon has a performance issue they’re not fully comprehending yet. Not claiming “qobuz-gate” or anything, just that Roon is MUCH slower for me, very often, since 1.6.

I suspect this has to do with severe network load associated with certain Roon functions - I have noticed it with searching, but it may be more than one function or activity.

I have seen all of these happen in the past 2 months. Since I use Roon at two different locations, and in one location the network has only a single switch and that location performs better generally, and the other location has a few hops between switches, and that is the slower location, I suspect that Roon does some things that are very network intensive and is sensitive to networks that are not completely streamlined. That said, I can watch quite a few hi definition movies across the network simultaneously.

Rebooting the core or closing and restarting Roon helps. But I suspect that is not necessarily because it is a memory leak. My guess is that It is because closing Roon shuts down some process that is the cause of the slowdown. The issue returns the next time the process is triggered.

One thing I have been able to repeat: Do 5-10 searches in rapid succession. See if your processing speed takes a hit. It does not immediately return to the original speed and performance is affected for a hangover period. Tracks also appear to load more slowly at the same moment.

Interesting. This is my sad little setup, I have 100mbps AT&T fiber as it’s just me and I don’t do much more than stream Tidal or Qobuz 24/7. I have two low-power routers acting in AP mode (Netgear on 5ghz with the ROCK NUC plugged into it with devialet expert pro as the only client). My 2017-built unit is hardwired with what I think is CAT5 but the low voltage guys didn’t do it to spec, so the AT&T guys nor facilities management hasn’t been able to pinpoint the issue with the wiring, so I use WiFi. No dropouts. I was seeing packet loss but not hearing it on 2.4ghz, but none on 5ghz. There’s some a**hole running a hacked router nearby as I get a -26db 5ghz signal from him in my kitchen and a -30db signal when my laptop is six inches away from my 5ghz ap. Firewalla could be causing an issue, but honestly things got less laggy once I removed the double-NAT issue and let Firewalla handle what I hope could be considered security

I should note that a building-wide memo went out about the WiFi noise issue, but the highest I’ve seen my noise floor go is -88

I observe the exactly same as you do and also reported in this forum. I’m located in Europe, i.e. in France. Maybe, this could be a reason that Roon database access from overseas is prone to delays. Qobuz with other 3rd party software is very snappy in return of searches, not so in Roon’s implementation of Qobuz. I thought it improved over time, since the 1.6 release, but then again I get these long waiting for showing a search result or start of play of a Qobuz album or after skipping in the play queue of 10 or more sec.
Reboot of Core helps recovering, but only for a few new searches or new plays. Not sure if it is only Qobuz related as I stopped my Tidal subscription after 1.6. release.

1 Like

I could be wrong. Roon is a very complex technology that accesses local media storage, a local database, while at the same time streaming media to endpoints, accesses remote media storage, and accesses remote databases. From that standpoint I do not feel at all qualified to diagnose the exact cause of this. I do feel based on the correlation of activity to these slowdowns, that they arise out of some sort of congestion within Roon when certain features are accessed. I’ve been able to reliably duplicate the slowdowns with intensive searches.

Try 5-10 searches in 30 seconds to a minute and see if anything slows down for you. It may also relate to tagging, only in the sense that most of the time I’m doing searches it relates to bringing up objects - artists or albums - that I then tag.

FWIW I also experience inconsistent performance with 1.6 on a ROCK Core setup (UK) with no issues before. I’d say around 80% of the time it’s good enough (2-5 seconds for a search) but 20% of the time searches take forever (10 seconds - >30 seconds). This is particularly frustrating when just looking for a local album.

Edit: I use Tidal but not Qobuz

1 Like

I observe that same behavior as @HWZ since Roon 1.6.
Already reported some time ago.

Same problems as @dhusky, here in Denmark. I think the problems came with 1.6.
No issues before that.
No Qobus, Tidal only.