#68 Tag id3v2.3.0 problem

[Anonymous]

Mac (kid3 version 2.1.0):
1) If I select Preferences/Tags/id3v2/Version used for new tags = id3v2.3.0, new tags (tag2) are still created as id3v2.4.0.
2) If a tag id3v2.4.0 is converted to id3v2.3.0 by Tools, the File info "AIFF 44100 Hz 2 Channels ..." disappears from the view.
If the file with the converted tag is opened again by kid3, no tag is detected, and the file info is still missing.
If the file with the converted tag is analyzed with "soxi", the result is an error:
soxi FAIL formats: can't open input file 5 Audio Track.aiff': AIFF header does not begin with magic wordFORM'

Ubuntu (kid3-qt version 2.0.1):
1) Same behavior,
2) 2) If a tag id3v2.4.0 is converted to id3v2.3.0 by Tools, the File info "AIFF 44100 Hz 2 Channels ..." is changed to "MPEG 1 layer 1 44100 Hz Stereo".
The rest is the same as above (Mac)

The files are still playable.

BN

[Urs Fleisch]

Thanks for the report, the behaviour is reproducible. The reason is the following:
Tagging WAV and AIFF files is only supported by TagLib, and TagLib uses ID3v2.4.0. For ID3v2.3.0 tags, Kid3 uses id3lib, but id3lib does not support tagging of WAV and AIFF files. I suppose that it even would not be possible to use ID3v2.3.0 tags with such files because this tag has to be at the start of the file. The file then starts with the ID3 header and no longer with the FORM or RIFF header, respectively, so the files will no longer be recognized as AIFF or WAV.
ID3v2.4.0 tags, however, can be prepended (which is the normal case) or appended to the file, and the latter is done in the case of AIFF/WAV files.
What you have to do is to avoid using the "Convert to ID3v2.4.0" functions on files other than MP3.
What I have to do is to check the file format before converting and only read and write MP3 files with id3lib. I will fix this for the next release.

[Anonymous]

Tanks for the explanation.
I now will have to convince the people behind "Music Player Daemon" to support id3v2.4.0. These tags are currently not displayed in the "Ario" mpd client which I use on my Ubuntu Studio system.

I assume you mean "What you have to do is to avoid using the "Convert to ID3v2.3.0" functions on files other than MP3"?

BN

[Urs Fleisch]

For MP3s I still recommend (and use) ID3v2.3.0 (and ID3v1.1) because it is supported by more devices and players than ID3v2.4.0. But for WAV and AIFF, I suppose that ID3v2.3.0 is not possible, as I have explained earlier. You can even find "approved" statements on the net which say that WAV files cannot be tagged. I only know TagLib which supports it, and most software on Linux uses TagLib, so I am a bit surprised that MPD does not support it (I do not know MPD, but for libid3tag, which is on the dependency list of the mpd Ubuntu package, the package description states that it supports ID3v2.4.0 (read/write) whereas ID3v2.3.0 support is read-only).

Yes, I meant "What you have to do is to avoid using the "Convert to
ID3v2.3.0" functions on files other than MP3".

[Anonymous]

I have tested and found that mpd supports id3v2.4.0 tags at least in mp3 files, but not in aiff files. "Supports" or "fail=bug" I am not sure.
I have tested both "Ario"(Ubuntu) and "Theremin" (Mac) clients and they both show the same thing, i.e. nothing.

I am pretty sure WAV is out of the question, but AIFF should have a chance.

[Urs Fleisch]

Is now fixed in Git: Before converting to ID3v2.3.0, it is tested if the file format is supported by id3lib.

http://kid3.git.sourceforge.net/git/gitweb.cgi?p=kid3/kid3;a=commit;h=825e6c85d323d79e21bbba8c069e83f9cda80f18

[Urs Fleisch]

Is fixed in version 2.2.