Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: Lame command line options precedence (Read 2962 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Lame command line options precedence

What does Lame do when it gets (potentially) conflicting command line options? For example, if I say --alt-preset fast standard, but then add -b 96 -mm, are the latter two options ignored? The reason this happens is because I use the Lamer frontend, because it is the only one which runs on my notebook (EAC does not), and allows direct mp3 encoding from line-in.

Lame command line options precedence

Reply #1 –
Quote
Originally posted by kumar
For example, if I say --alt-preset fast standard, but then add -b 96 -mm, are the latter two options ignored?
No, the settings are not ignored. In this case the lowbitrate limit will be 96kbps and it will be mono encoding.

Some switches do not work with --alt-presets though, which wouldn't otherwise be ignored.
Juha Laaksonheimo

Lame command line options precedence

Reply #2 –
Quote
Originally posted by kumar
For example, if I say --alt-preset fast standard, but then add -b 96 -mm, are the latter two options ignored?


As JohnV said, they're not ignored, but make sure you put them in that order.  "--alt-preset standard -b 96 -mm" would encode using the standard alt-preset but with a minimum bitrate of 96 kbps and mono encoding, but if you did "-b 96 -mm --alt-preset standard" the -b 128 of --alt-preset would override your -b 96 (not sure about the -mm) and so it would be ignored.