· After import using ROONALBUMTAG, message appearing 'this tag was not found in your library'
No genres being used in my library. Roon set to No x2 for 'roon's metadata database' and 'genres from filetags'. System solely set to use tags as genres. This functionality is working for entries like 'darksynth' or 'downtempo'. Those are read from the files and the tag is automatically created and attached to the files. As expected. When I use the entry 'Synthwave' for ROONALBUMTAG, it attaches to the files BUT when clicking on it, I get the message above with missing tag. I thought it was some conflict with the genre but there are no genres in the system! If I manually create a new tag and manually attach those albums/files to the new manual tag, it does work...but each entry now shows 2 clickable entries. One that does go to the tag and its contents, the other with the error. This so far is only for 'Synthwave'...like there is some ghost entry in the database somewhere. Tried backing up/restoring database to no avail.
Tell us about your home network
· This is not relevant to the issue.
mjw
(Father! Father! Resist not! Let us destroy the core! Set us free!)
2
I had this issue last year, and it was caused by manually deleting the tag when releases were imported with ROONALBUMTAG.
Most likely a bug. IIRC, I had to restore the previous night’s backup.
Depending on how you set the import date (I have this in the files’ metadata), you could remove all releases that use the tag from your library, delete the tags, clean the library, and reimport. But backup first as I don’t know if this would work.
100% this is a bug. You can of course delete the manually made tag (Synthwave) to which you have added albums manually to (and the tag does disappear) but if you delete the tag that was created at import by Roon into ROONALBUMTAG, it orphans that tag and any albums that were attached to it get the ‘tag not found’ error. It does not clean itself up apparently. Just confirmed this with another tag that was working. Roon upon a ‘rescan album’ doesn’t then further recreate the tag as it is no doubt a duplicate but you cannot see it anymore in the ‘my tags’ space.
mjw
(Father! Father! Resist not! Let us destroy the core! Set us free!)
4
Which is why I suggested removing them from the library.
Yep, I now remember that, too.
I hope you have a backup since a fix, once Roon confirms the issue, could be in the development backlog for some time.
Hmmm…If you are referring to removing the albums, that is a no-go. You cannot remove a tag that is of course no longer present in the ‘my tags’ section.
The workaround is to remove the embedded ROONALBUMTAG and just manually create the tag/add the albums manually (confirmed this works) but a fix is needed. I have had Roon mysteriously forget tags so having them embedded in the audio files is 100% safe and gives redundancy in case of issues…
mjw
(Father! Father! Resist not! Let us destroy the core! Set us free!)
6
I was suggesting you remove the albums and reimport after sorting out the tag issue. Since you have two identical tags, delete these when no albums are using the tag, and then reimport. I can’t remember what I did exactly, so I may have resorted to restoring a backup, but worth a try unless it messes up your import date (I always use IMPORTDATE, so not an issue.)
Tried that to no avail. Deleting the tag auto-created keeps it somewhere and Roon past that point regardless won’t ever create it again automatically. Creating a new tag even with the same name won’t glue them together as internally they have different pointers. I will live with the one tag being bad so far and stick to manual addition on this one while hopefully all the others continue to work with the expected behavior…
mjw
(Father! Father! Resist not! Let us destroy the core! Set us free!)
8
Okay, maybe that’s why I ended up restoring a backup. TBH, I can’t remember, but it definitely sucks.
Thank you for writing in @Kevin_Dackiw and for your thorough report! Thanks for confirming the issue as well @mjw - we have a ticket in with development for further review.
In the meantime, I’m curious - the tag Synthwave is likely a globally recognized genre in Roon’s cloud, I wonder if there is some sort of UID collision happening here.
Are you able to reproduce this with any tag name? What if you try __Synthwave?
We should have more information to share before the end of the week. Thank you!
If I pick other ‘common’ genres like “Berlin School” or “Darksynth” then all is well. Even “Ambient” works. One would think Ambient is a pretty globally recognized genre too? Perhaps not and a subset of Electronic…
As for the ‘_Synthwave” test, that passed just fine. I suspected there was a hidden hash/UID collision somewhere so your insight is encouraging as you dig.
Just for reference, this came as I decided to classify my electronic collection manually and do away with genres. Disabled throughout Roon and all genre tags in files removed.
Here is my current set of tags with only Synthwave being the oddity (so far!).
Thanks for sharing the results of your investigation with us. We have made several attempts to reproduce this on our side, and we were able to spot the same behavior: when you delete a tag from Tags, it does not disappear from the album and does not let you go through the Tag/Genre.
We will add this information to the investigation ticket for R&D so they can fix it.
