HydrogenAudio

Hosted Forums => foobar2000 => General - (fb2k) => Topic started by: 2zrg on 2024-04-23 15:23:25

Title: Lame Settings for Foobar Conversion, CBR 128
Post by: 2zrg on 2024-04-23 15:23:25
Hi there,

I am looking for the parameters for foobars Mp3 conversion within this settings:

(https://i.imgur.com/3HCyInr.png)

I just want to create a CBR 128 lame profile (for car audio). (I dont't know if I have to use --replaygain.)

Can somebody help me out?

Thanks
Title: Re: Lame Settings for Foobar Conversion, CBR 128
Post by: jaybeee on 2024-04-23 15:41:09
Code: [Select]
-S --noreplaygain -b 128 - %d
Title: Re: Lame Settings for Foobar Conversion, CBR 128
Post by: Apesbrain on 2024-04-23 15:55:19
And update the "Display" info at the bottom.
Title: Re: Lame Settings for Foobar Conversion, CBR 128
Post by: 2zrg on 2024-04-23 16:25:35
Code: [Select]
-S --noreplaygain -b 128 - %d

Thank you! I was experimenting with -b 128 without the "s" (which didn't work)....
Title: Re: Lame Settings for Foobar Conversion, CBR 128
Post by: 2zrg on 2024-04-23 16:30:09
And update the "Display" info at the bottom.

Done ;)
Title: Re: Lame Settings for Foobar Conversion, CBR 128
Post by: eahm on 2024-04-24 00:04:14
I put together some encoders settings here if you'd like to check how they are configured and all that: https://hydrogenaud.io/index.php/topic,104627.msg1010390.html#msg1010390
Title: Re: Lame Settings for Foobar Conversion, CBR 128
Post by: Case on 2024-04-24 08:20:13
I don't see anyone replying to your original wondering about the need for --noreplaygain. That command line parameter is there to make the encoding faster by preventing lame from computing a track gain for the file. If you don't care about ReplayGain, calculating the gain values is a waste of processing power. If you do care about ReplayGain, calculating only the track based values is most likely a waste of time. It's better to let foobar2000 calculate both track and album based values once encoding is done. And not only is foobar2000's scanner more optimized and faster, it also offers several advanced options people may like.

The -S is there also for performance reasons. It tells the encoder it doesn't need to waste any cycles printing progress/histograms to the non-existing console screen that no one can even see.
Title: Re: Lame Settings for Foobar Conversion, CBR 128
Post by: 2zrg on 2024-04-24 14:03:44
I don't see anyone replying to your original wondering about the need for --noreplaygain. That command line parameter is there to make the encoding faster by preventing lame from computing a track gain for the file. If you don't care about ReplayGain, calculating the gain values is a waste of processing power. If you do care about ReplayGain, calculating only the track based values is most likely a waste of time. It's better to let foobar2000 calculate both track and album based values once encoding is done. And not only is foobar2000's scanner more optimized and faster, it also offers several advanced options people may like.

The -S is there also for performance reasons. It tells the encoder it doesn't need to waste any cycles printing progress/histograms to the non-existing console screen that no one can even see.


Thanks for the info.

Then I guess the only important part here:
Code: [Select]
-S --noreplaygain -b 128 - %d
is the "-b 128" right?

Title: Re: Lame Settings for Foobar Conversion, CBR 128
Post by: Apesbrain on 2024-04-24 16:49:55
Then I guess the only important part here:
Code: [Select]
-S --noreplaygain -b 128 - %d
is the "-b 128" right?
Well, some of those other parts are important as the conversion won't run without them. But, yes, you've got the idea.

The bitrate options are CBR, ABR (rarely used), and VBR:
https://timothygu.me/lame/usage.html

For playback in the car, I typically encode to -V4.