[BeSweet] - Upgrading to a newer version of LAME?

[mob]

Hey guys,

BeSweet hasn't been updated since 2005 but it is still my favorite transcoder (or at least the only one that I know about that does the job right).

Anyway, BeSweet comes with a very old version of LAME and I need to upgrade it to v3.97. Is there any way to do that? Would this old version of BeSweet even be able to use the new LAME?

Thanks!

[Digga]

Hey guys,Anyway, BeSweet comes with a very old version of LAME and I need to upgrade it to v3.97. Is there any way to do that? Would this old version of BeSweet even be able to use the new LAME?just replace the LAME version included in BeSweet with a newer one (i.e. overwrite lame_enc.dll), that should work fine.

you can get LAME v3.97 from here:
http://www.rarewares.org/

[mob]

Thanks for the info Digga :)

That's exactly what I did and I made an MP3 with the command -V 5

However, the log file that BeSweet created said it was 128K CBR.

So I'm wondering, does BeSweet really work with this new version? or should I stick with the old one? I'd really like to use the new one though.

[tebasuna51]

Use:
-lame( -v --vbr-new -V 5 -b 32 )

[mob]

Use:
-lame( -v --vbr-new -V 5 -b 32 )

cool thanks a lot, I will give this a try right away and see how it goes.

btw, can you explain that command to me? Like, what is the difference between -V 5 and -v --vbr-new -V 5 -b 32 ?

I'm just trying to understand it better. Thanks.


edit:
I just tried your command and it worked. But how come? What was wrong with my original command?

Also, something strange is happening when I play the output MP3 file in Media Player Classic. I see the length of the track keeps changing as the file is being played. What's the deal with that? :confused:

[tebasuna51]

btw, can you explain that command to me? Like, what is the difference between -V 5 and -v --vbr-new -V 5 -b 32 ?
...
I just tried your command and it worked. But how come? What was wrong with my original command?

The parameters to BeSweet command line, -lame( param ), are not translated literally to lame and can't be compared with parameters for Lame.exe.

BeSweet is closed source and not upgraded by the author, then new features can't be translated. The best aproach to use BeSweet now is use the GUI BeLight than try adapt BeSweet to new encoders.

Also, something strange is happening when I play the output MP3 file in Media Player Classic. I see the length of the track keeps changing as the file is being played. What's the deal with that?

To know the duration of VBR files there are 2 options:
- Read all the file to see the number of samples (slow method for players) or
- Read a field in the header than inform about the full duration of the file. Lame.exe put this info in the first frames of the file by default, unless you put the -t parameter.

Seems BeSweet-lame.dll don't put this info. I don't test this because I always use lame.exe.

EDIT: BeSweet-lame_enc.dll don't produce identical results than lame.exe but the duration info is ok like you can see with Winamp for instance.

The MPC info change with files produced by dll or exe because seems don't read the header duration field, and use the file size with the bitrate average of played frames, then until the average don't reach the final value the duration is inexact.

[mob]

Thanks for the explanation tebasuna51 :)

To tell you the truth, I'd also like to use LAME.EXE but the only problem is that I need to convert some MP3's from PAL to NTSC and BeSweet is the only tool I know of that can do it. :(