Mac OS X AAC command line encoder besides FAAC? |
  |
Mac OS X AAC command line encoder besides FAAC? |
 Jun 1 2012, 22:37
Post
#26
|
|
 Group: Members Posts: 379 Joined: 16-December 10 From: Palermo Member No.: 86562  |
It seems there is something wrong in your wav files. I don't know ffmpeg options, anyway the command line you showed before seems strange to me: what's that -10 option and the minus sign right before the pipe? And in the first place, are you sure about the way wav handles multichannel? (I confess my complete ignorance on this matter)
-------------------- ... I live by long distance.
|
 |
 
|
|
Jun 2 2012, 05:13
Post
#27
|
|
|
Group: Members Posts: 11 Joined: 30-May 12 Member No.: 100283 |
"-v -10" forces ffmpeg to not output any infos (error/debug/status messages)
" - " sets the output to pipe the ffmpeg part of the command line should be fine, I use it all the time,.. to feed stuff to oggenc/lame/faac |
|
|
|
|
Jun 2 2012, 11:06
Post
#28
|
|
|
Group: Members Posts: 379 Joined: 16-December 10 From: Palermo Member No.: 86562 |
QUOTE (It's me Selur @ Jun 2 2012, 06:13)  "-v -10" forces ffmpeg to not output any infos (error/debug/status messages) " - " sets the output to pipe Ah ok, so is -v loglevel (I just would have written -v 10  ) and "no output file specified means stdout".QUOTE the ffmpeg part of the command line should be fine, I use it all the time,.. to feed stuff to oggenc/lame/faac So the troubles are on the AAC encoding side? Well, following the good old rules of thumb for troubleshooting, make a test run with the simplest case you can (i. e. two channel track) and try also to convert your current WAV files with a well known working AAC converter (say GUI version of XLD or xACT... if you can let yourself use a GUI once!  )
-------------------- ... I live by long distance.
|
|
|
|
|
|
Lo-Fi Version | Time is now: 26th May 2013 - 00:52 |
