>
> Hi all!
>
> > I just updated the Makefiles and tested LAME's new decoding capabilities
> > with some toolame-02h generated MP2s.
> >
> > I did not find the time to do the same with mp[1g] files yet, maybe later.
>
> OK, I found the time, but with LayerI there seems to be a problem:
>
>
> robert@bob:~/MP3/lame-cvs/lame-2000-08-17 > lame --decode t.mpg x.wav
> input: t.mpg 44.1kHz MPEG1 2 channel LayerIII
> output: x.wav (wav format)
> skipping initial 1105 samples (encoder + decoder delay)
> Oops: mpg123 returned more than one frame! Cant handle this...
> Frame# 1/193 149 kbps Oops: mpg123 returned more than one frame! Cant
>handle this...
> Frame# 2Oops: mpg123 returned more than one frame! Cant handle this...
> 3Oops: mpg123 returned more than one frame! Cant handle this...
> 4Oops: mpg123 returned more than one frame! Cant handle this...
> 5Oops: mpg123 returned more than one frame! Cant handle this...
> 6Oops: mpg123 returned more than one frame! Cant handle this...
> 7Oops: mpg123 returned more than one frame! Cant handle this...
> 8Oops: mpg123 returned more than one frame! Cant handle this...
> 9Oops: mpg123 returned more than one frame! Cant handle this...
> Frame# 10/193 148Oops: mpg123 returned more than one frame! Cant handle
>this...
> Frame# 11/193 149Oops: mpg123 returned more than one frame! Cant handle
>this...
> Frame# 12Oops: mpg123 returned more than one frame! Cant handle this...
>
>
The mpglib/mpg123 routine is supposed to return only 1 frame
of data. 1 frame = 1152 samples MPEG1 layer 3, 576 samples MPEG2 layer3,
and (not-very-good) the check looks like this:
if ((outsize!=576) && (outsize!=1152)) {
fprintf(stderr,"Oops: mpg123 returned more than one frame! Cant handle this...
\n");
}
For layer I, what is the frame size? I think 1024, which is why
is triggers this message?
Mark
--
MP3 ENCODER mailing list ( http://geek.rcc.se/mp3encoder/ )
