> > hello, > when encoding really large files (cd-quality, wav, >500 megs) with lame > (via the mlame script, with encoder "nice -n 19" and > options="--alt-preset standard -ms" the following happens: > > everything starts fine: > LAME version 3.91 (http://www.mp3dev.org/) > Using polyphase lowpass filter, transition band: 18671 Hz - 19205 Hz > Encoding test.wav to test.mp3 > Encoding as 44.1 kHz VBR(q=2) stereo MPEG-1 Layer III (ca. 7.3x) qval=2 > Frame | CPU time/estim | REAL time/estim | play/CPU | ETA > 9400/134282 ( 7%)| 3:52/ 55:26| 4:38/ 1:06:23| 1.0546x| 1:01:44 > 128 [ 84] %% > [..] > > but after some time > the cpu time / estim dissapears: > Frame | CPU time/estim | REAL time/estim | play/CPU | ETA > 134280/134282(100%)|1193046 h/ 0:00| 1:07:06/ 1:07:06| 0.0000x| 0:00 > here the job is already finished, but 2 frames seem to be missing too (which > did not appear to be a problem at the end of the file btw). > > my system: > suse 7.1 with kernel 2.2.18-suse (which is 2.2.18 with some patches applied by > suse such as reiserfs afaik) > gcc 2.95.2 > > maybe someone can test, if the same problem appears on other systems because > it is a bug in lame, or if just my system is broken. > > thanks > wernfried >
The frame counter display is just an estimate based on the input filesize - it has no effect on the encoding. the fact that it was within 2 out of 134k frames is pretty good :-) Mark _______________________________________________ mp3encoder mailing list [EMAIL PROTECTED] http://minnie.tuhs.org/mailman/listinfo/mp3encoder
