D/l'ed the 3.98 release of LAME and I'm experiencing the following problems with Razorlame...

1) Encoding is VERY slow compared to V 3.97
2) Histogram doesn't work
3) Progress bar is very "jumpy" and inaccurate
4) Original WAV files don't delete after encode

I'm encoding @ 192/V=0 with bass rolloff at 19.2k

Any one else having similar problems?

@192 kbps w/ -V 0...?
Or did you mean -q 0...?

OTOH, why don't you just use the presets?

- razorlame is known to cause problems with newer lame versions. Use another frontend.

- lame 3.98 is an alpha-version - expect problems.

If RazorLame gets an "unknown" message from Lame, the wavs won't be deleted.

More about this:
http://www.dors.de/phpbb/viewtopic.php?t=336

Yeah- -V 0

Bum keyboard a/o bum typist.

Yeah- makes sense.

I haven't used the frontend for too long, at least not to the point of seeing all of the errors that can happen

Nasty messages when you try to encode at 194, I know that

Any other frontends I might try, just for the sake of funnin'? I'm just now getting into experimenting w/this command line thing, as if I haven't let THAT be known...

I was a die hard Razorlame user until the newer CODECs started to cause it grief, then someone else here recommended All2Lame, which to my mind is even better.
It allows you to store presets via a dropdown menu so it's really easy to change the encoding profile.
The only thing it doesn't offer is to delete source files after encoding.
But, that's a small price to pay.

Here is the link for All2Lame.

Regards,
Madrigal

Thanks for that Madrigal.

Do newer versions of LAME have a more precisely placable lowpass or something?

Last I knew, LAME lowpassed at intervals of 500Hz, so there's no 19.2 lowpass, but rather 19 and 19.5... ?

I recommend (again) Frontah.