1 ==========================================================================
2 fdkaac - command line frontend encoder for libfdk-aac
3 ==========================================================================
8 On Posix environment, you will also need GNU gettext (for iconv.m4) and
11 How to build on Posix environment
12 ---------------------------------
13 First, you need to build libfdk-aac and install on your system.
14 Once you have done it, the following will do the task.
15 (MinGW build can be done the same way, and doesn't require gettext/iconv)
18 $ ./configure && make && make install
22 First you have to extract libfdk-aac source here, so that directory tree will
23 look like the following:
24 +- fdk-aac ---+-documentation
33 MSVC solution for Visual Studio 2010 is under MSVC directory.
37 Generic tagging options like --tag, --tag-from-file, --long-tag allows you
38 to set arbitrary tags.
39 Available tags and their fcc (four char code) for --tag and --tag-from-file
40 can be found at http://code.google.com/p/mp4v2/wiki/iTunesMetadata
42 For tags such as Artist where first char of fcc is copyright sign,
43 you can skip first char and just say like --tag="ART:Foo Bar" or
44 --tag-from-file=lyr:/path/to/your/lyrics.txt
46 Currently, --tag-from-file just stores file contents into m4a without any
47 character encoding / line terminater conversion.
48 Therefore, only use UTF-8 (without BOM) when setting text tags by this option.
50 On the other hand, --tag / --long-tag (and other command line arguments) are
51 converted from locale character encoding to UTF-8 on Posix environment.
52 On Windows, command line arguments are always treated as Unicode.