Roon stops playing music when adding new music to the library

I waited far too long for those words to be written :grin::pray:

But thank you for your service :grin::face_with_hand_over_mouth:

3 Likes

Possibly as it doesn’t show in logs. All you see is the metadata task running if you examine those and the issue only occurs when that runs.

I’ve never had the current queue issue with it adding old history to it either or albums being split due to the various artists issue, but that doesn’t mean the problem doesn’t exist because it doesn’t affect me. Also the current Sonos bug exhibits similar behaviour also.

2 Likes

Strangely I didn’t have the history bug until I read about it widely on this forums. Then it happened that day (and the next), and I understood them why people were complaining about it as it completely ruined the current music listening session (for us album only listeners) and it was really frustrating. Thankfully Roon fixed it within a few days.

I have also never had the various album splitting bug, at least that I have noticed.

This bug/issue only affects me sparodically, but it impacts other users more incan imagine how annoying it is to them.
It’s fair to say that many of us add a lot of music to our library so this could happen more often.

1 Like

Hmm, I’m starting to think that this is what I initially suspected. A bug in the latest software update. I never had any issues for months and months, then suddenly it just started happening frequently. Maybe it is time for all of us to start opening tickets to try and figure out what is going on…

@CrystalGipsy already has one open ticket relating to issues with performance after adding music that many of us have added information too (around the Metadata update process exhausting one or two full CPU threads impacting performance)

My own issues are sparodic when adding music and it’s rare that music actually stops playing (though it happened twice recently).
Create a ticket and I am sure other’s will add information and anecdotes to try and help get this investigated as it needs to be

1 Like

Just wanted to support you and say this is a common issue for me. I have a daily playlist that syncs with tidal, and when playing it, I’m often adding many of the songs to my library. If I start adding more than a few to my library in succession, Roon usually stops playing, audio sources show not found for a minute, eventually it all comes back to normal but can take between a minute and maybe 4-5 minutes and I typically have to hit the play button again to get the music restarted. It’s really annoying but I know it’s one of those mystery problems that doesn’t seem easy to troubleshoot. I live with it and try to remember not to add multiple songs in quick succession.

I suggest that these Issues are linked or related. Music stopping. Endpoints losing contact. High CPU usage. Other threads on instability.

There are a lot of these threads. I suspect Roon knows there is a central issue but the remedy may be overwhelmed by technical debt.

My gut feeling is there is a fundamental inefficiency somewhere in the database. I can see this when I run focus queries involving many objects with Roon tags. Results take several minutes unless instead Roon has to be restarted. This may be why Roon doesn’t support and/or logic for tags…maybe they’ve used it and the database bottlenecks.

So then when the database is doing anything significant, it’s vulnerable to any other activity and is easily destabilized. For some this slows Roon down. For others it knocks out network connections and that also stops the music. I can see when Roon is burning a single CPU core at over 100% and that is exactly when Roon is slow or unstable.

There may also be library content that exacerbates the issue. Unidentified albums or lots or Roon tags. Or maybe even some long standing unidentified data corruption. Those without such factors may still have the same issues but not detect them due to having a different library.

So when someone says ā€œI don’t have that problemā€ it may really mean ā€œthat problem doesn’t affect my library to the point of instability.ā€

It would just be nice to know Roon is on this.

4 Likes

Does Roon have an archive of previous versions of the software?

I’d love to go back about two months to when I never had any issues. I don’t have prior installers because I’m on ROCK and it handles the downloads and installation. Sadly, it doesn’t look like there is any rollback features in ROCK or Roon either…

No, there is no rollback possibility. Think I’ve read on this forum that some or at least one has several Roon setups. One gets the updates and the others stays on the version they are happy with.

Well they gave me inconclusive answer the usual we can’t repeat it even with a copy of my database. I know it’s not a hardware limitation as I have put it in sort test for hours burning network, disk and cpu and it’s doesn’t drop a beat or throttle itself. I think it’s a bottleneck of its own single core activities, something they think they have optimised but hasn’t at all it’s just moved inefficiencies

I use tags but i don’t have a huge amount of them, I have 9 unidentified albums. I guess these are tried to be identified each time anything changes in the db this can be metadata updated, addding new files, losing streaming connections or it’s restarted as has been said by support. This is something they can address if they chose to.

The fact this is now also happening to a set of Sonos users as well after playing to them for a period of time shows something is off. This isn’t triggering any updates just core proceed gets stuck.

Also LMS which I use also will max out a core when doing library updates but this doesn’t stop the program from doing its basic task of browsing playing music etc or losing connection. This phenomenon is purely Roon. Using it at full pelt is fine as it should be done quicker but at the cost of the ability to do anything else is not good.

