Conflicting Genre Tag - mp3tag vs. Lumin App

@g-man-langley

Can you do me a favor and check the size of the Music Library of the Music.app

It should be located under /Users/~/Music, where "~" is the name of the logged in user's folder.

Inside this folder you'll find another folder named "Media", and the music library data file itself, named, by default "Music Library.musiclibrary".

MinimServer is a DLNA streaming server, so i don’t think the Music app is relevant, and takes away from what is the crux here.

@AreDigg

Have you seen this?

yes, but it seem like there is an issue with MinimServer and reading the tags. One thing about MPEG4 and genre is that there are two different atoms for the metadata.

But still it's strange that when adding / changing tags in Apple Music / Music.app yes there are two apps nowadays it corrects itself in MinimServer,

But why DOES it read it correctly from Apple but not from MP3tag?

Edit: Let's wait what the developer of MinimServer has to say on the OP's his query

Nothing strange there.

Can you check that G-Music drive I believe you have your music stored there if there is anything else on there then Music files? (like a database etc)

Nothing but music files, some booklet.pdf’s and images of front/back covers.

MinimServer replied saying the genre tag in a sample file I sent is in the incorrect format, it’s on the link to the forum I posted. mp3tag will read it however, as well as VLC and Foobar.

MinimServer suggested I save the file in mp3tag to write the correct format, I even changed it to “Pop” and still get “[unknown]” in MinimServer/Lumin.

OK, well, dropping this modified file, after removing and adding again to Apple Music gives me Unknown Genre, even though mp3tag now says “Pop” and reads that value back. Sigh.

^ Deffo updated in Apple Music. At this point, I think mp3tag is writing the text value of the new genre, but possibly keeping extra char that Apple Music and MinimServer don’t like.

Contact @Florian and maybe prepare one those files to upload to a sharing site so Florian can have a look.

Thank you for the example file @g-man-langley !

I've analyzed the issue and it's related to two different ways of storing the genre in the MP4 tag.

Mp3tag tries to use the gnre MP4 atom for genres that are part of the ID3v1 standard. This stores the index to the actual genre in this pre-defined genre list. For custom genres, it uses the ©gen MP4 atom, which is what Apple Music seems to expect now.

The file in question uses the gnre atom (ID3v1 genre index), which also doesn't seem to be supported by MinimServer.

I have not decided on a solution for this so far.

Thanks Florian, I think I understand (a bit). So you are talking about these being the standard genres, anything not in this list is custom, is that correct? And you believe MinimServer does not support that, sorry if I misunderstand?

Does the genre always get written to a single block in the file? Like a special field in the file.

Yes, based on the information from this topic and the reply you received from the developer of MinimServer (I've checked the post in the MinimServer forums), it looks like MinimServer doesn't support MP4 gnre atoms.

Yes, those are the MP4 atoms I'm referring to. In case of the MP4 gnre atom, it's a binary block in the file that stores the ID3v1 genre index instead of the actual string value, e.g, 17 for genre Rock. In case of the MP4 ©gen atom, the actual string value of the genre is stored, i.e., Rock.

This also confirms what @AreDigg already suspected above.

My analysis was incomplete. I've edited my posts above and used strikethrough on all occurrences where I referred to Apple Music and MinimServer not supporting gnre atoms.

Lots of code changed in the MP4 implementation to v1.9.7 and it seems that I'm not writing the typeID for the gnre atom expected by Apple Music anymore. Apple Music seems to expect no type (0x00) whereas Mp3tag for Mac currently writes signed integer 0x15.

I'll investigate further and keep you posted.

I guess if it’s the case of having one or the other then it could be a preference setting?