Summary: | SE mobile unable to read mp3 tags (of some files) properly | ||
---|---|---|---|
Product: | [Frameworks and Libraries] taglib | Reporter: | Yogesh Marwaha <yogeshm.007> |
Component: | general | Assignee: | Scott Wheeler <wheeler> |
Status: | RESOLVED NOT A BUG | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Yogesh Marwaha
2008-08-14 09:39:01 UTC
I've uploaded mp3 files for you This is one which is working properly: - http://yogeshm.007.googlepages.com/Ishq_Ada_-_Ada.mp3 ...and this is the one where tags are not shown properly: - http://yogeshm.007.googlepages.com/Bachna_Ae_Haseeno_-_Bachna_Ae_Haseen.mp3 In this file album name is shown as "Bachna Ae Hasee" instead of "Bachna Ae Haseeno" and title is shown as "Bachna Ae" instead of "Bachna Ae Haseeno". The first obvious difference is that the "correct" file uses Latin-1 strings, while the other one uses UTF-8 strings. Does the phone show tags correctly for http://oxygene.sk/lukas/test.mp3 (it's the Bachna_Ae_Haseeno_-_Bachna_Ae_Haseen.mp3 file but with Latin-1 tags and truncated)? If it does, it's not really a TagLib bug. Yes, tags are shown correctly for "http://oxygene.sk/lukas/test.mp3" in my phone. If the problem is not with taglib, then which program is responsible for this. The only app I use is Amarok (Noatun was the preferred app about one and half year ago); I might have tried others but not for long and *never* edited any tags except with Amarok/Noatun. OT: Can you suggest any way I can force all files in my collection to use latin-1 encoding? Is latin-1 the dedfault/preferred encoding format for mp3 files? Hmm, then it sounds like the bug is in your phone. There is no "preferred" encoding for ID3v2 -- the standard supports Latin1, UTF-8 and UTF-16. It seems that your phone doesn't work with at least UTF-8, possibly also UTF-16. It's fairly easy programatically to set TagLib to write Latin1 tags, in fact, the default in 1.5 is to write Latin1 unless the string is using characters that can't be represented in Latin1. Getting that supported in your tagger of choice is another matter. |