On Wed, Feb 05, 2003 at 08:59:06PM +0100, Jon Wikne wrote:
> Hi List,
>
> OK, so I'm probably stupid.
>
> With aviplay from avifile0.7-0.7.29, the video from an .avi file
> freezes with the following error message:
>
> <ffmjpeg> : doesn't support DR1
well - when ffmpeg said - it doens't support DR1 then it simply
doesn't support it :)
Unless you would convice Alex (the author of mjpeg decoder in ffmpeg)
to finaly fix/improveve the code to be usable with DR1 there will
be no DR1 usable (either in mplayer nor in avifile - not sure
how this works in xine...)
> The sound continues, but the video sticks in one frame.
Could you send me such sample video - it might be probably buggy
You could eventually try different codec (either some of the Win32
codec or the stupid slow demo Mjpeg codec from avifile)
> "Also I've finaly enabled ffmpeg DR1 method rendering so also users
> could use it. (There were some problems which had to be resolved
> first so there will be no major problems. And as always user could
> enable/disable this at runtime)."
You runs for quite some time - and might be configured by opening
video decoder config dialog (right button in video window will
open popup config dialog where you could change various codecs parameters -
for now there isn't many options but - DR1 could be enable/disabled
from there)
> Great! So how do I enable DR1 at runtime?
It's enabled by defaults - so if you haven't disabled it's enabled :)
When ffmpeg sais it will not support DR1 there is no way to change
except fixing the ffmpeg code...
> or
> "aviplay -h --codecs_video"
> They only give the main help menu.
aviplay --codec shows the list
aviplay --codec ffodivx:help shows configurable options
(ok here was bug - just fixed in cvs)
--codec_video is for selecting codecs' order
> So what are the secrets of this program, anyway? Do I have to
> read the source to find out?
Yep there is a lot of secrets :)
That's what makes it unique :)
And I think only using the force and reading the source might
reveal them - anyway I'm trying to keep unstable parts of API
undocumented to minimalized the necessity of keeping
compatibility with some weird tricks.
So by using the standard API - you could be mostly sure it will
remain workable (at least for 0.7 branch)
By using tricks from aviplay <-> libaviplay comunications you
might expect changes anytime...
--
.''`. Zdenek Kabelac kabi@{debian.org, users.sf.net, fi.muni.cz}
: :' : Debian GNU/Linux maintainer - www.debian.{org,cz}
`. `' Overclocker's house :)
`- http://www.bbspot.com/News/2002/08/house.html
_______________________________________________
Avifile mailing list
[EMAIL PROTECTED]
http://prak.org/mailman/listinfo/avifile
