Hello @Arnaud_de_Fontgallan ,
Thanks for letting us know, we will discuss your case with the team and get back to you once we have discussed, thanks!
Hello @Arnaud_de_Fontgallan ,
Thanks for letting us know, we will discuss your case with the team and get back to you once we have discussed, thanks!
Thanks, I hope we can get a solution soon as this has been pending for a long time now and the files seem to have no issue
We understand how frustrating it is that this has taken so long to resolve. Thank you so much for your continued patience and cooperation. It really means a lot. We’ll keep you in the loop and let you know as soon as we have more information to share.
Hello, still no news ? This is becoming really upsetting… Also FYI, i discovered that when i have a slow connection, Roon ARC can’t play files from my library (not surprising given that the connection is slow) but it won’t play the files that are available offline neither, apparently it tries to read these files over the Internet instead of reading the downloaded version. I hope you can fix all this soon…
Hello @Arnaud_de_Fontgallan
Thank you for your patience while we checked with the team regarding your report. We have tried to reproduce the behavior on our end using the linked files, but we were unable to do so. Just to confirm here, if you remove the conductor tag entirely from the files, does the tag go away in ARC? As for the playback issue, can you please provide the time + date + track when this next occurs? This will allow us to cross reference diagnostics, thanks!
Hi, we’ve tried this already and it didn’t work. Also, to do this and see a result on the library I would need to remove the tag from all my files, and then add it again which on several 100 000 files would be just crazy. How can you explain that i experience an issue and you don’t see it ?
Please, at your convenience, reboot RoonServer one last time.
So far, Roon developers haven’t identified the event when RoonServer indexes/creates the tag through the tagging mechanism from logs. In the absence of a creation event, the only logical explanation for the origin of this Conductor tag is latent corruption at your RoonServer database level.
Conductor is a standard metadata field - its sudden appearance in the tag category is only explicable if errors have begun to accumulate during background indexing of the database. Roon checks for database corruption on-the-fly, thoroughly checksumming each object to validate unexpected changes. However, hardware failures or deeper latent corruption can go unnoticed until accumulation has become problematic.
Do you have a Backup of your Roon database? Try restoring your earliest Backup available, and then syncing ARC to that version of the database (you’ll need to disconnect ARC and resync).
Let us know if the erroneous tag file still occurs in that case.
Hello, I’ve entirely removed Roon from the NAS and re-installed it creating a new database. I’ve also chosen to use the metadata contained in the file for all tags and including the “track import date” (see attached). I’ve then re-installed Roon ARC and i now don’t have any access to the filters tab ! Also the sorting by “date imported” is completely erroneous while the files all contain this tag (this works well on JRiver Media center which i used to create all the tags). This is really very disappointing
How precisely did you uninstall Roon - by deleting the RoonServer folder, or by simply uninstalling the RoonServer app? Did you restore a Backup? The current RoonServer has the same name as the previous RoonServer, but you mentioned you effectively started a database from scratch. We need to ascertain this information in order to determine whether your database still has latent corruption.
Roon and JRiver Media Center have significant differences in metadata modeling - have you reviewed our File Tag Best Practices here?
You’ve toggled your Roon Import settings to prefer the file creation time for Date Imported. Is this not what you’d prefer?
Roon’s metadata model is very different from other music programs. Along with File Tag Best Practices above, please ensure you’ve read through this document to understand how Roon will be prioritizing data sources for each album, track, and composition in your library.
Hi,
here’s what i’ve done precisely :
By doing this, as explained above i ended up with no possibility to click on the the filters tab on Arc as shown above. And when i sorted out the albums on Roon based on import time it shows nonsense while the “import date” tag is present on the files and i’ve asked Roon to use the file’s data rather than it’s own.
Then i’ve removed again entirely the folder, re-installed Roon and used the oldest back-up i had to restore it and i end up with the same problem with the “conductor’s” tag filter.
At this point, it might simply be useful that i give you remote access to the Synology which i’m happy to do if your technical team spends some time solving this issue
Thanks for the follow-up. Sorry to hear your issues persist, and that we’re unfortunately unable to offer remote access at this time.
We would like to see if an A/B test of —stripping all embedded tags and custom metadata from the files, refreshing the database, and letting Roon re-index the files from scratch— may show us some additional insight.
Be sure to create a fresh backup before making any edits.
We’ll be on standby for your reply and results, thank you! ![]()
I’m late to this thread but see a couple things that I think I might be able to assist with.
First:
It’s been my experience that certain key words/terms in Roon don’t behave well as Tags, including 'Various Artists" and “Classical” - see what happens if you create a tag like “Classical Albums”.
Second:
You have to use Synology Package Manager to remove the application; simply removing folders won’t do.
Many thanks for your help, I’ll try this once I’m back home in 2 weeks and feedback.
Thanks in advance
We had an additional update to share here.
There are subtle differences to tag logic between Roon and ARC that are likely exacerbating the confusion here.
In Roon, tags that exist but are not applied to any library objects will not be displayed. This means that the Conductor tag may very well exist at the level of your Roon database, but it will be effectively invisible to you from within the Roon application.
ARC, on the other hand, displays all tags in the database, even if they have not been applied to an object.
So, the most likely possibility here is that a deleted file or a file that failed to import (listed in your Skipped Files in Roon Settings → Library) contains the erroneous tag Conductor.
I recommend double-checking the tags attached to any local library content that you’ve deleted from the library since you created this database - the tag will remain in Roon after the deletion. Similarly, double-check any of your recent Imports into Roon that failed (Skipped Files) for objects that contain the tag.
Please let us know if this helps clarify things. We’ll watch for your response once you return and hope all is well in the meantime.
Thanks but I don’t understand how this helps :
Unfortunately, your database contains evidence of both possible latent corruption and misconfigured historical tagging that is confounding Roon’s tag treatment. The best option is to fully refresh the database, re-tag your desired content with a third-party software, in alignment with the best practices here, and then re-import into Roon.