Large Library

[Arindal]

@Andrew_Webb

Why doesn’t Roon just let us mark them as “don’t try to match this”? Wouldn’t that solve the problem in one fell swoop?

It might solve the aspect of roon trying to find matches with sets of metadata over and over again.

But from my understanding of roon´s algorithm it would not solve performance issues as a lot of unidentified albums even if they are left alone by identification would still pose a significant amount of computing load on the local roon server as everything related to them has to be crawled and compared for all browsing operations.

But I might be wrong.

[anon77144803]

Not sure that is true at all. I don’t recall seeing any such thing mentioned. Only that it will be repeatedly looking for metadata for unidentified albums when it runs its lookups which is at intervals and not all the time. This process is known to be heavy on the resources. Tbh so little was mentioned about this in that post I think a lot are jumping to conclusions on slowdowns.

This is the only mention of it and it’s still vague.

Do regular (daily) restarts of roon have a negative impact?

@Joachim_Herbert, We’ve taken time to look through available diagnostics and reviewed previous cases concerning ongoing poor performance. There are always ongoing efforts to debug and improve Roon, and at times, you’ve encountered known slowness related to search indexing or other processes that we have improved. But we need to set expectations and limits concernign library size and, more importantly, the breakdown of the content within the library. The common factor across all of your poorly…

[tripleCrotchet (Tony)]

@connor

This is the reason Roon’s backend services like audio analysis spin endlessly. Anytime you make a change to your library, Roon will attempt to identify the upwards of 150k audio files that are not officially released or recognized music.

I had missed the above referenced thread. Was there ever any confirmation about this? My commonsense interpretation of that quote is that any library edits will trigger an attempt by roon to identify unidentified albums in your library. Doesn’t look vague to me at all but of course it may not be what happens or needs qualification.

The reason I ask is that on occassion I deliberately unidentify, identified albums. This is mostly with Classical but also Pop/Rock as well. The main reasons are where roon misidentifies works with more than one catalogue number, gets the multi-part hierarchy wrong or gets the track sequence wrong. In these cases I find navigating the unidentified album with a few manually added tags a lot easier than the identified version. Of course, now I have forgotten which albums were deliberately unidentified and which couldn’t be identified because I never had the sense to add some kind of tag.

It never occurred to me that an edit of a single album could trigger a general back-ground library process.

[miguelito (Miguel Barrio)]

After all these years… ARC is still crashing!

[Norman_Spector]

Pleased to report that ARC is now working perfectly for me: with my iPhone 15 Pro mirrored to my MacBook Pro 2021 running iOS Sequoia 15.2 I am able to download music for offline listening from my large library almost instantaneously with one click and no crashes cc @connor @benjamin

[miguelito (Miguel Barrio)]

I had a period of a month where it seemed the crashes were resolved and I had a great time listening with ARC. Then the crashes restarted - slightly less brutal, it would stop playing but the process was still there. Upon putting ARC back as the main app it would reset to the home page. Strange.

I have move from a NUC10i7 to a NUC13i7. Because ARC has to resync as the server effectively has changed, I have not had a crash yet. We shall see.

[birban59]

I’m almost afraid to post this, but ARC seems to be working for me now. Two things changed that may have aided the situation.

I moved my Roonserver over to a Linux server I just created. When I did that, I just went from scratch on my music library, allowing Roon to rebuild it. It occurred to me that I’d been passing my library around from install to install since I first started, years ago. I thought maybe starting new would help clean things up a bit.

Additionally, I have a friend who got his roon to start running by upgrading his NIC card. At the same time, he rebuilt his library on a new installation.

I’m certain it didn’t have to do with moving to Linux, or my friends would have been working before. So either the library rebuild did the trick, or my NIC on the new server is faster. It is rated the the same speed as my old one however, so I’m leaning toward the library rebuild as the fix.

My library is bigger than it’s ever been, 40,000+ LPS, over 1/2 million tracks, 16 TB. I am tentatively overjoyed that it is now working, with the big library.

Going to be so ■■■■■■ if it stops working after this post though.

Peace.

[SandsOfArrakis (The Spice Must Flow)]

I’ve always rebuild my Roon server from scratch after changing hardware. And ARC never gave me any problems. I only have to rebuild a handful of playlists. But that can be done in 10 minutes tops

I personally don’t really care about playcounts etc. When it comes to Roon’s recommendations and mixes, they are the same on the new server compared to the old one.

My new N97 based little NUC Roon Rock(s) my 96k track/7.4k album libary with ease. (82k local tracks, rest Qobuz). 3 endpoints at home and Roon ARC on my iPhone.

I have a feeling you might be right about Roon issues with a restored upon restored server reinstalls. A fresh start sounds like it may be the solution indeed.