Need help with command parameters for FhG AAC Options

[Pulstar]

I tried various options but it seems I can't get a "solid" file output. Perhaps someone could help me out with the appropriate parameters for fb2k's converter?

[Shadoko]

Command Line Encoder Settings - Editing Preset


Encoder: Custom
Encoder file: yourpath\fhgaacenc.exe
Extension: m4a
Parameters: --vbr 4 --ignorelength - %d

lossy
24

[A_Man_Eating_Duc...]

here you go



EDIT: too slow

This post has been edited by A_Man_Eating_Duck: Nov 1 2012, 20:09

[Pulstar]

CODE

1 out of 1 tracks converted with major problems.

Source: "C:\Users\X\Music\sample.mp3"
  An error occurred while writing to file (The encoder has terminated prematurely with code 0 (0x00000000); please re-check parameters) : "C:\Users\X\Music\sample.m4a"
  Additional information:
  Encoder stream format: 44100Hz / 2ch / 32bps
  Command line: "C:\Program Files (x86)\foobar2000\components\fhgaacenc.exe" --vbr 3 --ignorelength - "sample.m4a"
  Working folder: C:\Users\X\Music\
  
  Conversion failed: The encoder has terminated prematurely with code 0 (0x00000000); please re-check parameters

[lvqcl]

Encoder stream format: 44100Hz / 2ch / 32bps

Did you set 'Highest BPS...' setting to 32 instead of 24?

[Pulstar]

Encoder stream format: 44100Hz / 2ch / 32bps

Did you set 'Highest BPS...' setting to 32 instead of 24?

Yes, thanks for offering further help. I guess it's something with stdin/stdout.

[A_Man_Eating_Duc...]

have you got all the required files in the same directory as fhgaacenc.exe?

CODE

enc_fhgaac.dll
fhgaacenc.exe
libmp4v2.dll
libsndfile-1.dll
nsutil.dll

[Pulstar]

Yes! I will try to move the files to another directory, but I don't think it's a permissions problem since I have UAC disabled.

[A_Man_Eating_Duc...]

don't forget this bit

Install VC2008 runtime if you don't have yet
http://www.microsoft.com/downloads/details...0D-3802B2AF5FC2

[Pulstar]

I have all the runtimes hehe.. I guess I will have to use the command prompt to encode the files. Thanks for everyone who pitched in.

Is there a GUI for this encoder? I don't want to install Winamp

This post has been edited by Pulstar: Nov 3 2012, 10:39

[A_Man_Eating_Duc...]

Try running the command line manually from the CMD prompt and see if it works.

[Pulstar]

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.

[nu774]

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

Not reproducing here. Please show me console message of fb2k.

[Pulstar]

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.

[nu774]

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.

[Pulstar]

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

[nu774]

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.

1. 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.
2. 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.
3. 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.