I have read in this forum that, by default, Mp3tag pads ID3v2 tags to 2048 bytes.
I wonder if this mean that Mp3tag adds 2048 bytes of padding (extra null bytes), or if it means that it sets the entire tag size (header + frames + padding) to 2048 bytes? I cannot convince myself one way or the other.
Because I had read that Mp3tag pads 2048, I chose that for my LAME encoding, figuring that Florian is pretty wise, so this must be a good padding size. So I have used (in LAME)
V0 --id3v2-only --pad-id3v2-size 2048
After LAME encoding, I check my files with mp3diags, and the ID3v2.3 tag shows padding=2048.
If I subsequently resave my tag in Mp3tag, the padding size reported by mp3diags generally decreases.
So I'm left wondering what Mp3tag is doing with padding.
As asked above, is the target 2048 the padding, or is it the entire tag size?
Does Mp3tag actually remove padding under certain circumstances? If so, why? And can this be controlled by the user?
If Mp3tag is removing padding, could this eventually result in having to rewrite the entire file when I edit the tag in the future? Or can Mp3tag increase the padding again at a later date, to prevent this?
Can someone explain how padding is set when I CREATE a tag in Mp3tag, and how padding is changed when I re-save a tag with Mp3tag?
Many thanks for help on this. My apologies if I have overlooked a write-up on this somewhere. I have done my best to search it out.