You might be onto something with the ā€œunidentified tracksā€ā€¦ I’m a Psytrance DJ and have a lot of music that is not common and isn’t listed in big music label’s catalogs. I’ve noticed that whenever the music cuts out, that the progress indicator is going and when I click on it, it says ā€œIdentifying X of Y tracks. Z identified.ā€ It’s usually very large numbers like, ā€œIdentifying 23 of 89 tracks, 1 identified.ā€

Have a similar situation with my old collection of approx 1K of badly tagged MP3 files. I suspect Roon to continiously trying to find and update these , which will not happen and i will most likely not take the time to add more data to them either …
I have now moved these MP3 files to a separate wathc-folder. A solution (mitigation) could be that Roon provided an option to turns off the metadata search for a specific (watch) folder.

All my recorded DJ sets (an those of others) are in their own folder, so that would likely work for me too.

BTW, I just tried to tell Roon to prefer my own Metadata in files and now my entire library is being rescanned/imported. I’ve got a bit over 1/4 million tracks and after 3 hours it is only 10% done… Trying to play anything now doesn’t really work. Hoping this isn’t going to take two days to finishing updating the database… Just an FYI and warning to others.

Sounds like a good idea - why not post it in Feature Suggestions ?

Yup, this is by design - and Roon tells you that it may take some time…

Yeah, I saw that but figured ā€œsome timeā€ meant possibly 3 - 6 hours… not 2 - 4 days.

This has been suggested before. It must be in a feature suggestion by now surely? However, it is a workaround for an issue that needs fixing. The extent to which unidentified music is part of the issue is unknown.

ā€œSome timeā€ā€¦ It’s now TEN DAYS LATER and still going… I think I would have been better off reinstalling Roon and importing all my music again from scratch. It should not take more than a day to process a quarter million tracks. MediaMonkey does it in 7 hours on similar hardware and that is going across a SMB network share while my RoonCore is on a NUC with local PCIe x4 SSD.

Roon is completely unusable while this process is happening… It will play one track, then several MINUTES pass before starting the next track. Same thing when you click play on the interface, several minute wait. Last night I tried to play some music on Roon, music didn’t start, so I started playing music with another app and fell asleep to the music. I was woken up by Roon suddenly starting the playlist I clicked play on HOURS earlier. This is with all the library settings set to ā€œthrottledā€ by the way.

If RoonCore cannot process imports and be functional at the same time, maybe there could be a ā€œpreprocessorā€ that people can use for large libraries to process music off the RoonCore and then that preprocessed information could be imported quickly to the system?

Throttled only affects tracks analysis for dynamic range and waveform creation. The metadata side isn’t configurable and uses one core only ans does all of Roons processes so it will kill it if your machines single core speed isn’t all that. The more unidentified tracks you have which I believe you said you have DJ mixes are likely to slow it down as it attempts. Your library if I remember is v large for Roon. Something it’s really not good at is music not in its databases. Even when it does finish you will get in constant slow state when adding new stuff as it attempts again and again to get metatdata for stuff that doesn’t exist. It’s a really poor design for anyone with non standard metadata. I don’t think Roon is the correct choice for your collection. I would look at something else that doesn’t care about matching it.

What I’m hearing you say is… ā€œRoon isn’t good for music that isn’t popular.ā€ The mere fact that the the library is managed with the same (single) core that is used for playback is a DESIGN FLAW, and should be fixed. I’m so tired of being told, ā€œIf doesn’t work, don’t use itā€, rather than Harmon fixing the problem or at a minimum acknowledging it.

Remember, this entire thread and problem started after the December update and no one has been able to provide a way to rollback to the August 2024 release that did NOT have these issues. My support ticket for this issue has not been updated in weeks.

As an attempt to solve the problem, I’ve already moved all the recorded DJ sets and live performances to another directory and excluded them from Roon’s library. That actually is what triggered the massive reloading of all the library and started the ā€œapplying library settingsā€ process. So far this has NOT solved the issue and wouldn’t explain why so many other people are having issues as well. I’d think that the classical music and bootleg collectors would be getting hit with this problem if it is triggered by the inability to identify tracks.

If Roon cannot handle EDM music with their current lookup provider then they should get a partnership with MusicBrainz, Beatport, or SoundCloud, all of which have metadata for EDM tracks and albums. However, that really feels like a separate issue, or at least it should be… Crippling the playback for all music because metadata can’t be found is a serious BUG and not an excuse.

We also know that Harmon is collecting all the metadata from our libraries as it states this in their privacy policy. If they aren’t using this metadata to help identify other’s tracks, that is pretty silly. If they are going to invade our privacy, they might as well use that data to help identify tracks/albums for other users of their service when not available in their primary metadata provider.