# Conflicting Genre Tag - mp3tag vs. Lumin App

**URL:** <https://community.mp3tag.de/t/conflicting-genre-tag-mp3tag-vs-lumin-app/69825>\
**Category:** Mac\
**Tags:** bug-fixed\
**Created:** [September 20, 2025, 8:47am UTC](https://community.mp3tag.de/t/conflicting-genre-tag-mp3tag-vs-lumin-app/69825 "2025-09-20T08:47:41Z")\
**Posts on this page:** 20\
**Page:** 4

<div class="post-metadata">

**Author:** ![mjcm](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/m/9d8465/32.png) [@mjcm](https://community.mp3tag.de/u/mjcm)\
**Post date:** [September 22, 2025, 7:49am UTC](https://community.mp3tag.de/t/conflicting-genre-tag-mp3tag-vs-lumin-app/69825/63 "2025-09-22T07:49:10Z")

</div>

@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".

---

<div class="post-metadata">

**Author:** ![AreDigg](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/a/bbe5ce/32.png) [@AreDigg](https://community.mp3tag.de/u/AreDigg)\
**Post date:** [September 22, 2025, 8:36am UTC](https://community.mp3tag.de/t/conflicting-genre-tag-mp3tag-vs-lumin-app/69825/64 "2025-09-22T08:36:54Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![mjcm](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/m/9d8465/32.png) [@mjcm](https://community.mp3tag.de/u/mjcm)\
**Post date:** [September 22, 2025, 8:52am UTC](https://community.mp3tag.de/t/conflicting-genre-tag-mp3tag-vs-lumin-app/69825/65 "2025-09-22T08:52:58Z")

</div>

@AreDigg

Have you seen this?

> [@Conflicting Genre Tag - mp3tag vs. Lumin App](https://community.mp3tag.de/t/conflicting-genre-tag-mp3tag-vs-lumin-app/69825/38):
>
> Yes! Changing in Apple Music, rescan MinimServer and we have Jazz baby!! Well done sir.

---

<div class="post-metadata">

**Author:** ![AreDigg](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/a/bbe5ce/32.png) [@AreDigg](https://community.mp3tag.de/u/AreDigg)\
**Post date:** [September 22, 2025, 9:23am UTC](https://community.mp3tag.de/t/conflicting-genre-tag-mp3tag-vs-lumin-app/69825/66 "2025-09-22T09:23:32Z")

</div>

> [@mjcm](#):
>
> 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.

---

<div class="post-metadata">

**Author:** ![mjcm](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/m/9d8465/32.png) [@mjcm](https://community.mp3tag.de/u/mjcm)\
**Post date:** [September 22, 2025, 9:35am UTC](https://community.mp3tag.de/t/conflicting-genre-tag-mp3tag-vs-lumin-app/69825/67 "2025-09-22T09:35:38Z")

</div>

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,

> [@AreDigg](#):
>
> yes, but it seem like there is an issue with MinimServer and reading the tags.

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

---

<div class="post-metadata">

**Author:** ![g-man-langley](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/g/d07c76/32.png) [@g-man-langley](https://community.mp3tag.de/u/g-man-langley)\
**Post date:** [September 22, 2025, 9:58am UTC](https://community.mp3tag.de/t/conflicting-genre-tag-mp3tag-vs-lumin-app/69825/68 "2025-09-22T09:58:41Z")

</div>

![Screenshot 2025-09-22 at 10.58.00](https://community.mp3tag.de/uploads/default/original/3X/9/d/9dd0e1cfeef914c987b1b14e0aaaac87986b3885.jpeg)

---

<div class="post-metadata">

**Author:** ![mjcm](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/m/9d8465/32.png) [@mjcm](https://community.mp3tag.de/u/mjcm)\
**Post date:** [September 23, 2025, 12:31am UTC](https://community.mp3tag.de/t/conflicting-genre-tag-mp3tag-vs-lumin-app/69825/69 "2025-09-23T00:31:19Z")

</div>

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)

---

<div class="post-metadata">

**Author:** ![g-man-langley](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/g/d07c76/32.png) [@g-man-langley](https://community.mp3tag.de/u/g-man-langley)\
**Post date:** [September 23, 2025, 4:41am UTC](https://community.mp3tag.de/t/conflicting-genre-tag-mp3tag-vs-lumin-app/69825/70 "2025-09-23T04:41:28Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![g-man-langley](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/g/d07c76/32.png) [@g-man-langley](https://community.mp3tag.de/u/g-man-langley)\
**Post date:** [September 23, 2025, 5:16am UTC](https://community.mp3tag.de/t/conflicting-genre-tag-mp3tag-vs-lumin-app/69825/71 "2025-09-23T05:16:51Z")

</div>

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.

 ![Result](https://community.mp3tag.de/uploads/default/original/3X/7/c/7c1e7d73ba739a74baadd3c828ff8536cf1600d0.jpeg)

 ![mp3tag](https://community.mp3tag.de/uploads/default/original/3X/b/a/badc69bdd3237eb196333627a9e01afa28b8132d.jpeg)

 ![Modified](https://community.mp3tag.de/uploads/default/original/3X/c/b/cb1f9bdf17e98d0c26881e16a0e7f9a574d3366a.jpeg)

 ![Reload](https://community.mp3tag.de/uploads/default/original/3X/7/a/7a906c19724dd712e609e0f97078ca4953088df3.jpeg)

---

<div class="post-metadata">

**Author:** ![g-man-langley](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/g/d07c76/32.png) [@g-man-langley](https://community.mp3tag.de/u/g-man-langley)\
**Post date:** [September 23, 2025, 5:21am UTC](https://community.mp3tag.de/t/conflicting-genre-tag-mp3tag-vs-lumin-app/69825/72 "2025-09-23T05:21:19Z")

</div>

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.

 ![Screenshot 2025-09-23 at 06.20.57](https://community.mp3tag.de/uploads/default/original/3X/a/c/acde8fd468582660b9af67d2e6fef4b7a5c224d9.jpeg)

 ![Screenshot 2025-09-23 at 06.18.29](https://community.mp3tag.de/uploads/default/original/3X/6/6/664bcbf29cb645a5b5882f7ce725d3b32777f6f0.jpeg)

---

<div class="post-metadata">

**Author:** ![g-man-langley](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/g/d07c76/32.png) [@g-man-langley](https://community.mp3tag.de/u/g-man-langley)\
**Post date:** [September 23, 2025, 5:22am UTC](https://community.mp3tag.de/t/conflicting-genre-tag-mp3tag-vs-lumin-app/69825/73 "2025-09-23T05:22:19Z")

</div>

![Screenshot 2025-09-23 at 06.21.58](https://community.mp3tag.de/uploads/default/original/3X/1/d/1d99c4919048d53bd9e61677ecfc5b1d8bebfebf.jpeg)

---

<div class="post-metadata">

**Author:** ![g-man-langley](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/g/d07c76/32.png) [@g-man-langley](https://community.mp3tag.de/u/g-man-langley)\
**Post date:** [September 23, 2025, 5:22am UTC](https://community.mp3tag.de/t/conflicting-genre-tag-mp3tag-vs-lumin-app/69825/74 "2025-09-23T05:22:37Z")

</div>

^ 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.

---

<div class="post-metadata">

**Author:** ![mjcm](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/m/9d8465/32.png) [@mjcm](https://community.mp3tag.de/u/mjcm)\
**Post date:** [September 23, 2025, 5:57am UTC](https://community.mp3tag.de/t/conflicting-genre-tag-mp3tag-vs-lumin-app/69825/75 "2025-09-23T05:57:07Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![Florian](https://community.mp3tag.de/user_avatar/community.mp3tag.de/florian/32/5759_2.png) [@Florian](https://community.mp3tag.de/u/Florian)\
**Post date:** [September 23, 2025, 3:59pm UTC](https://community.mp3tag.de/t/conflicting-genre-tag-mp3tag-vs-lumin-app/69825/76 "2025-09-23T15:59:35Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![g-man-langley](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/g/d07c76/32.png) [@g-man-langley](https://community.mp3tag.de/u/g-man-langley)\
**Post date:** [September 23, 2025, 4:49pm UTC](https://community.mp3tag.de/t/conflicting-genre-tag-mp3tag-vs-lumin-app/69825/77 "2025-09-23T16:49:58Z")

</div>

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?

> **[List of ID3v1 genres](https://en.wikipedia.org/wiki/List_of_ID3v1_genres)**
>
> ID3 is a metadata container most often used in conjunction with the MP3 audio file format. It allows information such as the title, artist, album, track number, and other information about the file to be stored in the file itself.
> The ID3v1 series, in particular, stores genre as an 8-bit number (therefore ranging from 0 to 255, with the latter having the meaning of "undefined" or "not set"), allowing each file to have at most one genre out of a fixed list.
> Genre definitions 0-79 follow the ID...

---

<div class="post-metadata">

**Author:** ![g-man-langley](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/g/d07c76/32.png) [@g-man-langley](https://community.mp3tag.de/u/g-man-langley)\
**Post date:** [September 23, 2025, 4:51pm UTC](https://community.mp3tag.de/t/conflicting-genre-tag-mp3tag-vs-lumin-app/69825/78 "2025-09-23T16:51:28Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![Florian](https://community.mp3tag.de/user_avatar/community.mp3tag.de/florian/32/5759_2.png) [@Florian](https://community.mp3tag.de/u/Florian)\
**Post date:** [September 23, 2025, 6:13pm UTC](https://community.mp3tag.de/t/conflicting-genre-tag-mp3tag-vs-lumin-app/69825/79 "2025-09-23T18:13:14Z")

</div>

~~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.~~

> [@g-man-langley](#):
>
> Does the genre always get written to a single block in the file? Like a special field in the file.

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`.

---

<div class="post-metadata">

**Author:** ![Florian](https://community.mp3tag.de/user_avatar/community.mp3tag.de/florian/32/5759_2.png) [@Florian](https://community.mp3tag.de/u/Florian)\
**Post date:** [September 23, 2025, 6:22pm UTC](https://community.mp3tag.de/t/conflicting-genre-tag-mp3tag-vs-lumin-app/69825/80 "2025-09-23T18:22:54Z")

</div>

> [@AreDigg](#):
>
> One thing about MPEG4 and genre is that there are two different atoms for the metadata.

This also confirms what @AreDigg already suspected above.

---

<div class="post-metadata">

**Author:** ![Florian](https://community.mp3tag.de/user_avatar/community.mp3tag.de/florian/32/5759_2.png) [@Florian](https://community.mp3tag.de/u/Florian)\
**Post date:** [September 23, 2025, 6:40pm UTC](https://community.mp3tag.de/t/conflicting-genre-tag-mp3tag-vs-lumin-app/69825/81 "2025-09-23T18:40:30Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![g-man-langley](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/g/d07c76/32.png) [@g-man-langley](https://community.mp3tag.de/u/g-man-langley)\
**Post date:** [September 24, 2025, 4:34am UTC](https://community.mp3tag.de/t/conflicting-genre-tag-mp3tag-vs-lumin-app/69825/82 "2025-09-24T04:34:51Z")

</div>

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

[Previous page](https://community.mp3tag.de/t/conflicting-genre-tag-mp3tag-vs-lumin-app/69825.md?page=3)

[Next page](https://community.mp3tag.de/t/conflicting-genre-tag-mp3tag-vs-lumin-app/69825.md?page=5)
