Metadata for some local tracks suddenly seems to have gone crazy. For some albums, tracks and albums titles are displayed in ALL CAPS. For some others, artwork is not read from local storage, displaying covers that seem sometimes random. Fortunately this does not happen with all albums. Forcing a re-scan on the storage location after modifying import settings does nothing. Is there a way to truly force a re-scan that will update all metadata?
Thank you for reaching out to the Roon Support team. The easiest way to revert any unwanted metadata changes would be to restore a recent backup saved - do you have any backups you’d be able to restore and test from?
Let us know how it goes, and if the issue persists, we’ll be happy to help further!
Unfortunately no backups as I had to redo the library recently because an unfixable ROCK meltdown which, well also was not appreciated.
“Force rescan” does not do that. My plan to do next is to remove the storage location, re-add it and hope that actually forces a re-scan. However, I do not need support to know that is the next step. However, I would love to know why “Force rescan” does not refreshes all metadata after changing the import parameters. Unless you mean for it to just look for new stuff. Then IT SHOULD BE NAMED DIFFERENTLY.
Did that before and again after your post. It chugs for a bit but I still see the same stuff. No change in the library. Will remove the location as planned then report
That did the trick. Removed the location, cleaned up the library, double checked the desired import settings, re-added the location, the let it process. Now it did something, re-scanned/analyzed.
Not sure that I would call this a solution - more like a workaround. The library was very recently created, so it makes no sense that it would decay like that. Also feels that just “Force Rescan” should have had the same effect as doing what I did.
Hi @vmartell,
Thanks for the update, and I’m glad to hear that things are working again—though I completely understand your point about this feeling more like a workaround than a proper solution.
You’re right—Force Rescan should have worked in this case, especially with a newly created library. It’s definitely unexpected that it didn’t have the same effect, and we appreciate you sharing the steps that got things moving again.
Please don’t hesitate to reach out if anything changes—we’re here to help.