Hi,

as we all know, per default lame 3.92 adds an idv2-tag if one of the fields doesn't match. Lame also leaves the idv1-tag though it might know that this idv1 is not complete at one of the fields... Lame should delete the idv1 automatically if it detects need of a v2 and as it knows the v1 must be broken. This would be a very good conservative setting.

Yesterday I was playing around with winamp2.8 and a TitlySpy plugin, which reads the IDv1 and writes it to disk while playing. It only reads the IDv2 if the v2 is the only tag...

As some software only handle id3v1, I think that it is better to always append v1 tag.

OK this is a point. Maybe an option would be helpful, which makes lame add a single v2 (and not a v1) if the fields don't suit?

--add-id3v2 force addition of version 2 tag
--id3v1-only add only a version 1 tag
--id3v2-only add only a version 2 tag

You should use the --pad-id3v2 option too

Here's what I use in EAC:
--alt-preset standard --id3v2-only --pad-id3v2 --tt "%t" --ta "%a" --tl "%g" --ty %y --tc "EAC: Lame 3.92 @ alt pre std" --tn %n --tg "%m" %s %d

It works fine in Media Jukebox, iRiver iMP-350, and anything else that displays tag info.

Xenno

What's the reason behind this option again? I don't have any trouble with v2 tags without it.

thanks
--jth

Well, I think that the extra room allows tag string length addition/subtractions without requiring a total rewrite of the file to your HD. As you know v2 tags are stored in the front of the file. I've got a more than a few 10 MB+ mp3's (using --alt-preset-standard in EAC). I'm able to modify tag contents and save quickly (though I never batch edit).

Maybe Gabriel has some input on this.

Xenno

But this there is no option which does the following (pseudo-code):

if (idv1-allfields_suit)
add_idv1
else
add_idv2
endif

...which applies only ONE minimal id3-tag.