TagEditor, multiple genres and Plex

[denisgomes]

Hello, I was not sure if I should file this under bug or suggestion but here it is.

I'm in the process of reorganizing my music library and retagging all my files with information from Discogs. It works like a charm and it is a breeze to do it. However there is one thing I noticed when using Plex to play my music.

Most albums from Discogs have multiple genres and TagEditor puts them appropriately, and it does so with a semicolon separator, eg: "Electronic;House;Techno". Then I noticed that when browsing by genre, Plex displays this as a single genre "Electronic/House/Techno" instead of separate genres "Electronic", "House" and "Techno".

A quick Google search revealed a Reddit thread about this problem and the suggestion was to use a space after the semicolon so that Plex recognizes these as separate genres. I tried doing this in TagEditor but it didn't work. So I tried doing it in MP3tag and it worked as expected. Later on I used a batch function in MP3tag to fix all my genres at once.

So it seems that TagEditor displays multiple genres separated by ; but actually saves them separated by /, which Plex does not pick up as separate genres. I can confirm this by changing the genre on TagEditor and then opening the file on MP3tag.

Now, the actual problem is: even if I type a semicolon and space to separate genres, TagEditor displays it like this but then changes it to / when saving. So the solution for now is to use MP3tag to fix it.

My suggestion for this would be to not make any transformations or changes when saving tags, or to add an option to define your own separators when saving the tags.

Thanks for such a great product!

[Artem]

The ";" uses by AIMP as universal delimiter for all file formats, next, AIMP will store the data to file tags according file specification. For example, ID3v2.3 uses "/", ID3v2.4 - null separator, Ogg Vorbis stores each value in separate tag pair (field).

Plex does not pick up as separate genres

This is issue of the Plex app. It must follow to ID3 standard.