mp4 command line tagger
Reply #62 – 2005-11-25 16:09:48
here special characters, like ä ö ü are not displayed correctly [a href="index.php?act=findpost&pid=341149"][{POST_SNAPBACK}][/a] thats because tg.exe does NOT do any conversion to utf-8. if you want your tags to be in correct utf-8 you need to feed tg.exe with utf-8 and this is NOT possible with .bat files (as these are stored as ANSI) however there is a way to use windows to feed tg.exe with utf-8: 1) run the dos console (normally under start -> programs -> tools -> dos) 2) type chcp 65001 which will change the console to use utf-8 3) go to the console settings and change from "rasterfont" to "lucida console" under "fonts" 4) type the commandline normally placed in your .bat file as always 5) enjoy your tags in correct utf-8 (also shown correctly in itunes/quicktime) if you dont do this on windows you dont have your tags stored in utf-8 and quicktime/itunes doesnt display special characters correctly apart from that someone warned me that tg is not save to use as it seems to fuck up some atoms, also if you tag a file multiple times with it you will get duplicate atoms (look at them in dumpster), so tg is propably not save to useI don't have quicktime 7.03 installed, so I can't say anything about that, but I see you testing with the "tg" binary. You should be careful with it. After some.... massaging, I managed to compile it on Mac OS X. First of all, if your udta atom (I think) is over 200,000 bytes it bombs out (easily fixed). But then it also strips all but a handful of atoms in "moov.udta.meta.ilst". Granted, most I don't care about. On a sample iTunes purchases song, it worked: worked at stripping 21 atoms to 7. And it removed my "covr.data" atom. Besides that, while it deleted those atoms, all it did was make a "free" atom: 460kb worth of null space. That amounted to 11% - a heavy price if you do it a huge number of files. Not to berate the author of the software, because I know we all start somewhere, and it was a good crack at it, but just know that that tagger isn't idyllic (although none really are), and there are compromises in using that tg.exe tagger.