Quoting Jiri Svoboda: > You do not need to figure it yourself. Mplayer will do that for You. > Just report only hw supported colorspaces. In most cases > you mplayer will choose YV12.
Cool. > > > > But the current implementation doesn't allow multiple applications > > > > to share the same exclusive context, while multiple > > exclusive contexts > > > > are allowed. Entering exclusive cooperative level creates > > a private layer > > > > context (config etc.) and switches to it. > > > > > > Actually, I get confused by the concept of cooperative > > levels and contexts. > > > > Layer contexts are part of the core. They are used to > > implement cooperative > > levels. Each context has its own display layer configuration, > > surface etc. > > Only one context is active per layer. Switching between these > > contexts changes > > the complete configuration, layer surface etc. > > I think there is no need to deal with contexts (concurent acces to > same layer). It is much more easier to and new mplayer slave comand > and implement moving&resing inside mplayer vo (vo_directfb) > It takes just few lines of code ~ 20 lines I guess. > This way there will be no conflict. You just send the command > and mplayer wil do the rest. I hope that it's fast enough. I dislike the usual latency between moving the window and the overlay. -- Best regards, Denis Oliver Kropp .------------------------------------------. | DirectFB - Hardware accelerated graphics | | http://www.directfb.org/ | "------------------------------------------" Convergence GmbH -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe directfb-dev" as subject.
