[MPlayer-users] Re: xvid and mencoder - corrupt headers?

ivanova flamingivanova at punkass.com
Sun Jun 6 12:16:43 CEST 2004


On Sun, 6 Jun 2004 11:03:46 +0200
Tobias Diedrich <ranma at tdiedrich.de> wrote:

> rcooley wrote:
> 
> > Yes, that is exactly what MPlayer does.  It was mentioned on -dev that
> > some AVI files can't be read if it tries to use ODML, so the default is
> > to try regular AVI unless it's too big to be regular AVI. 
> > 
> > In MPlayer-1.0pre4:
> > 
> > libmpdemux/aviheader.c: unmodified: line 228 of 713 [31%]
> > 
> >       // FIXME: do not use odml index for files that don't need it.
> >       // apparently the odml code is buggy!
> >       if (demuxer->movi_end < 0x7fffffff) break;
> > 
> > You could change 0x7fffffff to about half that, so it will read ODML for
> > 1GB+ files.  Alternatively:
> 
> No, please use the attached patch.
> The apparent corruption problem is a bit more tricky, because I could
> not reproduce it so far and most users do not seem willing to upload
> 1GB+-Files... :-)
> 
> However if you could reduce the ODML_CHUNKLEN to a small value and
> produce a small buggy file with that in upload it, that could help
> finding the bug.

I'm not sure I understand all this. The current version only writes a ODML avi if it is bigger than 2GB. This patch makes mencoder always write a ODML avi. 
Is this right? But if my 1.3 GB avi is not ODML, why do other apps report sync/header errors? Do they all expect ODML avis?

Is this patch included in the latest CVS version? - I'll try it out. 

BTW I tried searching the mailinglist archives at http://zebra.fh-weingarten.de/~maxi/cgi-bin/namazu.cgi?idxname=mplayer-users but I keep getting a server error.




More information about the MPlayer-users mailing list