please help: INPUT_MAX_ALLOCATION reached!!!

[Jochen Steinbicker]

Well, my last mail was kind of wrong as i found out today. My Problem was 
in the first instance processor related, but not in the further instances 
(i.e., when i tried encoding with different settings).
DIVX ENCODES WITH HIGH BITRATES WORK FINE - but one should not encode with 
q-pel enabled (one of the mpeg4 feats).
Somehow VLC's buffer (or something MacOSX) seems to need a restart after it 
crashed with "input max allocation reached" ... whatever



At 18:05 10.09.2002 +0200, you wrote:
>On Tue, Sep 10, 2002, Jochen Steinbicker wrote:
> > divx5 does eat a lot of processor, but the one that makes it crash still
> > leaves some % of processer free; and besides, it should just skip 
> frames if
> > there is too much to decode, right? but what it does is it fills up its
> > buffer until its filled and crashes ... (if it helps, i can post the
> > crash.log)
>
>  'Frames skipping' works only for mpeg1/2. The ffmpeg plugin( the one
>used here ) decodes all frames even if there isn't enougth time to do
>it( and so decodes too late pictures that won't be displayed ). It's
>only in cvs version that I've tried to add frames skip support but it's
>not really usable and with mpeg4/divx it's not easy since there is only
>a few I pictures.
>
>  A way to see if it's cpu related : could you start playing the file at
>lower speed ( by clicking on 'Slow' 1,2 or 4 times as soon as possible
>) ? If it still crashes could you upload a part of this file ?
>
>--
>fenrir
>
>
>--
>This is the vlc mailing-list, see http://www.videolan.org/vlc/
>To unsubscribe, please read http://www.videolan.org/lists.html
>If you are in trouble, please contact <postmaster at videolan.org>

-- 
This is the vlc mailing-list, see http://www.videolan.org/vlc/
To unsubscribe, please read http://www.videolan.org/lists.html
If you are in trouble, please contact <postmaster at videolan.org>