Well, anytime I do anysort of tag editing in foobar, including adding replaygain info, foobar thinks it'd be a good idea to insert a space in between every single letter. So if I'm naming from tags, a certaing file might be called "mu-Ziq - Bilious Paths - Fall of Antioch.mp3". I apply replaygain info, and then name the file from the tag again, the new name for the file is "m u - z i q - B i l i o u s P a t h s - F a l l o f A n t i o c h.mp3"

What's the deal!?

It would help if you could show us the renaming script you're using..

The renaming script is **** LM-1, in heavy use over at *****. you can download it here, if you like:
*****
it adds two right click options for folders: **** check, and **** enforce. Check will check the folder (presumably an album of music) for compliance with the ***** standard, and Enforce will either bring the folder up to standard, or mark it as errored. This program has been working fine for me for over a year now, and no similar problem arises when using other mp3 editors, such as MP3 tag studio.


MOD.: Please no links to or names of sharing groups, thanks.

So you're using an external renamer.

Oops. You said the files get spaces in the tags after you edit the tags. OK. So which tags are you using on your files? ID3v1? ID3v2? Both? ID3v1+APEv2? If you use ID3v2, how have you got it set up?

Somehow I suspect this is a problem of **** LM-1 not supporting UTF-8 or something like that.

Does foobar2000 show the spaces in the tags too?

I'm using both ID3V1 and ID3V2 in my tags, and it appears that foobar recognizes and displays the tags correctly.

Not sure what you mean by "how do you have ID3V2 setup?" ....EAC generates the tags, if that helps.

So is this a problem with the renaming program? Some jibber jabber about utf-8?

Well, problem solved.

I had to go to preferences > components > ID3V2 Tag support and check the box labeled "Write ISO-8859-1 tags instead of UTF-16"

Thanks for the help!

Tell the author of that script/tool to properly support the ID3v2 standard if he's interested in not causing more problems for his users.

New foo_id3v2 v1.15, lossless fallback to ISO-8859-1 on a frame by frame basis. That's right, no UTF-16 unless the frame needs it. Still, external software should support all ID3v2 features, or blow up when unsupported features are detected. Pain in the ass that it may be.