I know, alpha versions can't be recommended, but due to the very promising experiences with 3.100a2 so far I couldn't resist porting 3995f to this 3100g variant of 3.100 alpha2.
Have the LAME authors ever explained why they don't just include your functional extensions in the main binaries?
And one more thing. I'd be happier if I could use commands like -VBR224, rather than to use a magic number like -V2+, even when I sometimes get 220kbps, 232kbps, or 199kbps.
...Perhaps a better way to do this would be to key -V0+ through -V5+ to each standard frame size. EG -V0+ is keyed to ~320kbps, -V1+ to ~256kbps, -V2+ to ~224kbps, etc.
On another note, halb27, I wanted to notify you of some strange behavior. If I pass the option --lowpass -1 -V0+, encoding fails. But -V0+ --lowpass -1 works as expected.
I tried to reproduce the error, but did not succeed. My 3100g and 3995f --lowpass -1 -V0+ encodings from the cmdline were fine. Can you give me more details, please?
I've read the -X documentation: that's nothing for me. As it's not in the --longhelp: is it really working?
a) -X is the "Change Quality Measure" switch. It controls how LAME searches for, and decides upon, the best quantization. You'll find it in LAME's commandline documentation.
d) I assume that adding a highpass would very slightly decrease frame complexity, so could result in a further very slight improvement in the resulting encoding. But that of course would need to be tested.
Quote from: BFG on 15 December, 2012, 05:13:27 PM...Perhaps a better way to do this would be to key -V0+ through -V5+ to each standard frame size. EG -V0+ is keyed to ~320kbps, -V1+ to ~256kbps, -V2+ to ~224kbps, etc.That's exactly what I did with 3100g.
Quote from: BFG on 16 December, 2012, 06:26:24 AMa) -X is the "Change Quality Measure" switch. It controls how LAME searches for, and decides upon, the best quantization. You'll find it in LAME's commandline documentation.That page shouldn't be there any longer. It is from the older documentation.Current documented switches are here
Is it possible to select the bitrate instead of the -Vx+? ...
... It would be great if your extension will support the rates between ~130 kbps and ~160 kbps (VBR). ...
... It's very likely that 15.8-16 kHz is the most appropriate for MP3 encoders at 130-135 kbps. ...
Quote from: Kamedo2 on 16 December, 2012, 08:28:11 AMIs it possible to select the bitrate instead of the -Vx+? ...I don't like this idea (see post #6), but it's easy to put to work.Would an extension of the -V option, say -V xxx, xxx between 176 and 300, help you? -V xxx would mean that -Vn+ is used with n such that average bitrate for my test set of various pop music is xxx kbps.Any suggestion for another switch instead of extending the meaning of -V x?