I've switched to QAAC now, and it works nicely. However there's a new quirkiness: The capital V switch for True VBR doesn't function unless I write it like so e.g. -V90 if I write it -V 90 it just defaults to its, er default value. Too bad Nero seems to be discontinued, I liked it, but it's time to move on.

I've switched to QAAC now, and it works nicely. However there's a new quirkiness: The capital V switch for True VBR doesn't function unless I write it like so e.g. -V90 if I write it -V 90 it just defaults to its, er default value

I don't get an error message, but the resultant files are always the same size regardless of the TVBR switch value, unless I write it concatenated.

Strange. Version of qaac? And I'd like to know exact command line which should be printed in the console of fb2k (view->console).Also, try it from directly command line. qaac will show something like the following by which you should know if TVBR quality value is misinterpreted.

CODE

AAC-LC Encoder, TVBR q63, Quality 96

Although you can specify 0-127, it is rounded to the nearest available value. In case you specify 60, you will get 63.

Hmmm it seems that spaces in the path screw up the V switch for me, no big deal. Just tested this with a sample on the root folder, and the resultant file sizes are similar. Thanks for the help

Whiltespace in the pathname of input file has nothing to do with space in "-V 91" (or something).They are completely different things.

Pathname of input has nothing to do with a CLI encoder. It's fb2k who opens it and decodes it. fb2k then feeds decoded audio to the encoder via pipe or temporary file.

Also you don't have to care about pathname of output (placeholder %d) . fb2k will take care of it for you so that even a CLI encoder which doesn't handle Unicode pathnames will work.

Command line parser of qaac is based on BSD getopt (modified to handle Unciode), and capable of both "-V91" and "-V 91" style (for short options).

"Similar size" of resultant files doesn't prove nothing. If you are using fb2k, just open up property dialog for the song, and look at "tool" tag information. You can see VBR quality or something. Alternatively, you can use tools like Mediainfo.

I've recently installed Win 7 (Pro 64) and am trying to get everything set up but I'm having problems getting FB2K to work with the Fhg AAC encoder.

FB2K is set up as per A_Man_Eating's example in Post 3. enc_fhgaac.dll, fhgaacenc.exe, libmp4v2.dll, libsndfile-1.dll & nsutil.dll are in the same folder. But I'm getting exactly the error that Pulstar reported in Post 4. As it's a fresh install I assume it won't be related to VC2008 runtime.