Here is a FLAC Comment Editor that I wrote. It was written in C#, so you need the .NET v1.1 Framework to run it (available in the "Windows" section of Windows Update).



As you can see, it supports unicode. The "Freeze values" checkbox makes it so that the textboxes aren't changed when you load a file, which is useful for tagging a whole album (you only have to change the title and track number each time). A few notes:

- The Winamp plugins don't appear to support unicode, so for now unicode characters won't show up properly in Winamp.
- It uses the "COMMENT" field to store comments (like X-Fixer's Winamp plugin), instead of "DESCRIPTION" which the reference Winamp plugin uses.
- If the FLAC has no comment header present (FLAC's encoded with 1.0.4 or earlier, I believe), an empty vendor string will be written (I don't think this matters, the Winamp plugin doesn't have a problem with it).
- It doesn't have much error handling, so if you do something like open a non-FLAC file, expect it to crash . It shouldn't mess up your files though (read next note...).
- It hasn't been tested by anyone other than myself, so backup the first few files you use it on (I highly doubt it would mess up a file, especially since it rewrites all the metadata including the comments in a temporary file first, and then copies it back into the real file... but still, better safe than sorry).

I know it's pretty basic, but I like it , so I decided I would share it. Let me know if you find any bugs, and possibly suggestions (I don't know that I will be working on it much though).

If you are using the metadata interface in libFLAC, then FLAC__metadata_object_new(FLAC__METADATA_TYPE_VORBIS_COMMENT) should give you an object with the filled-in vendor string.

Josh

Actually, I re-invented the wheel . This project was mostly for fun, and to help me get more familiar with C#/.NET.

Is the vendor string for the program that encoded the file, or the tagger? I assume the former... In that case, what should I be putting in there?

It's supposed to be for the encoder... now that I think about it, for the case you are trying to cover you should probably just leave it blank then.

Josh