-
Notifications
You must be signed in to change notification settings - Fork 313
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Genres[] tag - Genres not displaying properly in applications #126
Comments
BTW, I am using the exact same approach for Artists[] and Performers[] and both work perfectly! |
So, I'm actually in the process of switching from saving my songs into wav format because I found out that mp3's only store the first genre in the metadata, meanwhile wav stores multiple. Mp3 is also a compressed format, and wav is not, leading to a more lossless audio quality |
@Spiker985 @MartinHarran Also note that it is OK and normal for a tag writing app to replace known genres with the numerical equivalent. I think that there are 40 such genres but could be more or less. |
@J-P- |
`Hi everyone
I am developing a C# application that gathers genre information about a song in Discogs and inserts it into an MP3 file using Taglib-sharp. I am running into problems however when I add the genres in using the Genres[] tag; what particularly bugs me (no pun intended!) is the variation in how the tag is interpreted in various applications, not just the difference between different applications but the variation within specific applications.
Here is the relevant piece of code:
Here are the results of five files for which I have gathered genre/style information;
The individual items in the lists above are stored inside the Genres tag as a string array - I have shown them here separated by semicolons for illustration but what I have shown above also matches the JoinedGenres tag displayed in the ‘locals’ window when the file is opened using Taglib in Visual Studio.
Here is how they appear in Windows Explorer (preview panel and Properties\Details).
Explorer displays the tags in varying ways with no real discernible pattern. In File #1, it picks up the first 3 tags as a single tag (separated by space, no delimiter); the next 2 tags are correctly delimited with a forward slash but are showing the Taglib index numbers for the genres instead of the relevant tag text (the index numbers are correct for the genre); the final two genres are displayed correctly.
In File #2, all the tags are delimited correctly but some are displayed as text and some as the genre index no.
The other 3 files are a mixture of what is happening in File #1 and File #2.
I have also looked at the results in both Mp3Tag and MediaMonkey; they give identical results as follows::
In four of the files, the application is only picking up the first genre but for File #2, they pick up all the tags and delimit them except that like Windows Explorer, some of them are displayed as text and others as index numbers!
There is a fairly easy workaround for this, just by saving all the genres into a single string separated by either forward slashes or commas as applications like MediaMonkey can handle that ok but I'm intrigued as to what is causing the actual problem. It's not even clear to me whether it's a TagLib issue or whether it has to do with applications not properly handling the ID3V2 tags. I see, for example, in the TagLib Changelog that the decision was made back in 2007 to stick with IDV2.3 as "the number of applications that hiccup on ID3v2.4 is too astounding" though that shouldn't be a factor here.
Can anyone shed any light on this?`
The text was updated successfully, but these errors were encountered: