This may be a bug in vorbiscomment.exe:

If I type:



It creates the file "file.ogg.vctemp".

Isn't it supposed to replace the original instead of creating this temp-file?
I've checked to make sure "file.ogg" is not write-protected or in use by WinAmp or other application.

However, this works as expected:



It creates the file "out.ogg".

And, is there any way to pass UTF8-encoded string to vorbiscomment? As it is now, it doesn't seem to support them.

I used vorbiscomment from Winvorbis 1.33

I don't believe it's bug but feature. If you look at usage screen of Vorbiscomment you see that it requires output file as parameter. The way I see it they still allow running with only input name but they don't want to overwrite the original if user was unintentionally running the command incorrectly.


I think not, vorbiscomment automatically converts text from users codepage to UTF-8.

BTW. I don't think the vorbiscomment developer reads this board. If you notice anything, it's better to use http://bugs.xiph.org

--
GCP

Ok, but I don't want to rename all files after I've put tags on them.

Well, so I tried this:

Now "file.ogg" ends up at 0 bytes...



Yes, but I was thinking when passing arguments from another program (frontend). Ansi-chars is no problem but how should for example Greek or Cyrillic characters be passed? That why I thought it would be a good idea if vorbiscomment could accept already-UTF8-encoded strings as parameters.