> :: There are a lot of core dumps!
> ::
> Sorry. The results are not sooo bad. I switched to max quality via "-q 9".
> "-q 9" seem to be not very good tested.
> File is to be found in "http://www.uni-jena.de/~pfk/resample.tar.gz".
>
> Every Coder uses other command line switches with another meaning.
>
> FhG: -qual 0 min -qual 9 max
> Lame: -qual 9 min -qual 1 max
>
Hi Frank,
-q n is an undocumented flag used only for internal testing, and
thus most values of 'n' do not work. The qval scale was
chosen to be consistent with the -V n option. The -V option
is scaled from 0=best to 9=worst because originally, the
value of 'n' was the number of bands for which distortion
was allowed to be > masking. It is far too late to change
this now!
Right now, the only -q values which are tested on a regular
basis are:
lame -f (uses -q 7)
lame (the default, uses -q 5)
lame -h (uses -q 2)
Another point: I notice you changed the encoding status display to
update every 2 seconds, rather than every 100 frames. Any reason for
this? I prefer 100 frames because I like looking and nice round
numbers, and it doesn't impact the speed. Also, to do the 2 second
update, you had to introduce a static variable to lame.c: this is a
bad idea since we are trying to remove all static variables (except
constants) to make the library thread safe. However, the whole
timestatus.c package is not thread safe, and the status display
wouldn't be used by someone doing multiple encodings within a single
executable, so it doesn't really matter.
Mark
--
MP3 ENCODER mailing list ( http://geek.rcc.se/mp3encoder/ )
