Lame Command Line
Reply #37 – 2010-03-22 11:57:21
On the file posted by Steve, I would be interested to at how V0-encoded files compare to the 320 (with varying q levels). Steve, can you easily ABX this? Or /mnt? It is very easy... I clearly hear much lower background high-freq noise in V0: LAME 3.98.3 -b 320 -q 0 vs LAME 3.98.3 -V 0foo_abx 1.3.4 report foobar2000 v1.0.1 2010/03/22 13:43:05 File A: D:\Samples\Show_Me_Your_Spine__Sample_b320q0.mp3 File B: D:\Samples\Show_Me_Your_Spine__Sample_V0.mp3 13:43:05 : Test started. 13:43:27 : 01/01 50.0% 13:43:31 : 02/02 25.0% 13:43:35 : 03/03 12.5% 13:43:39 : 04/04 6.3% 13:43:44 : 05/05 3.1% 13:43:55 : 06/06 1.6% 13:44:02 : 07/07 0.8% 13:44:07 : 08/08 0.4% 13:44:12 : 09/09 0.2% 13:44:18 : 10/10 0.1% 13:44:23 : 11/11 0.0% 13:44:28 : 12/12 0.0% 13:44:32 : 13/13 0.0% 13:44:35 : 14/14 0.0% 13:44:40 : 15/15 0.0% 13:44:45 : 16/16 0.0% 13:44:46 : Test finished. ---------- Total: 16/16 (0.0%) Also, it seems like pre-echo is slightly quieter with -b 320 -q 0 (but I'm not 100% sure) I've got almost the same results for -b 320 -q 3 (default 320 CBR mode) and -b320 -q 2 . In comparing with -V 0 of course.halb27, see my previous posts. I was talking about restriction of minimal bitrate in VBR V0 mode. I'm using 3.98.3 of course... Sorry, I didn't read carefully enough. As for your real question -b 320 together with -Vx isn't meaningful (except for the case you do need a constant bitrate but want to use VBR). What seems to be a problem in understanding is that frame bitrate is mixed up conceptually with audio data bit rate - quite a common misunderstanding unfortunately. -Vx -b 320 just means having Lame use frame bitrates of 320 kbps. It doesn't tell about the audio data contents within the 320 kbps frames. I remember having tried this a couple of years ago, and after mp3repacking -V0 and -V0 -b xxx yielded more or less the same bitrate (maybe it was even exactly the same). So both -Vx and -Vx -b320 provide (more or less or even exactly) the same audio data stream provided by the VBR mechanism, but with -b 320 added it's put into 320 kbps frames, leaving a lot of space unused. thank you! Now it's all clear for me