# 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:** 1
**Showing post:** 76

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

---

_[View the full topic](https://community.mp3tag.de/t/conflicting-genre-tag-mp3tag-vs-lumin-app/69825)._