ReplayGain not being applied consistently

[audioffile]

With current versions of foobar you can high light files, right click, and choose "tagging -> tag types" and uncheck APEv2 while checking ID3v2.

That's what I did, but soap reports this may not work as expected and recommended using a different tagging tool. Unless I misread what he said above.

That function means, even if you have X tags, foobar will write in your selected format when it writes changes.  With that option off it writes new/modified tags of the needed type to match the existing.

[saratoga]

With current versions of foobar you can high light files, right click, and choose "tagging -> tag types" and uncheck APEv2 while checking ID3v2.

That's what I did, but soap reports this may not work as expected and recommended using a different tagging tool. Unless I misread what he said above.

That function means, even if you have X tags, foobar will write in your selected format when it writes changes.  With that option off it writes new/modified tags of the needed type to match the existing.

Thats not the function hes talking about.  Changing the tag types the way I described has always worked for me.

[audioffile]

Thats not the function hes talking about.  Changing the tag types the way I described has always worked for me.

I already did that, but it didn't work.  . I'm still going to see what MP3Tag does. If that fails, reformat.

[audioffile]

OK, so when I was able to see all of the comments in Mp3Tag, it became obvious that evilnick was right. I just misunderstood the meaning of 'very large comment'.

That makes me wonder whether there are very large comment tags (or embedded album art) on those files, which might make the tag parser choke??

[evilnick]

If only I'd managed to capitalise the C in Comment! 

[audioffile]

Do you know how big is too big?

I still have a few other files that are failing, but cutting the comments seems to have fixed most of them.

[Lear]

The tag buffer is 900 bytes (for targets with more than 2 MB RAM), and that's used for all tags that Rockbox supports.

[saratoga]

The tag buffer is 900 bytes (for targets with more than 2 MB RAM), and that's used for all tags that Rockbox supports.

Is it possible to parse short tags like RG first so that they will be read even if the buffer is overfilled?

[GodEater]

I would imagine that's possible - but you'd have to do it by continually rescanning the file for the tags you want to find first. Doesn't seem very efficient to me.

[saratoga]

I was thinking just keep reading even when the buffer is full and if you find a RG tag, drop or truncate some less important field. 

[GodEater]

Ah ok - yes, that could work too.