Help - Search - Members - Calendar
Full Version: LAME DOS Box
Hydrogenaudio Forums > Lossy Audio Compression > MP3 > MP3 - Tech
mhudson7
Anyone know where I can find a guide to interpreting info in the Lame dos box? Some is self explanatory, but some isn't.
xmixahlx
try: lame --longhelp


later
sh1leshk4
I think he's referring to the info when you're encoding.
Like LR, MS, short, long, or the % and * signs...
Brainbug
guess itīs about joint stereo-settings. check out this thread (last posting by robert):
link
Never_Again
Let's go through a complete LAME screen line by line, using the recommended version and settings

CODE
LAME 3.97 (beta 2, Nov 29 2005) 32bits (http://www.mp3dev.org/)
CPU features: MMX (ASM used), SSE (ASM used), SSE2
Self-explanatory.

CODE
Using polyphase lowpass filter, transition band: 18671 Hz - 19205 Hz
Lowpass range; the audio data that is above this range will not be encoded, thus saving bits for lower frequencies.

CODE
Encoding as 44.1 kHz VBR(q=2) j-stereo MPEG-1 Layer III (ca. 7.3x) qval=3
The q after the VBR is the --Vx value you specify on the command line (or imply with a preset). Consult this table for relation between --V values and presets.
ca. 7.3x referes to the compression ratio relative to the source WAV, in this case, the MP3 is guesstimated to be 7.3X smaller than the WAV. The prediction is accurate with CBR; with VBR, the actual ratio will naturally vary from track to track.
qval is the -q value you pass on the command line (or imply with a preset).

CODE
   Frame          |  CPU time/estim | REAL time/estim | play/CPU |    ETA
 5400/7132   (76%)|    0:16/    0:21|    0:16/    0:21|   8.7312x|    0:05
The numbers are as follows, on separate lines according to the | separators:
-current frame #/total frame count (%of total frames complete thus far)
-elapsed CPU cycles spent encoding, converted to real time/estimate of the total thereof
-elapsed real time spent encoding/estimate of the total thereof
-encoding speed to the track length ratio - in this case, the time the spent encoding the track is 8.7312X shorter than the time it would take to play back the track in a CD player
-an estimate of how much longer the encoding will take

CODE
32 [  15] *
40 [   0]
48 [   1] *
56 [   0]
64 [   0]
80 [   0]
96 [   8] *
112 [  86] ***
128 [ 285] **********
160 [1262] %%***************************************
192 [2131] %%%%%%%%%%%%%%%%%%%*************************************************
224 [1125] %%%%%%%%%%%%%%%%%%%*****************
256 [ 391] %%%%%%%%*****
320 [  96] %%%*
These numbers and symbols are a detailed breakdown of the frames encoded thus far. The first number is the frame size, the number in brackets is the total count of the frames of that size; the % and * symbols refer to stereo modes used: % is Left-Right, * is Mid-Side.
Thus, we can see that at this point 1262 frames have been encoded at 160 kbps. Of these, most are mid-side joint stereo.

CODE
---------------------------------------------------------00:45-----------------
The progress bar. The time value travelling along it is the remaining time of the track if it were played realtime - not to be confused with the ETA earlier on.

CODE
  kbps        LR    MS  %     long switch short %
 192.8       28.2  71.8        91.7   4.4   3.9
-average bitrate
-percentage of the frames encoded in left-right stereo mode
-percentage of the frames encoded in mid-side stereo mode
-block types and pecentage thereof used: long, mixed and short.

CODE
Writing LAME Tag...done
ReplayGain: -4.9dB
-------------------------------------------------------------------------------

Press any key to continue . . .

Self-explanatory
mhudson7
Thanks Never Again!! I was thinking I had stumped the band. Someone(s) spent a lot of development time on this, and its great to be able to understand it!

Now if I could figure out the foobar autoscroller...
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2008 Invision Power Services, Inc.