large mp3 encode time question |
![]() ![]() |
large mp3 encode time question |
Nov 27 2005, 22:36
Post
#1
|
|
|
Group: Members Posts: 7 Joined: 28-March 04 Member No.: 13073 |
got a 13 hour audiobook in wav 16-bit 22.05kHz mono format
converted it to 40Mbs CBR mp3 in adobe audition in 5 minutes tried lame 397b2 with "-b 40 -m m -h" and it estimated over 5 hours even using the "-f" fast switch instead of "-h" estimated over 1 hour what's the deal with that? This post has been edited by DCameronMauch: Nov 27 2005, 22:41 |
|
|
|
Nov 28 2005, 00:09
Post
#2
|
|
|
dBpowerAMP developer Group: Developer (Donating) Posts: 2653 Joined: 24-March 02 Member No.: 1615 |
13 hour = 60x13 = 780 minutes
/ 5 minutes = x156 real time encoding. Lame would be around x15 encoding, which is normal (depending upon computer), different encoders. BTW there is a Real Mp3 encoder that is much faster than Lame. -------------------- Spoon http://www.dbpoweramp.com
|
|
|
|
Nov 28 2005, 00:21
Post
#3
|
|
![]() Group: Members Posts: 1303 Joined: 14-September 05 From: Helsinki, Finland Member No.: 24472 |
It can be adjusted:
CODE Z:\Convert\Wave>lame 16-22mono15min.wav -b 40 -m m -h LAME 3.97 (beta 1, Sep 29 2005) 32bits (http://www.mp3dev.org/) CPU features: MMX (ASM used), SSE (ASM used), SSE2 Using polyphase lowpass filter, transition band: 10403 Hz - 10669 Hz Encoding 16-22mono15min.wav to 16-22mono15min.wav.mp3 Encoding as 22.05 kHz 40 kbps single-ch MPEG-2 Layer III (8.8x) qval=2 Frame | CPU time/estim | REAL time/estim | play/CPU | ETA 34457/34457 (100%)| 1:01/ 1:01| 1:01/ 1:01| 14.756x| 0:00 ------------------------------------------------------------------------------- kbps mono % long switch short % 40.0 100.0 66.3 16.7 17.1 ReplayGain: -14.9dB CODE Z:\Convert\Wave>lame 16-22mono15min.wav -b 40 -m m -f LAME 3.97 (beta 1, Sep 29 2005) 32bits (http://www.mp3dev.org/) CPU features: MMX (ASM used), SSE (ASM used), SSE2 Using polyphase lowpass filter, transition band: 10403 Hz - 10669 Hz Encoding 16-22mono15min.wav to 16-22mono15min.wav.mp3 Encoding as 22.05 kHz 40 kbps single-ch MPEG-2 Layer III (8.8x) qval=7 Frame | CPU time/estim | REAL time/estim | play/CPU | ETA 34457/34457 (100%)| 0:42/ 0:42| 0:42/ 0:42| 21.101x| 0:00 ------------------------------------------------------------------------------- kbps mono % long switch short % 40.0 100.0 66.3 16.7 17.1 ReplayGain: -14.9dB CODE Z:\Convert\Wave>lame 16-22mono15min.wav -b 40 -m m -f --noreplaygain LAME 3.97 (beta 1, Sep 29 2005) 32bits (http://www.mp3dev.org/) CPU features: MMX (ASM used), SSE (ASM used), SSE2 Using polyphase lowpass filter, transition band: 10403 Hz - 10669 Hz Encoding 16-22mono15min.wav to 16-22mono15min.wav.mp3 Encoding as 22.05 kHz 40 kbps single-ch MPEG-2 Layer III (8.8x) qval=7 Frame | CPU time/estim | REAL time/estim | play/CPU | ETA 34457/34457 (100%)| 0:06/ 0:06| 0:06/ 0:06| 129.75x| 0:00 ------------------------------------------------------------------------------- kbps mono % long switch short % 40.0 100.0 66.3 16.7 17.1 With "-b 40 -m m -f --noreplaygain" my 15 min 16/22.05 test file was encoded in 6 seconds. 13 x 4 x 6 s = 312 s = 5 min 12 s (XP/P4/2.8 Ghz, P4 hyperthreading enabled) -------------------- http://listening-tests.freetzi.com
|
|
|
|
Nov 28 2005, 00:49
Post
#4
|
|
![]() Group: Members Posts: 1303 Joined: 14-September 05 From: Helsinki, Finland Member No.: 24472 |
A small correction:
LAME doesn't show time values below 1 s. It truncates the decimal digits. My test file was exactly 15 min 0.00 s. The speed was 129.75x. The encoding time was: 15 x 60 / 129.75 = 6.94 s 13 x 4 x 6.94 s = 360.88 s = 6 min 0.88 s This post has been edited by Alex B: Nov 28 2005, 00:52 -------------------- http://listening-tests.freetzi.com
|
|
|
|
Nov 28 2005, 02:30
Post
#5
|
|
|
Group: Members Posts: 7 Joined: 28-March 04 Member No.: 13073 |
I must have something seriously wrong going on.
Based on your calculations, my 13 hour file should encode in just about 6 minutes. But I still have an estimated encode time of 1 hour 30 minutes.. My systems is an XP/AMD64/4000+. Seems like something is seriously wrong. Hum. Let is run for a long time and it failed with some unknown error. Twice. Looks like the problem may be with razorlame. When I run lame from the command prompt, it seems to be giving me the encode time I expected. Guess it's time for another front end gui... |
|
|
|
Nov 28 2005, 03:35
Post
#6
|
|
|
Group: Members Posts: 7 Joined: 28-March 04 Member No.: 13073 |
One more question while I am at it though:
The -q quality setting, think I am going to get any difference I could notice between -h and -q0? I would like to think I would be getting something for 3x the encoding time. |
|
|
|
Nov 28 2005, 12:52
Post
#7
|
|
![]() Group: Members Posts: 1303 Joined: 14-September 05 From: Helsinki, Finland Member No.: 24472 |
QUOTE (DCameronMauch @ Nov 28 2005, 04:35 AM) The -q quality setting, think I am going to get any difference I could notice between -h and -q0? I would like to think I would be getting something for 3x the encoding time. I don't have experience of encoding audio books. I suppose -h would be slightly better than -f (in case -f has audible problems). I have no idea what -q 0 might do. With usual music files and VBR settings like -V 5 and better I can't hear a difference in casual listening when -q 0 is added. At least -q 0 is not one of the commonly recommended options. The speed drop from 130x to 21x when --noreplaygain is not used looks like a bug to me. -------------------- http://listening-tests.freetzi.com
|
|
|
|
Nov 29 2005, 04:49
Post
#8
|
|
|
Group: Members (Donating) Posts: 698 Joined: 31-March 04 From: NYC Member No.: 13152 |
QUOTE (DCameronMauch @ Nov 27 2005, 09:30 PM) RazorLAME is obsolete and has been superceded by AdvaLAME.
|
|
|
|
Nov 29 2005, 05:57
Post
#9
|
|
![]() Group: Members (Donating) Posts: 1350 Joined: 4-March 02 From: Indianapolis, IN Member No.: 1440 |
QUOTE (DCameronMauch @ Nov 27 2005, 04:36 PM) got a 13 hour audiobook in wav 16-bit 22.05kHz mono format converted it to 40Mbs CBR mp3 in adobe audition in 5 minutes tried lame 397b2 with "-b 40 -m m -h" and it estimated over 5 hours even using the "-f" fast switch instead of "-h" estimated over 1 hour what's the deal with that? 5 hours? So...what's the problem? Click the encode button, and go to bed. When you wake up, it's done. This post has been edited by indybrett: Nov 29 2005, 05:59 -------------------- Wait Master, it might be dangerous... you go first.
|
|
|
|
Nov 29 2005, 17:02
Post
#10
|
|
![]() Group: Members Posts: 1303 Joined: 14-September 05 From: Helsinki, Finland Member No.: 24472 |
QUOTE (indybrett @ Nov 29 2005, 06:57 AM) 5 hours? So...what's the problem? Click the encode button, and go to bed. When you wake up, it's done. It's not a problem if the time is normal. In this case the developers should look into this. I don't consider this speed drop without the "--noreplaygain" switch normal. (129.75x > 21.1x) If it's normal an explanation would be nice. Perhaps the switch should be added to the HA recommendations for low bitrate & samplerate mono files. Even better would be if LAME could disable the replaygain check automatically when the used switch combination is going to result slowdowns like this. QUOTE (Alex B @ Nov 28 2005, 01:21 AM) CODE Z:\Convert\Wave>lame 16-22mono15min.wav -b 40 -m m -f LAME 3.97 (beta 1, Sep 29 2005) 32bits (http://www.mp3dev.org/) CPU features: MMX (ASM used), SSE (ASM used), SSE2 Using polyphase lowpass filter, transition band: 10403 Hz - 10669 Hz Encoding 16-22mono15min.wav to 16-22mono15min.wav.mp3 Encoding as 22.05 kHz 40 kbps single-ch MPEG-2 Layer III (8.8x) qval=7 Frame | CPU time/estim | REAL time/estim | play/CPU | ETA 34457/34457 (100%)| 0:42/ 0:42| 0:42/ 0:42| 21.101x| 0:00 ------------------------------------------------------------------------------- kbps mono % long switch short % 40.0 100.0 66.3 16.7 17.1 ReplayGain: -14.9dB CODE Z:\Convert\Wave>lame 16-22mono15min.wav -b 40 -m m -f --noreplaygain LAME 3.97 (beta 1, Sep 29 2005) 32bits (http://www.mp3dev.org/) CPU features: MMX (ASM used), SSE (ASM used), SSE2 Using polyphase lowpass filter, transition band: 10403 Hz - 10669 Hz Encoding 16-22mono15min.wav to 16-22mono15min.wav.mp3 Encoding as 22.05 kHz 40 kbps single-ch MPEG-2 Layer III (8.8x) qval=7 Frame | CPU time/estim | REAL time/estim | play/CPU | ETA 34457/34457 (100%)| 0:06/ 0:06| 0:06/ 0:06| 129.75x| 0:00 ------------------------------------------------------------------------------- kbps mono % long switch short % 40.0 100.0 66.3 16.7 17.1 -------------------- http://listening-tests.freetzi.com
|
|
|
|
Nov 29 2005, 17:11
Post
#11
|
|
![]() Group: Members Posts: 526 Joined: 15-January 02 From: Warwickshire -- England Member No.: 1036 |
I believe beta 2 has a change related to that option. Worth checking out.
Kristian This post has been edited by kritip: Nov 29 2005, 17:11 |
|
|
|
Nov 30 2005, 09:18
Post
#12
|
|
|
Group: Banned Posts: 31 Joined: 30-November 05 Member No.: 26109 |
QUOTE (Never_Again @ Nov 29 2005, 05:49 AM) QUOTE (DCameronMauch @ Nov 27 2005, 09:30 PM) RazorLAME is obsolete and has been superceded by AdvaLAME.But this are all programs, that have small amount of options. For best tunning for encoding, u should use EncoderPro (http://www.scron.prv.pl/) , tool that is designed for HQ audio coding. This post has been edited by CRYON: Nov 30 2005, 09:18 |
|
|
|
Nov 30 2005, 19:01
Post
#13
|
|
|
Group: Members Posts: 346 Joined: 21-August 02 Member No.: 3138 |
QUOTE (CRYON @ Nov 30 2005, 12:18 AM) But this are all programs, that have small amount of options. For best tunning for encoding, u should use EncoderPro (http://www.scron.prv.pl/) , tool that is designed for HQ audio coding. Hmm.... Anyone speak Polish? Can't really tell just what this is. -------------------- [url=http://www.domain.com]Click here![/url]
|
|
|
|
Nov 30 2005, 19:37
Post
#14
|
|
![]() Group: Members Posts: 1075 Joined: 15-October 03 From: Memphis, TN Member No.: 9323 |
QUOTE (Alex B @ Nov 29 2005, 11:02 AM) It's not a problem if the time is normal. In this case the developers should look into this. I don't consider this speed drop without the "--noreplaygain" switch normal. (129.75x > 21.1x) If it's normal an explanation would be nice. Umm... Calculating ReplayGain values will *always* be slower than not calculating them. Regardless of any other switches. I mean, it's a simple matter of doing the work vs. not doing the work. By adding the --noreplaygain switch, you're telling it to not bother running the audio data through the ReplayGain algorithims to figure out the average volume. This won't affect the quality of the encode any, but it will mean that no RG information will be added to the LAME header. This post has been edited by Otto42: Nov 30 2005, 19:38 -------------------- http://ottodestruct.com
|
|
|
|
Nov 30 2005, 19:56
Post
#15
|
|
![]() Group: Members Posts: 1303 Joined: 14-September 05 From: Helsinki, Finland Member No.: 24472 |
QUOTE (Otto42 @ Nov 30 2005, 08:37 PM) Umm... Calculating ReplayGain values will *always* be slower than not calculating them. Regardless of any other switches. I mean, it's a simple matter of doing the work vs. not doing the work. By adding the --noreplaygain switch, you're telling it to not bother running the audio data through the ReplayGain algorithims to figure out the average volume. This won't affect the quality of the encode any, but it will mean that no RG information will be added to the LAME header. Usually the LAME replay gain analysis has very small effect to the encoding time. In this case the effect was over 600%. Most likely it is because of the silent parts issue (LAME 397b2: "ReplayGain analysis should now be faster when encountering silent parts"). My artificial test file mimicked speech and included repeated silent passages. -------------------- http://listening-tests.freetzi.com
|
|
|
|
Nov 30 2005, 20:26
Post
#16
|
|
![]() Group: Members Posts: 526 Joined: 15-January 02 From: Warwickshire -- England Member No.: 1036 |
@Alex B.
Did you also run the test with b2 then? Did it improve? The screen caps you posted say beta 1. KRistian |
|
|
|
Nov 30 2005, 20:35
Post
#17
|
|
![]() Group: Members (Donating) Posts: 799 Joined: 12-September 03 Member No.: 8821 |
QUOTE (woody_woodward @ Nov 30 2005, 08:01 PM) QUOTE (CRYON @ Nov 30 2005, 12:18 AM) But this are all programs, that have small amount of options. For best tunning for encoding, u should use EncoderPro (http://www.scron.prv.pl/) , tool that is designed for HQ audio coding. Hmm.... Anyone speak Polish? Can't really tell just what this is. Translation: "Converts WAV to MP3, MP4, AAC, and M4A. Has very advenced GUI and very fast algorithm giving high quality. Uses LAME, GOGO and SimpleEnc libraries for mp3 encoding and FAAC for mp4. Worth of recommendation as it offers advenced encoding options and simple & fast interface. Can save the configuration to a file or registry." CRYON is the author, already discussed. This post has been edited by rutra80: Nov 30 2005, 20:41 |
|
|
|
Nov 30 2005, 20:41
Post
#18
|
|
![]() Group: Members Posts: 1303 Joined: 14-September 05 From: Helsinki, Finland Member No.: 24472 |
QUOTE (kritip @ Nov 30 2005, 09:26 PM) I have not downloaded b2 and tried it with anything yet. Unfortunately I deleted the 38 MB test file (I made it quickly in Wavelab just for checking this), but I'll try this with another file later. Edit: I just found the file. I didn't delete it after all. I'll test it and post the results. This post has been edited by Alex B: Nov 30 2005, 21:25 -------------------- http://listening-tests.freetzi.com
|
|
|
|
Nov 30 2005, 21:25
Post
#19
|
|
![]() Group: Members Posts: 1303 Joined: 14-September 05 From: Helsinki, Finland Member No.: 24472 |
3.97b2 -b 40 -m m -f
CODE Z:\test\noreplaygain>lame 16-22mono15min.wav -b 40 -m m -f LAME 3.97 (beta 2, Nov 29 2005) 32bits (http://www.mp3dev.org/) CPU features: MMX (ASM used), SSE (ASM used), SSE2 Using polyphase lowpass filter, transition band: 10403 Hz - 10669 Hz Encoding 16-22mono15min.wav to 16-22mono15min.wav.mp3 Encoding as 22.05 kHz 40 kbps single-ch MPEG-2 Layer III (8.8x) qval=7 Frame | CPU time/estim | REAL time/estim | play/CPU | ETA 34457/34457 (100%)| 0:08/ 0:08| 0:08/ 0:08| 105.89x| 0:00 ------------------------------------------------------------------------------- kbps mono % long switch short % 40.0 100.0 66.3 16.7 17.1 ReplayGain: -14.9dB 3.97b2 -b 40 -m m -f --noreplaygain CODE Z:\test\noreplaygain>lame 16-22mono15min.wav -b 40 -m m -f --noreplaygain LAME 3.97 (beta 2, Nov 29 2005) 32bits (http://www.mp3dev.org/) CPU features: MMX (ASM used), SSE (ASM used), SSE2 Using polyphase lowpass filter, transition band: 10403 Hz - 10669 Hz Encoding 16-22mono15min.wav to 16-22mono15min.wav.mp3 Encoding as 22.05 kHz 40 kbps single-ch MPEG-2 Layer III (8.8x) qval=7 Frame | CPU time/estim | REAL time/estim | play/CPU | ETA 34457/34457 (100%)| 0:06/ 0:06| 0:06/ 0:06| 141.19x| 0:00 ------------------------------------------------------------------------------- kbps mono % long switch short % 40.0 100.0 66.3 16.7 17.1 3.97b1 -b 40 -m m -f CODE Z:\noreplaygain>lame 16-22mono15min.wav -b 40 -m m -f LAME 3.97 (beta 1, Sep 29 2005) 32bits (http://www.mp3dev.org/) CPU features: MMX (ASM used), SSE (ASM used), SSE2 Using polyphase lowpass filter, transition band: 10403 Hz - 10669 Hz Encoding 16-22mono15min.wav to 16-22mono15min.wav.mp3 Encoding as 22.05 kHz 40 kbps single-ch MPEG-2 Layer III (8.8x) qval=7 Frame | CPU time/estim | REAL time/estim | play/CPU | ETA 34457/34457 (100%)| 0:39/ 0:39| 0:39/ 0:39| 22.529x| 0:00 ------------------------------------------------------------------------------- kbps mono % long switch short % 40.0 100.0 66.3 16.7 17.1 ReplayGain: -14.9dB 3.97b1 -b 40 -m m -f --noreplaygain CODE Z:\noreplaygain>lame 16-22mono15min.wav -b 40 -m m -f --noreplaygain LAME 3.97 (beta 1, Sep 29 2005) 32bits (http://www.mp3dev.org/) CPU features: MMX (ASM used), SSE (ASM used), SSE2 Using polyphase lowpass filter, transition band: 10403 Hz - 10669 Hz Encoding 16-22mono15min.wav to 16-22mono15min.wav.mp3 Encoding as 22.05 kHz 40 kbps single-ch MPEG-2 Layer III (8.8x) qval=7 Frame | CPU time/estim | REAL time/estim | play/CPU | ETA 34457/34457 (100%)| 0:06/ 0:06| 0:06/ 0:06| 137.50x| 0:00 ------------------------------------------------------------------------------- kbps mono % long switch short % 40.0 100.0 66.3 16.7 17.1 LAME 3.97b2 is much better. Also the "--noreplaygain" option is slightly faster (I tried this three times to make sure). The test PC has a different faster setup now. That's why I tested LAME 3.97b1 again. This post has been edited by Alex B: Nov 30 2005, 21:38 -------------------- http://listening-tests.freetzi.com
|
|
|
|
![]() ![]() |
|
Lo-Fi Version | Time is now: 20th May 2013 - 13:01 |