{Bug Report] Importing genre tag beginning with a number, gives incorrect album genre

Plex Media Server Metadata & Adding Files
,
1

Server Version#: 1.31.2.6810
Player Version#: N/A

Hi all,

I am importing my music library into Plex. The library is carefully curated to make sure the Metadata tags are correct. I make heavy use of genres for organizing my music, but I only ever have a singel genre tagged per track. I know that Plex only has a concept of “Album Genre” rather than “Track Genre”, but all my album tracks will have the same genre tag defined.

I am using “Prefer Local Metadata”, and genre source set to “Metadata”. Mostly the process worked fine, but I noticed some weird genres showing up. It turns out that I have some genres that begin with a number (50s, 60s, 70s, 80s etc), and when imported, those get set to an incorrect album genre in plex.

As an example, I imported a single album all tagged with Genre = “80s”. After import, the album genre was “folk”.

I imported another album that I had already modified the genre tag to “The 50s”. That imported just fine (when previously importing with genre = “50s”, it imported as album genre = “Darkwave”…

server log of the import process below.

Some of the genres I can easily fix, as the albums are grouped under one folder, but other genres are spread across different folder, so I will have to look at the plex library, find each album in the bad genre, and go and modify by hand…
Plex Media Server Logs_2023-03-14_20-14-28.zip (4.9 MB)

ps - loving getting my music collection under control again, after the various mega-corps (Apple, Google, Amazon) tried to take it over and mess with it!

2

I think the problem is because, in the early days of the ID3 metadata standard (v1), genres were represented by numbers. “50” is indeed “Darkwave,” and “80” is “folk.”
List of ID3v1 Genres - Wikipedia

The ID3 v2.3 standard, which is currently the most commonly-used version, allows for text genres, but it also specifies that the numeric codes from v1 can still be used.

3

Thanks. I haven’t looked at the spec, but I’m guessing that the bug is in checking just the first characters, rather than using a regex to exclude cases where the code number is followed by more characters. My regex crafting is stale (petrified even!), but that should be an easy fix…

Anyway, obviously super lo-pri, and I have already modified my library to add "The " infront of these categories (I had to fork out for Metadatics to do that, but I was probably going to need it anyway.).

Thanks again,
Chris.

4

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.