On Fri, 16 Jan 2004, James Finnall wrote:
> I updated from the CVS last night and was able to produce something that at
> least ogle could run without any error messages, even with the output set for
Great!
> full rate. But I could only mplex to about 350 MByte then it would abort with
> "buffer overflow" message. I have not been able to get past that now. But it
> appears that my dropped sound parts might be cleared up. I haven't been
> Any suggestions on this one! The messages are below.
> ++ WARN: [mplex] Stream e0: data will arrive too late sent(SCR)=157704192
> required(DTS)=157402974
> ++ WARN: [mplex] Video e0: buf= 164668 frame=052409 sector=00143782
> ++ WARN: [mplex] Audio c0: buf= 891 frame=073007 sector=00020818
ARGH - that's the rate control bug that was supposedly fixed a few
days ago :(
As a workaround could you try a larger '-b' option with mplex? That's
the video buffer size. Normally the DVD default of 220 is enough,
but I am curious if '-b 300' or perhaps a bit larger will work.
Looks like you've snagged the first bug that needs to be fixed before
a release - congratulations!
The encoder chap is busy at work/home this weekend so it will be a
couple days before the bug can be dealt with.
Cheers,
Steven Schultz
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Mjpeg-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/mjpeg-users
