Page 1 of 1
Bug in ID3v2 tag?
Posted: Tue Mar 03, 2009 6:02 pm
by simonc2
When exporting a project as MP3 I've noticed that any value I put in the Year box in the ID3v2 tag editor doesn't seem to register in the output mp3 file. When editing the file in an editor I can see the text for the year I entered but maybe Audacity is putting this in the wrong place for a v2 tag, and other software doesn't recognise it.
Is this a bug? Can anyone else reproduce this?
Grateful for advice.
Re: Bug in ID3v2 tag?
Posted: Tue Mar 03, 2009 6:51 pm
by steve
ID3v2 is not really a "standard". As Captain Barbosa would put it "it's more like a guideline".
Different applications have different interpretations of ID3v2 tags and there is a lot of variation. It is generally recommended to tweak the tags as necessary using whatever is your primary application for ID tags. (if you mostly use WinAmp, tweak the tags in WinAmp - If you mostly use iTunes, do it in iTunes).
Re: Bug in ID3v2 tag?
Posted: Tue Mar 03, 2009 7:36 pm
by waxcylinder
simonc2 wrote:Is this a bug? Can anyone else reproduce this?
This is a known
"feature" in 1.2.x - I'm not sure if it still exists in 1.3 as I tend to edit my tags in iTunes (I export as AV and import into iTunes as AAC).
WC
Re: Bug in ID3v2 tag?
Posted: Thu Mar 05, 2009 2:04 am
by Gale Andrews
Many common Windows media players expect an ID frame called "TYER" to indicate the year, even though "TDRC" is correct for the current ID3 specification. If this is really a nuisance for you, update to 1.3.7 Beta, or wait for the new 1.4.0 stable to come out. We've reverted there to TYER and made a lot of changes so tags should show up in other players a lot better.
Note: In either case you'll need a new lame_enc.dll. The one we link to off the main site might have issues in some cases, so use this one if you change to 1.3.7:
http://www.gaclrecords.org.uk/lame_enc.dll
Exit Audacity. Remove any older versions of lame_enc.dll from the folder where you have 1.3.7 installed, or from the "Plug-Ins" folder within that. Place the new lame_enc.dll into the Audacity installation directory. Audacity should detect the .dll file there immediately when it restarts.
If there are any further problems, they will likely be due to a conflict with Audacity still trying to read the preferences path to the old .dll file. To ensure this is corrected, exit Audacity, then reset your preference settings file at:
Documents and Settings<user name>Application DataAudacityaudacity.cfg
To do this, open audacity.cfg in a text editor, delete the two lines starting with:
[MP3]
MP3LibPath=
and save the changes.
Gale