kevinofoz 0 Posted January 11, 2021 Posted January 11, 2021 I am running Emby on my Sonology NAS. While Emby was running (clean install), I copied over a couple hundred songs from my Windows PC onto the share that has been setup in Emby as my music folder on my NAS. The folder structure is pretty basic (Artist -> Album -> Song). And all MP3s are tagged with artist, album, song, etc. In this case, the first artist alphabetically was "`Til Tuesday". About 60% of the music library appears to have the artist and album artist labeled as "`Til Tuesday", which I can assure you is not the case in the MP3 file itself. In the logs file, you can see one case. Search for Glycerine (by Bush) and you will find an example of a file that was processed correctly. In the logs, I see a request for "https://musicbrainz.emby.tv/ws/2/artist/?query=arid:93ccd76c-3790-4435-a8bf-02bc26294b93" and I see UUIDs in the MusicBrainz tags. Search for Mouth (also by Bush) and you will see a request for "http://coverartarchive.org/release/usicBrainz Album Id" I have also seen this with other collections and other songs on clean installs. It seems like Emby cannot recognize the Artist (even though it is in the tag and folder name) and so errors out with the ID and defaults to the first artist that was processed. All other data does seem correct. Even the genre. But this is obviously a big deal if I can't find my songs. embyserver.txt
Abobader 3470 Posted January 11, 2021 Posted January 11, 2021 Hello kevinofoz, Please wait for someone from staff support or our members to reply to you. It's recommended to provide more info, as it explain in this thread: Thank you. Emby Team
Happy2Play 9785 Posted January 11, 2021 Posted January 11, 2021 Looking at those externalids suggests you have corrupt/bad embedded tags. I bet mp3tag would tell you the same thing.
kevinofoz 0 Posted January 11, 2021 Author Posted January 11, 2021 I just realized that I had to view the extended tags in MP3tag. I realized this when I used ffprobe to do the same command I saw in the logs. These bad tags have probably been there for years. Windows Media Player, Google Music (RIP), Plex, etc. None of them ever indicated that there was a problem with the tags. I will go ahead and fix these tags for my case. Any suggestion for a tool to handle fixing these? It is probably hundreds. But I do believe that the error handling does need to be fixed. It encounters a bad tag and it defaults to the first artist it found. That is not a good default. In fact, I just had a talk with my team today about default values in code. Instead, it should default to the artist tag or something similar. In my case, those had perfectly good values. It is not really using a default value. It is using a wrong value.
Carlo 4561 Posted January 11, 2021 Posted January 11, 2021 MP3tag or Picard can handle hundreds pretty easily.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now