Old lame commands not working for v3.99.5 in CLI Encoder

[TakuSkan]

I just upgraded my lame v3.98.2 to v3.99.5 from Rarewares and found my very old, very simple command line for CLI Encoder doesn't work anymore:

[infile] [outfile] --preset 128

I've used that for years. But I can't seem to get any v3.99.5 command to work. I uninstalled the old version of CLI Encoder and downloaded and installed the new Release 4. But I still get any commands to work for me.

Any feedback would be much appreciated. Obviously I don't do this very often. :-D

[Spoon]

Re: Old lame commands not working for v3.99.5 in CLI Encoder

You would have to check your --preset 128 command is valid in the latest lame encoder (try to encode a wave file without dbpoweramp).

[TakuSkan]

Re: Old lame commands not working for v3.99.5 in CLI Encoder

Just ran this with v3.99.5 on a test file and it worked fine from the command line:

lame --preset 128 b.mp3 c.mp3

[Spoon]

Re: Old lame commands not working for v3.99.5 in CLI Encoder

in file and out file should be enclosed in quotes

[TakuSkan]

Re: Old lame commands not working for v3.99.5 in CLI Encoder

in file and out file should be enclosed in quotes

Hmmm... Maybe another quirk of the new lame, as it did in fact process the file properly.

EDIT: Just tried it with v3.98 without quotes and it worked fine. The -? help info doesn't show any need for quotes:

RECOMMENDED:
    lame -V2 input.wav output.mp3

That was running lame from the command line. I and using bracket quotes in CLI Encoder

[TakuSkan]

Re: Old lame commands not working for v3.99.5 in CLI Encoder

Have you had a chance to try this yourself spoon?

EDIT: I just tried v3.99.5 in a copy of dbPoweramp on an old notebook with Vista, and CLI Encoder had no problems processing the file. Seems to be some issue between dbpoweramp and that Windows 7 system. Will give it a try on another Windows 7 system.

[TakuSkan]

Re: Old lame commands not working for v3.99.5 in CLI Encoder

Worked fine on a Win7 x64 system... went back to Win7 x32 system and ran a test without touching anything... and it worked fine. Must have been a Win7 issue that just needed rebooting. I could swear I did that tho' ... reboot is basic Windows Repair 101

I did notice that Lame 3.99.5 writes a metadata value for encoder as Lame 3.99r. And when checking the properties for the lame.exe file, the File Version is reported as: 3.99.2.5 and the Product Release is reported as: 3.99 release 5

Kind of odd... I'm sure there must be an explanation.

[Spoon]

Re: Old lame commands not working for v3.99.5 in CLI Encoder

3.99r is the maxium length of the version identifier, it is either 3.99a for alpha, or b for beta, or r for release.