Twistedcloud 7 Posted January 22, 2019 Posted January 22, 2019 (edited) Hello For some reason Emby recently only started reading the first Genre tag in all of my music. My Music folder is setup as Artist > Album > Tracks My Music is tagged using Mp3Tag and Music Bee Genre1//Genre2//Genre3//Genre4 Stone Sour Come What(ever) May Heavy Metal//Hard Rock//Alternative Metal//Post-Grunge Emby only shows Heavy Metal. Edited January 22, 2019 by Twistedcloud
Luke 39009 Posted January 22, 2019 Posted January 22, 2019 What are the contents of the album folder? Can you show a screenshot?
Twistedcloud 7 Posted January 22, 2019 Author Posted January 22, 2019 (edited) What are the contents of the album folder? Can you show a screenshot? Just the music files Edit I have tried playing around with it and it seems Emby is not reading my ID3 tags but rather the file details. if go into the file properties to details and update the genre tag there Emby will read it. My Emby will read a single tag: Heavy Metal//Hard Rock//Alternative Metal//Post-Grunge My Emby won't read: Genre: Heavy Metal Genre: Hard Rock Genre: Alternative Metal Edited January 22, 2019 by Twistedcloud
Twistedcloud 7 Posted January 23, 2019 Author Posted January 23, 2019 (edited) Update, my m4a and FLAC files work it only seems to be my MP3 files that are having an issue. Edit: I figured the issue may be with the ID# tags, Both MusicBrainz Picard and Musicbee have a default setting to save ID3v1 tags along with ID3v2.3 since both tags are saved past posts noted that Emby may not read them correctly I used ID3Remover to remove only the V1 tags and it is still not showing correctly. Edited January 23, 2019 by Twistedcloud
Happy2Play 9230 Posted January 23, 2019 Posted January 23, 2019 (edited) To me it is the delimiter you chose to tag with. I just tagged a track with using a semi-colon and it displayed without issue after Refreshing the Album. I believe Emby is limited to semi-colon or single forward slash delimiters, not positive on any others. Edited January 23, 2019 by Happy2Play
Twistedcloud 7 Posted January 23, 2019 Author Posted January 23, 2019 To me it is the delimiter you chose to tag with. I just tagged a track with using a semi-colon and it displayed without issue after Refreshing the Album. I believe Emby is limited to semi-colon or single forward slash delimiters, not positive on any others. Odd, so MusicBee uses ; but when it saves it saves as // rather then ; which is causing the issue.
Luke 39009 Posted January 23, 2019 Posted January 23, 2019 Update, my m4a and FLAC files work it only seems to be my MP3 files that are having an issue. Edit: I figured the issue may be with the ID# tags, Both MusicBrainz Picard and Musicbee have a default setting to save ID3v1 tags along with ID3v2.3 since both tags are saved past posts noted that Emby may not read them correctly I used ID3Remover to remove only the V1 tags and it is still not showing correctly. Correct, we use ffprobe. Make sure your tagging software writes both and then it should work fine.
Twistedcloud 7 Posted January 24, 2019 Author Posted January 24, 2019 Well MP3 tagging is super annoying I use a combination of Emby, Kodi and MusicBee with Mp3Tagger and music BrainzPicard. MusicBee Reads the Following Tags: Genre1; Genre2 or Genre1\\Genre2 Kodi Reads the Following Tags: Genre1\\Genre2 or Genre1 / Genre2 Emby Reads the following Tags: Genre1; Genre2 or Genre1 / Genre2 and Genre1 \ Genre2 These 3 programs will not read the same set of ID3 tag for mulitpule Genre. The only work around I can see for anyone else who is running itno the same issue as me is to use Genre1; Genre2 and edit the kodi advanced system file to read ; rather then / (this may mess up tag reading for other file types) If any one has a suggestion on a better way to tag all my media between these 3 programs that would be great.
Happy2Play 9230 Posted January 24, 2019 Posted January 24, 2019 Ultimately Luke would need to see the output of what ffprobe sees. Then maybe he can add additional delimiters.
Luke 39009 Posted January 24, 2019 Posted January 24, 2019 Can you provide sample audio for testing? thanks.
Twistedcloud 7 Posted January 24, 2019 Author Posted January 24, 2019 (edited) Can you provide sample audio for testing? thanks. I uploaded some Mp3 files with tags, it seems Mp3Tags and MusicBee save tags by defult as in in File 1, This is the one Emby can not read. If I change the tags to either 02 or 03 Emby will read them (but that is a lot of work) 01- Test with double back slash ID3V1&2.3.mp3 02- Test with one slahs ID3V1&2.3.mp3 03- Test with ; ID3v2.3.mp3 04-Test with double back slash ID3v2.3.mp3 Edited January 24, 2019 by Twistedcloud
Happy2Play 9230 Posted January 25, 2019 Posted January 25, 2019 (edited) 1 &4 ffprobe doesn't see additional Genres. So it looks like a limitation of FFprobe. 2 3 Edited January 25, 2019 by Happy2Play
Luke 39009 Posted January 25, 2019 Posted January 25, 2019 Its' probably reading a different version of the id3 tags. that's why if you make sure your tagging software writes all of them, then you should be fine.
Twistedcloud 7 Posted January 26, 2019 Author Posted January 26, 2019 what do you use to tag and sort music before adding it into Emby? It seems both Mp3Tag and MusicBee save genre tags that FFprobe can't read
Luke 39009 Posted January 26, 2019 Posted January 26, 2019 Many people here use Mp3tag successfully. Picard is also popular. @@ginjaninja and @@Vicpa may have some tips. Thanks.
PenkethBoy 2066 Posted January 26, 2019 Posted January 26, 2019 Use Picard to update and correct your metadata (uses data from MusicBrianz) and solves 99% of peoples problems Try it on a few albums you are having problems with
Happy2Play 9230 Posted January 26, 2019 Posted January 26, 2019 Not that I understand it the backslash is used for "Quoting and Escaping", so I would suspect it will always be a issue in ffprobe.
Solution Twistedcloud 7 Posted February 23, 2020 Author Solution Posted February 23, 2020 I decide to jump back into the Music section of Emby and see if I could figure out my issues from above and I think it may be an issue with the Unraid version of Emby I was using (the linuxerver Docker version, I had run into issues when Emby upgraded to version 4 and switched the Docker to see if that would correct how often my Database got corrupted) ). I decide to install a clean version of Emby on my PC and try to get music working on it and it worked the first try. Seems that the issue I was having is tied to the Unraid docker version of Emby and not an Emby Issue. Here is how my Music Artists looked in Emby on Windows Here is what My Unraid (linux Server Version) shows. When I click into an Album here is what Windows Emby shows My Unraid Version: I am getting the same issue with FLAC and MP3. I had rebuilt the Database many times, Tried fresh installs but it wouldn't work. This is when I realized I wasn't using the official Emby version so I switch my install to the Official version of Emby and all now seems to be working. Hopefully this post may help someone who runs into the same issue in the future. Also for anyone Using MusicBee to sort and Tag Music, You can use Picard to switch the tags into a version Emby reads, In picard just write click use original Data in the fields and Picard with re-write the tags so both Music bee and Emby can read them. 1
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