[MPlayer-dev-eng] Re: [PATCH] VFCTRL_PERIODIC_UPDATE

Uoti Urpala uoti.urpala at pp1.inet.fi
Tue Jan 23 20:09:44 CET 2007


On Tue, 2007-01-23 at 10:24 -0500, Jason Tackaberry wrote:
> On Tue, 2007-01-23 at 17:13 +0200, Uoti Urpala wrote:
> > A better system for this would be good for MPlayer's own use too.
> > MPlayer's own OSD also fails with low FPS (adjusting speed of normal
> > video is enough to cause that).
> 
> This is what I've been trying to avoid.  I don't want to rearchitect
> core parts of mplayer to get this functionality.  It seems like this is

I didn't talk about any rearchitecting as part of the overlay
implementation there. Similar functionality could be used by MPlayer OSD
but that doesn't really affect the overlay implementation.

> what's required, since nobody is willing to accept compromises -- even
> when they don't impact the non-overlay case.

My suggestion for a relatively simple implementation that doesn't touch
core functionality is to implement it in vo_xv and/or some other vo.
Call the blend function in flip_page() (the delay probably isn't too bad
for this) and make a copy of changed areas so that another function can
update the same buffer to new overlay content later.

You've insisted on a vo-independent implementation, but given that
you're so willing to "accept compromises" in the implementation
otherwise as you said I don't buy it that the one thing you couldn't
possibly compromise on would be having it work with every vo, however
rarely used or exotic.




More information about the MPlayer-dev-eng mailing list