[MPlayer-users] Re: xvid and mencoder - corrupt headers?
Tobias Diedrich
ranma at tdiedrich.de
Sun Jun 6 14:49:43 CEST 2004
ivanova wrote:
> > 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?
The patch only affects how mplayer behaves when _reading_ a file.
Changing ODML_CHUNKLEN affects _writing_ a file.
The problem the patch fixes is as follows:
If you are writing a file and it gets bigger then 1GB mencoder will
produce an ODML avi by default (unless you use the -noodml switch).
In an ODML conformant avi the first GB ist more or less self-contained
in that it has an old-style avi index for this first GB.
Because the buggy reading code ignores the ODML extension for file <=2GB
seeking is broken for mencoder-created ODML files between 1GB and 2GB in
size.
Now the attached patch looks whether or not it needs to use the ODML
extensions and only uses them if it needs to (for _reading_ of avi
files).
> Is this patch included in the latest CVS version? - I'll try it out.
Yes it is.
--
Tobias PGP: http://9ac7e0bc.2ya.com
This mail is made of 100% recycled bits.
More information about the MPlayer-users
mailing list