My goal since using Roon as a lifetime subscriber was to rip my CD collection and move away from streaming services. Things happened and only recently has this started to become a reality.
A few years later, and in a few days I’ll surpass 100k tracks stored locally.
Now I could just use Roon without logging into Qobuz (my remaining streaming service), but I want a more offline Roon.
Import local content, download metadata and DR analyse once. Cut the internet from Roon.
A few of Roon’s users, myself included feel some issues being reported of slow Roon servers, crashing etc could be contributed to by sudden whole library metadata updates.
While this ensures things are upto date, sometimes it’s not wanted nor needed.
Audirvana offer such a facility, called Origin.
I’m asking Roon to consider this.
I want to have Arc, but isn’t critical as I can operate alternative solutions for that.
Roon 1.8 is prime for this. I often rollback to 1.8 and find it a far more stable performer. Arc would be a cherry on the cake, but not a huge requirement.
Chime in with comments, but I wish to gain as many votes on this as I think Roon could make more money selling access to this type of service.
I’m sure that when I first started using Roon (2016) that the library metadata updates were supposed to happen overnight and not disrupt normal listening time. I may be mistaken of course but the solution is to make the updates scheduled in the same way local backups are. Current behaviour is either by design or a bug. Either way it is more desirable to fix it than split Roon into two versions.
I agree. They currently kick in randomly and when they do they make the system completely unresponsive as the whole processes maxes out the one core Roon uses. Why it manages to max out this is beyond me, why it becomes unresponsive again beyond me. The machine is accessible and usable for all other apps and services running on it. This includes other streaming platforms they all function as normal. So yes it’s definitely a bug and likely a result of when they have tried to optimise things but it’s had the opposite affect. I did have it occasionally when I ran Rock as well but never really looked into it. I am on different hardware now and just run Linux server now and it has the same issue albeit it’s random, happpened the other day and not since.