If that’s the case, the problem is caused by a bug in ffmpeg, which Plex uses to read tags. A Plex developer has submitted a fix to ffmpeg, so we just have to wait until they accept the change and publish a new build.
I think that @beckfield is correct. It’s the same bug. I showed the exact problem with the genres not being “rolled up” in this post in the thread mentioned about a half year ago
It seems that Plex is determined that an album can not contain tracks from different genres, and therefore, the album is labeled with the first genre of the first track in the album.
I used to love my Plex music library. I hardly ever use it any more since their new improved scanner broke most of the things I liked about it. I rarely listen to albums, but used smart playlists and collections usually based on genre.
No, I think Certuna is reporting something different.
The other thread talks about all tracks having the same multiple tags, like blues;rock. Certuna is reporting each track having single, non-identical genres. It may be related, and maybe even the same fix, but it’s at least a different symptom.
An album in Plex can still have multiple genres - just try it with a song with Genre = “Pop;Rock”, this will give the album those two genres. It’s when there’s two tracks with one genre each, that Plex fails to roll them up correctly.
It used to do this not too long ago, it must be a change introduced in a recent build.
Curious— if your second track in the album has a genre of “R&B;Soul” are the genres “R&B” and “Soul” rolled up to the album level?
I’ll freely admit, part of my problem is that I haven’t “plex-ified” my music libraries and converted all of the ID3V2.4 tags to ID3V2.3 tags with multiple values separated by a semi-colon. I still haven’t forgiven them for the new scanner/agent that broke all of my genres and I’m still slightly hopeful the fix to ffmpeg will eventually make its way to Plex.
Nope. In my brief experimentation, it seems to take the genre of track one and assigns that to the album. The genres of the rest of the tracks are not rolled up to the album.
Even with my ID3v2.4 tags, the genre assigned to the album gets added into the artist’s genre tags. That is, only the genre given to track one of an album. The genre of any other track in the album, if they are different, don’t “roll” up to the artist level though. I don’t think they would even if I were to use IDv2.3 tags, but I could be wrong. My understanding is that the Plex database stores little (if any) track info.
The old scanner would at least read all of the tracks’ genres on initial scan or a forced refresh, and roll them all up to the album, and then up to the artist. The new version has always used only the first genre(s) it finds (in track one) and discards the others as far as I can tell from day one.
Again, I’m stubbornly clinging to my tags, so I really can’t say how the new scanner has worked with ID3v2.3 tags.
This new bug is independent of tag version, it happens with id3v2.3, v2.4, FLAC/Vorbis and MP4.
Yeah it’s really annoying that since they switched to ffmpeg as the new tag reader, Plex is forcing us to go back to an deprecated tag format (id3v2.3), and to make it even worse, forces us to go against the id3v2.3 standard as well (semicolon separators are non-standard). That was alreadt annoying for tracks with multiple genres per track. And now it doesn’t even read single-valued Genre tags correctly anymore…
) I stopped even using the agent. I have genre sources set to none and rely entirely on this script. It’s annoying to lose built-in support, but you can still have a perfectly tagged library. 