Ok, first some details:
- I'm using TagScanner 5.0
- All my mp3 files have tag in version 1.1 and 2.4@utf8
- Most of mp3 files have cover image written to tag

What I do:
- Save whole tag things in TagScanner to mp3 file (both tag version, image)
- MP3 is visible in windows explorer by cover instead of filetype (Vista) <- that's I like
- Now whenever I use playcount or rating to add "special" tag to a file (any: <PLAY_COUNT>, <RATING>) the mp3 tag is breaking: cover image is no longer visible in vista explorer window and also in TagScanner editor. (I think image is not breaking in TagScanner after just <RATING>)

Is it Foobar fault ? Most probably YES, as if I turn on TagScanner on and select files, re add image and resave the files, image become visible again in vista explorer (and TagScanner of course) but rating and playcount tags are kept and still visible in Foobar. (altough after listening to a file again and PlayCount update it breakes again) ...

Any possibilities to write "special" tags without breaking rest of it ?

As far as I know, foobar2000 writes id3v2.4 tags, however Windows Explorer only supports id3v2.3 tags.

I actually face the same problem, however I use Mp3tag to re-save the tags after modifying them by foobar2000.

Not really a fault of foobar2000, just Explorer does not support id3v2.4.

Btw, I have decommissioned id3v1, as id3v2.3 Unicode support works like a charm for me.

just checked, explorer does not support 2.3 either (@utf16)
and way to force exact version of saving tags in foobar ? (like 2.3/2.4)
but on the her hand TagScanner saves 2.3 @utf16 and everything is visible in both Explorer and Foobar

Foobar can either write 1.1, 2.4 and/or Ape tags. It can also use "compatibility mode" to help support some applications that don't follow have proper tagging standards (like iTunes and WMP)

you can turn on compatibility mode in preferences -> Advanced.

Thanks, unfortunately Compatibility Mode stops writing special tags like Rating ...

Most applications that "compatibility mode" is designed for blow up if you try to give them a custom field, so this should be expected, as it is probably necessary.

Another work around would be to have 1.1 tags for broken apps and use 2.4 tags for Foobar.

While it's still not recommended to be used except for compatibility with broken applications, custom tags are written as of version 0.9.5.

thanks Frank Bicking, i've get beta version and it's indeed working correctly.

Sigh, it is the problem of TagScanner.

I am using Vista Business, so I know of course.

Edit: Sorry moderators.



Moderation: Please do not inline images larger than roughly 800x600 and 80KB. Please use thumbnails and/or links for large pictures instead.