However, on mp3 it is not really a problem for my app, because the ID3v1 tags are placed last and I'm only reading the first tag of each kind. It can be seen, that the problem is present both on wav and mp3. I have uploaded new files non-latin2.wav and non-latin2.mp3 to the previous share to demonstrate this full-width character issue. I'm sure that also many other punctuation characters have full-width variants which are used in Chinese and Japanese. When Mp3tag transliterates these to 8859-1 -compatible format, it converts these characters into normal space and normal tilde characters, and apparently getID3 is only looking for characters replaced with ? characters. Here, the problematic part seems to be the full-width space following the Japanese Kanji characters as well as the full-width tilde next to it. One of them is the real-life music file from one of my users which has title 永夜抄 ~ Eastern Night. However, I can still find some residual cases. Thanks for the quick response and action. Here are the corresponding analyze results after CopyTagsToComments: I have uploaded a pair of sample files here, one wav and one mp3, both defining the same title/album/artis tags: But in this case, getID3 is smart enough to merge the tags so that the field contains only the UTF-8-encoded data. Meanwhile, if the same tag contents are saved to a mp3 file, the strategy used by Mp3tag app is pretty much the same: The UTF-8 data goes to ID3v2.3 and corresponding substitute string goes to ID3v1. Instead, the section of the result contains both versions of the tags, and what's worse, the RIFF tag with all those ? characters comes first. Now, when getID3 combines the different kinds of tags with CopyTagsToComments, it cannot merge these RIFF tags and ID3v2.3 tags properly. In the substitute string, all non-Latin characters are replaced with ? characters. When tagging with non-Latin characters, Mp3tag writes the UTF-8-encoded data to ID3v2.3 tags, and a "substitute strings" to the RIFF header. It seemed to happen only when the tags contained mixed Latin and non-Latin scripts, although I didn't test this quite extensively. There is not really a standard way of doing this and different tools support different ways or none at all. In general tagging WAV files is not really great. Thats a problem of the player, not of MP3tag. I ran in to the following problem when testing WAV files tagged with the Mp3tag application. Listening to wav files should be fine - depending on the player you see the metadata from the tags or you dont.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |