I have the “endlessly spinning circle” issue. It’s not giving the metadata message like other people have experienced; rather, it just seems to keep scanning even though “Adding music to library” is complete.
The Roon Core is running on a NUC10, reading data from a Synology NAS. Everything is hardwired (not using WiFi). Very large library.
I had a similar issue, I ended up sending a log file to Roon who identified a corrupt audio file in my local library. Once I zapped that the issue was sorted.
@Mike_O_Neill - I’ve had this install for years, so it’s not new. I have a definite sense for how long it normally takes - this time it’s an issue. Thanks as well.
@Graham_Getty - I’m guessing I have the same issue. Does anyone know if there’s ever been a post or support article where the Roon team explains how to look at your own logs? I’ve looked and couldn’t find, but may have missed it.
If you go to:
Left hand side 3 horizontal lines →
Settings →
Library
There is a Skipped files log that you can view that may shed light on your issue.
I hope that helps.
Interesting in that I think DJD (the original poster on that thread) may have had a “similar but not the same” issue as ours (though I’m not sure, of course).
The end result of an endlessly spinning circle is the same. However, DJD was getting the “Metadata Improver: Halted” message. Whereas based on the screenshots you and I don’t get that at all.
Not sure it helps us just yet, but could be important to know.
@MamaTried - thanks for the pointer. I hadn’t ever looked at that part of Settings, and it was interesting.
Unfortunately there wasn’t a new file listed that could be causing the issue, so it’s something else. That said, I did find out about some corrupt files on my hard drive that I didn’t know about, so now can fix. So thanks for that!
@support - can you please give @Rantanplanary and I a quick “here’s what to look for in the logs” so we can go in and see if we can find the file(s) that are causing the endlessly spinning circle?
If there’s already a knowledgebase article that explains this, apologies that I couldn’t find it. I’m thinking this will be helpful to multiple people in the future as well.
Figured it out through trial and error, removing and re-adding files that had been added when it started happening.
@beka If you could file a bug report, the offending file had an emoji in the file name. FWIW, replacing it with a different emoji fixed it, so it’s not all emojis.