Help - Search - Members - Calendar
Full Version: What means play/CPU showed in LAME log?
Hydrogenaudio Forums > Lossy Audio Compression > MP3 > MP3 - General
Addam
Hello.
Please, Can somebody tell me what means play/CPU in LAME log after encoding wav 2 mp3? And why it is not showed after decoding mp3 2 wav? Is there any way how to display it after decoding. I have tried to found it by google but unsuccessfully. Thank you for information (and sorry for my English)
Maggi
Hi Addam,

to my knowledge, it's the ratio about how fast the encoding is happening compared to real time playback, so eg. a 4 minutes long song gets encoded in 1 minute, resulting in 4x play/CPU ratio

it can be displayed during encoding when the --verbose flag is given to lame.exe


Just in case, I'm doing an Ace Ventura here, anybody with in-depth knowledge feel free to correct me.

Cheers,
Maggi

PS: here's an example of the --verbose output

CODE
==> Priority set to Low.
LAME 3.97 32bits (http://www.mp3dev.org/)
CPU features: MMX (ASM used), 3DNow! (ASM used), SSE (ASM used), SSE2
polyphase lowpass filter disabled
Encoding D:\Chiko-Trailer.wav
      to D:\Chiko-Trailer.wav.mp3
Encoding as 48 kHz VBR(q=0) j-stereo MPEG-1 Layer III (ca. 5.7x) qval=0

misc:

        scaling: 1
        ch0 (left) scaling: 0
        ch1 (right) scaling: 0
        filter type: 0
        quantization: xr^3/4
        huffman search: best (outside loop)
        experimental Y=0
        ...

stream format:

        MPEG-1 Layer 3
        2 channel - joint stereo
        padding: all
        variable bitrate - VBR rh (default)
        using LAME Tag
        ...

psychoacoustic:

        using psychoacoustic model: 1
        psychoacoustic model: NSPsytune
        tonality estimation limit: 8871.700195 Hz (not relevant)
        using short blocks: channel coupled
        subblock gain: 1
        adjust masking: -4.2 dB
        adjust masking short: -6.3 dB
        quantization comparison: 9
         ^ comparison short blocks: 9
        noise shaping: 1
         ^ amplification: 2
         ^ stopping: 1
        ATH: using
         ^ type: 4
         ^ shape: 1 (only for type 4)
         ^ level adjustement: -0.48
         ^ adjust type: 3
         ^ adjust sensitivity power: 1.000000
         ^ adapt threshold type: 2
        experimental psy tunings by Naoki Shibata
           adjust masking bass=0 dB, alto=0 dB, treble=0 dB, sfb21=5.25 dB
        using temporal masking effect: yes
        interchannel masking ratio: 0
        ...

    Frame          |  CPU time/estim | REAL time/estim | play/CPU |    ETA
  4000/4046   (99%)|    0:11/    0:11|    0:11/    0:11|   8.6168x|    0:00
32 [   0]
40 [   1] *
48 [   0]
56 [   5] *
64 [  10] *
80 [  19] *
96 [  50] **
112 [ 427] *************
128 [ 741] **********************
160 [2331] ********************************************************************
192 [ 397] ************
224 [  19] *
256 [   0]
320 [   0]
-------------------------------------------------------------------------------
   kbps        MS  %     long switch short %
  150.8      100.0        96.9   1.8   1.4
pdq
That is my understanding of it as well. I also remember it being pointed out that under some operating systems the CPU time value is inaccurate (I think it may have been elapsed rather than CPU time), but I don't remember which ones.
Addam
Thanks for explanation. And it is possible to add this into log after decoding mp3 to wav?
Maggi
QUOTE(pdq @ Mar 31 2008, 18:21) *

... I also remember it being pointed out that under some operating systems the CPU time value is inaccurate (I think it may have been elapsed rather than CPU time), but I don't remember which ones.

I see that behavior on WinXP for sure, but I seem to recall it was also present on Win2k.

As it is now, CPU time/estim always equals REAL time/estim, which cannot be right, because depending on the workload your system is handling, the CPU time/estim should always be less than REAL time/estim. The taskmanager's column "CPU Time" shows the proper CPU usage time of lame.exe though.


QUOTE(Addam @ Mar 31 2008, 18:39) *

Thanks for explanation. And it is possible to add this into log after decoding mp3 to wav?

Do you really mean a playback speed ratio when rendering MP3 to WAV or rather vice versa and adding the verbose output I posted above into a log file ?

Cheers,
Maggi
Addam
It can be verbose output (if it is necessarily) whitch you posted but it needn't . But I only need to add this parameter (play/CPU) into log after decoding and i don't know how because iam not skilled programmer and I don't know how to modify source code (i thing that this part is in timestatus.c). Thank you for tip with task manager.
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.