[Abcde-users] abcde using LAME options different from LAMEOPTS

[Steve McIntyre]

Hi Bruce!

On Mon, Jul 13, 2020 at 02:39:34PM -0700, Bruce Albert wrote:
>
>This is abcde v. 2.9.3 running on ubuntu linux 20.04.
>
>the LAMEOPTS line in .abcde,conf says:
>
>LAMEOPTS='-m j -V 0 -q 0 --vbr-new'
>
>But what I see in mediainfo run on a file ripped with it is:
>
>-m j -V 0 -q 0 -lowpass 22.1 --vbr-mt -b 32
>
>That isn't what I asked for.  Ripping the same file with RipperX produces:
>
>-m j -V 0 -q 0 -lowpass 22.1 --vbr-new
>
>which is what I wanted.
>
>And yes, the spectrograms on the files are slightly different.
>
>This is NOT a question about whether it matters or why; what I want to know is why abcde isn't doing
>what I ask for, and is there some option I have failed to set so that it will use the options I specify?

Sorry, but I'm genuinely not sure where you're getting those options
from - abcde does not have *any* code to change LAMEOPTS from what you
set, and there is no mention of "vbr" anywhere in the code that I can
see. If you run with debug enabled, check the log and look for the
lame command line maybe?

-- 
Steve McIntyre, Cambridge, UK.                                steve at einval.com
"... the premise [is] that privacy is about hiding a wrong. It's not.
 Privacy is an inherent human right, and a requirement for maintaining
 the human condition with dignity and respect."
  -- Bruce Schneier