On Mon, 2010-08-09 at 22:22 +0200, Dirk Meyer wrote:
> What features does it have? Is normal playback, seek, etc. working? I
> have no problems using the WIP stuff.
It's been a long time since I worked on it, as you know, but yes I think
all the basic plumbing is in place and working.
> P.S.: I'm not sure, but I guess there is a bug in kaa.config somewhere.
> For some reason a variable with True as default is detected as bool
> while a variable with False as default is not. I have to investigate it
> further, not today
If I get a chance tonight I'll take a look.
BTW I'd like to rename kaa.config.Var and kaa.config.VarProxy to Scalar
and ScalarProxy.
Var is ambiguous because lists and groups are still config vars. Scalar
is much clearer and the term is used in the docstrings too.
Also ...
On Mon, 2010-08-09 at 22:01 +0200, Dirk Meyer wrote:
> a. Remove everything that is not needed by the mplayer plugin. I do
> not see any reason to support Xine in the future and the gst
> backend needs a rewrite anyway. As for output: only xv and
> clutter will be supported in the future. The kaa.display support
> code will be removed. Objections now or be silient in the future.
I just read this more carefully. We need kaa.display support for
clutter support in the case of vdpau. The flow looks something like:
1. Create a window somewhere off the visible screen (but still
mapped).
2. Start MPlayer passing it the window id of our managed window.
3. Resize the window to the proper display resolution if needed.
4. Redirect the window into clutter using texture-from-pixmap
This approach is the only way I can see to make vdpau work while still
using clutter, but it has a couple problems:
1. When using frame-doubling deinterlacing, it only looks like half
the frames get redirected. I'm pretty sure gst-clutter (which
also uses tfp for this purposes) has this problem too.
2. I haven't been able to sort out how to buffer redirected
textures so I can display them using my own timing. When using
-vo shm, frames are buffered and delivered at the proper retrace
so things are quite smooth.
But the above two things aren't show stoppers and we should ignore them
for now, fixing later as part of polish.
Anyway, WIP popcorn doesn't do this yet, so there's no kaa.display
support to remove. It also doesn't do vdpau but that should be
relatively straightforward to add.
------------------------------------------------------------------------------
This SF.net email is sponsored by
Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev
_______________________________________________
Freevo-devel mailing list
Freevo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freevo-devel
