QUOTE(Dunc-uk @ Jan 4 2008, 15:39)

I opened the file I sent you in a hex editor myself. What I found was that there are two ID3v2 tags as you say... one ID3 v2.3 and one v2.4. This is entirely reasonable. ID3v2.4 is apparently only supported by a few software players, if you want id3v2.4 then it makes some sense to include ID3v2.3 as well for backwards compatibility (instead of ID3v1 for example).
Well, this is clearly not what you were trying to do. Did you try and load that file in some app that only supports id3v2.3 anyway?
QUOTE(Dunc-uk @ Jan 4 2008, 15:39)

Having both tags is no more or less non-standard than having id3v1 and id3v2.3, for example.
I think it is pretty different.
QUOTE(Dunc-uk @ Jan 4 2008, 15:39)

Not to mention that the spec says it is allowed.
This is what the
id3v2.3 spec says:
QUOTE
The ID3v2 tag header, which should be the first information in the file, is 10 bytes as follows:
It was the second tag in your file of course, so not the first information in the file.
This is what the 2.4 spec says:
QUOTE
The default location of an ID3v2 tag is prepended to the audio so
that players can benefit from the information when the data is
streamed. It is however possible to append the tag, or make a
prepend/append combination. When deciding upon where an unembedded
tag should be located, the following order of preference SHOULD be
considered.
1. Prepend the tag.
2. Prepend a tag with all vital information and add a second tag at
the end of the file, before tags from other tagging systems. The
first tag is required to have a SEEK frame.
3. Add a tag at the end of the file, before tags from other tagging
systems.
I didn't see any explicit reference in the actual specs to multiple tags at the beginning of the file (maybe you could point me to those), and mixing v2.3 tags and v2.4 tags. What you linked was some developer guidelines, again not about mixing v2.3 tags and v2.4 tags but metadata changes in internet streams (and it also mentions a lack of distinct files which we have here).
QUOTE(Dunc-uk @ Jan 4 2008, 15:39)

Do you still think it is worth me complaining to EAC about "brain dead tagging".
Yes. You can set it to write v2.3 tags right? If you do that, does it still add a whole new tag?
QUOTE(Dunc-uk @ Jan 4 2008, 15:39)

(The null padding is for the ID3 tag itself, so that new entries can be added to the tag without a complete file rewrite)
Right. I didn't say otherwise.
QUOTE(Dunc-uk @ Jan 4 2008, 15:39)

The issue is that "fixing" my existing tracks is nightmarishly difficult. Foobar will not tell you which variants of id3v2 exist in a given file (nor, more importantly let you create a playlist with just those files), only that one or more of them exists. So I have no trivial way to make a playlist with just those files in, such that your suggested workaround can be applied. If any one of the files in the playlist has only one ID3v2vX tag, then it will be thrown away. The only alternatives are all extremely laborious manual processes which would take far longer than it would to fix what I can only assume is a fairly trivial piece of code
All you are proving is that it is entirely impractical (for you/a user) to work with files with multiple id3v2 tags at the beginning. I am pretty sure that method I mentioned to remove the first tag using foobar2000 isn't by design, just a result of it not expecting multiple id3v2 tags in this manner. Unticking ID3v2 and then opening the dialog again to see it ticked again should be a good indicator of that.
QUOTE(Dunc-uk @ Jan 4 2008, 15:39)

(not wishing to reignite this argument, but I would happily fix it myself if the source were open).
Try a hex editor and disassembler instead then? What did you really expect me to say to that?
QUOTE(Dunc-uk @ Jan 4 2008, 15:39)

Even if I manage to "fix" all my files... the next sync will take forever as your plugin needlessly deletes compliant files and copies them back again, stressing the HDD and probably fragmenting the files.
No it is not needless. You modify the file, it gets updated on the iPod. Metadata etc. *is* important information. One example of the iPod using it is that it reads lyrics directly from the id3v2 tag.
QUOTE(Dunc-uk @ Jan 4 2008, 15:39)

If the iPod has ever had troubles playing these files, it certainly doesn't for me on the current firmware.
As far as I am aware it was just an issue on the iPod Classic/Nano 3G. It didn't sound like you had one of those.
QUOTE(Dunc-uk @ Jan 4 2008, 15:39)

[EDIT] I've found another reason why your workaround is poor. Foobar removes the first ID3v2 tag it finds, which is the one it updates. This means that any changes you've made to id3 tags in foobar since you originally ripped the track are lost, it returns to the original ripped state.
Well, I knew that. I don't know why you blame my workaround though when you are just showing you don't have a practical way to manipulate that second tag.