Encoding mp3 VBR instead of ABR

Restricting max bitrate is a bad idea because you are losing the benefit of VBR of using higher bitrate for a difficult-to-encode passages.

Well, I will not limit max bitrate and I will turn off error protection. And what about Lowpass filter. Regards

Error protection is already off by default. Lowpass is already internally adjusted according to the -Vx value used. -V5 and --abr 128 will use similar lowpasses.

Note: Besweet comes with the LAME 3.90 dll, not the lastest 3.97 version. Also it sets the minimum bitrate to 128kbps for all VBR modes, so you'll need to use -b 32 if you want it to behave like the CLI version of LAME.

Hi, jordisound. Try again with a current . At least the newest daily build gets the new-style lame commandline right - though you'll have to add "-b 32" manually. (I've addressed the issue in the BeLight thread.) I don't know about the JS problem. What is DC anyway? Using "-m j" shouldn't be necessary because it's default already. Which software are you using to analyse your MP3s? Another unrelated thing: Your BeLight commandline above normalises twice (with azid's --maximize and OTA's -hybridgain) but once is enough. Usually you should use OTA. Only 6ch Vorbis or AC3 output require azid normalisation.

@JordiSound Sorry, you are true about the -v parameter. I mistake Lame CLI docs. with BeSweet-Lame parameters. For BeSweet is necessary -lame( -v --vbr-new -V x ...) About the channel mode JS <-> DC. I make test, and with BeSweet I obtain Join Stereo and Stereo but can't obtain Dual Channel Using -m s/j/f/d with Lame encoder 3.97b2, and after analysing the headers of output files, work OK: Code: