Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: incompatibilities/inconsistencies with id3v2 tags (Read 6297 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

incompatibilities/inconsistencies with id3v2 tags

so i'm using the id3v2 tag plugin for foobar2k, as despite it being kludgy and nasty, just about everyone in the world uses id3v2.  everything seemed to be working fine with this, foobar was happy, winamp was happy, mp3 tag studio reads these tags properly, etc. however, when itunes gets a hold of an mp3 with tags written by foobar2k, it doesn't see them, and treats it as a flat file with no tags (although it does mention that the tag version is v2.3, despite the fields being empty!),  kode54, anyone, any solutions to this issue? or is this known/not cared about?

incompatibilities/inconsistencies with id3v2 tags

Reply #1 –
Complain to Apple for not supporting UTF-8 encoded frames. (ID3v2 supports ISO-8859-1, UTF-8, and both big and little endian UTF-16. Of course, many applications will stick whatever encoding your machine is set to into a field and call it ISO-8859-1, which it isn't. My tag component reads all supported formats, and always writes UTF-8. It stupidly translates the ISO-8859-1 encoding as whatever code page your machine is configured to use. Maybe I should get around to "fixing" this by doing my own ISO-8859-1 to UTF-8 translation...)

incompatibilities/inconsistencies with id3v2 tags

Reply #2 –
how easy would it be to make this plugin write to another frame type, i.e. possibly UTF-16? an option for this would be greatly appreciated, as it's pretty doubtful that apple gives a shit.

btw, out of curiosity, is ISO-8859-1 the common encoding scheme in the wild? i don't have problems with any mp3s and itunes other than the ones which have been touched by the foobar id3v2 plugin.

incompatibilities/inconsistencies with id3v2 tags

Reply #3 –
ISO-8859-1 is the common encoding. Nobody seems to give a shit about Unicode. I know Winamp 2.91 doesn't like UTF-16 fields, and it seems to treat UTF-8 like ANSI. What's the point of a standard if nobody supports it properly?

incompatibilities/inconsistencies with id3v2 tags

Reply #4 –
it seems that there's same situation with iRiver players. i made following tests on imp400 and ifp195tc players (imp400 is mp3/wma/asf cd based player and ifp195tc mp3/wma/asf is flash player to make it clear). both players supports id3v1 and id3v2 v2.0 - v4.0. when i use tag&rename to work with tags everything is ok, i mean players are able to read tags but when i make any change to tags from foobar with kode's 54 id3v2 plugin then both player are unable to read any tag - and also widows xp explorer no more displays tags when viewing mp3 files. i guess that this has something to do with unicode format of tag. so there's question to kode54 - could you add option to your id3v2 plugin to support non unicode tags?

incompatibilities/inconsistencies with id3v2 tags

Reply #5 –
UTF-16 LE and BE will be optional, if I can get id3lib to write them.

ISO-8859-1 will also be optional. ISO-8859-1 does not necessarily mean your local code page. Software which interprets ISO-8859-1 to mean local code page is broken.

Oh wait, that means my ISO-8859-1 reading support is misbehaving. I should correct it before I continue to post about standards.

incompatibilities/inconsistencies with id3v2 tags

Reply #6 –
hey, thanks a lot.. this will make things a lot easier for those of us using portable players.. right now i have to touch all my files periodically with another id3v2 editor to get them to be visible to iTunes/iPod... thanks!

incompatibilities/inconsistencies with id3v2 tags

Reply #7 –
question to kode54 - what changes incorporates version 1.03 of foo_id3v2 plugin? btw. could you publish changes log with your plugins, please

incompatibilities/inconsistencies with id3v2 tags

Reply #8 –
Already posted the changes in 3rd party plugins topic, but here it is again: Fixed tag removal to use memory buffering when the file is smaller than 16MB, just like my tag writer service. Previously, due to some tired miscoding, it was using memory buffering only for files larger than 10MB. The same goes for foo_input_standard's internal ID3v2 tag remover, which has already been corrected and should appear with the next release.

incompatibilities/inconsistencies with id3v2 tags

Reply #9 –
Posted v1.04.
  • Changed tag reader to translate from ISO-8859-1 as per spec, rather than using your local code page.
  • Configuration has returned, now you can write ISO-8859-1 strings instead of UTF-8.
I could try UTF-16 next, but I doubt anything out there supports that stuff any better than UTF-8. If you want more than ISO-8859-1, bug your vendor to add proper Unicode support, because this tag standard doesn't support any specific encoding other than ISO-8859-1.

EDIT: In case there are any questions about missing characters in tags, ISO-8859-1 includes Unicode character ranges 0x20-0x7E and 0xA0-0xFF. That's it. Need more? Use UTF-8.

incompatibilities/inconsistencies with id3v2 tags

Reply #10 –
@kode54:
is the id3v2 plugin in case installer the same as yours?

it reports the same version, but the size of the dll is about a half...

any idea why ?

incompatibilities/inconsistencies with id3v2 tags

Reply #11 –
The smaller file is compressed with UPX, and so are all components on official foobar2000 releases.

incompatibilities/inconsistencies with id3v2 tags

Reply #12 –
v1.04a. Just to be consistent with other Win32 character conversion that I'm aware of, the internal ISO-8859-1 convertors will emit question marks when they hit unsupported (UTF-8 -> ISO-8859-1) or illegal (ISO-8859-1 -> UTF-8) characters.

incompatibilities/inconsistencies with id3v2 tags

Reply #13 –
Altered the character conversion functions to use Windows conversion, so you should get some more sensible downgrading if your system supports it. (ie. fullwidth characters should become supported halfwidth versions.)

incompatibilities/inconsistencies with id3v2 tags

Reply #14 –
Quote
Complain to Apple for not supporting UTF-8 encoded frames. ID3v2 supports ISO-8859-1, UTF-8, and both big and little endian UTF-16.

Strictly speaking, ID3v2.3 supports ISO-8859-1 and UTF-16 only. Support for UTF-8 was added only in ID3v2.4; if you are writing UTF-8 but then marking your tag as v2.3, it's unsurprising that other applications are getting confused.

Quote
Of course, many applications will stick whatever encoding your machine is set to into a field and call it ISO-8859-1, which it isn't.

This is a genuine problem, and in the general case means one cannot be certain about the intended meaning of top-bit-set characters in ISO-8859-1 ID3v2 tags.

Quote
My tag component reads all supported formats, and always writes UTF-8.

A more conservative method might be to write ISO-8859-1 if all the characters in the tag are US ASCII (U+0000..U+007F) and UTF-16 otherwise -- especially if claiming to be ID3v2.3. Note that the last version of Winamp 2 that I tried doesn't read ID3v2.4.

Peter

incompatibilities/inconsistencies with id3v2 tags

Reply #15 –
This has already been resolved. Unicode writing now uses the same inconsistent UTF-16 style that half of the software out there expects. I can't vouch for everything.

ID3v2 is too convoluted, with too many varying implementations.

incompatibilities/inconsistencies with id3v2 tags

Reply #16 –
hiya ..i thought i'd drop this in here 'cos it seems approriate ..does this:
Quote
... then even more recently i've discovered that foobar2000 is removing my ID3v2 tags when i replaygain my mp3 files ..i could've sworn it DIDN'T do this when i started replaygain'ing my files ..but i've reinstalled XP on a clean partition since ..so it's a new install of foobar and maybe i'm using some different components or something ..but it's too late now... .. .

sound like the same 'problem' mentioned in this thread - the one that has since been resolved .[?].. { no i'm NOT being sarc'ky! } ..my mp3 tagger only reads up to ID3v2.3 tags and after i've replaygain'ed in foobar, the tags that were there a minute ago appear to have dissappeared ..do i need to update one of my foobar components to correct this .[?].. if so could you kindly point me in the right direction .[?]..

much appreciated :: tim ferguson

incompatibilities/inconsistencies with id3v2 tags

Reply #17 –
Quote
..do i need to update one of my foobar components to correct this .[?].. if so could you kindly point me in the right direction .[?]..

much appreciated :: tim ferguson[{POST_SNAPBACK}][/a]

Try going to Preferences > Playback > Input > Standard Inputs and see what "Tag type to write" is set to. You'll need foo_id3v2 for the ID3v2 options, which you can get from [a href="http://www.cqasys.com/projects/kode54/index.php]kode's page[/url] if they aren't already there (comes with the normal and special foobar installers). Hope that helps.
f to c to f to c
 

incompatibilities/inconsistencies with id3v2 tags

Reply #18 –
Quote
Try going to Preferences > Playback > Input > Standard Inputs and see what "Tag type to write" is set to ... Hope that helps.
cheers thanks silverbolt ..turned out that i need to check the "Always write ISO-8859-1 tags instead of UTF-16" in Components » ID3v2 tag support preferences