Artist metadata - genre field not populating

Haha… well the bug is ONLY a year old, and when I mentioned it, I was basically told that flac files work properly, and my files were obviously tagged incorrectly. So I don’t think it was ever looked at.

The Plex boss has visited this thread a couple of times, maybe he can get someone to look at it for us next time he pops by. :grin:

thanks for the investigative work, it’s much appreciated!

the issue has been fixed and will roll out as usual to a server in the near future.

3 Likes

Amazing! Thanks as always Elan

I came here about the same thing!!! Great to see the fix will be rolling out soon.

Could you elaborate on “in the near future”? There have been 8 Server releases since then without this fix. Is it still coming?

so sorry, it’s been in the back-burner to get reviewed and merged with other distractions. i’ll bump it.

1 Like

Thank you for implementing this fix!

I still have two issues in this area:
Genre capitalization doesn’t work, for example I always get Post-hardcore instead of Post-Hardcore (how it’s stored in the tag)

And the following:
For me the downloaded style tags are showing, which are for most of the time useless Pop/Rock

I have a similar problem, with only one genre (that I’m aware of) Soft Rock is always displayed as Soft rock. I actually went through the whole library and found just one album where I had misspelled the tag. I corrected it, refreshed for the album, (no change), refreshed the library (no change) and then Plex danced the album that I had changed (still no change) I’ve tried a couple of times, using variations of all of those, and no luck.

I suspect the misspelled genre name is stored someplace in the database that none of the usual and easy methods correct, and Plex applies that for whatever reason. I believe that is actually a remnant from the old system, even though that library was actually deleted before I switched to the new one. Probably a way to get rid of it if you edit the database, but it’s not so annoying that I’m prepared to do that.

That is correct, and we use case-insensitive matching. You’d need to edit the database (tags field) for now, unfortunately.