[MPlayer-dev-eng] [PATCH] reduce flashing on resize with VDPAU
Uoti Urpala
uoti.urpala at pp1.inet.fi
Tue Mar 24 19:06:14 CET 2009
On Tue, 2009-03-24 at 09:39 +0100, Dan Oscarsson wrote:
> On 2009-03-23 at 20:12 +0200 Uoti Urpala wrote:
>
> > Making the decision to drop the latest frame in flip_page is
> > undesirable, whatever logic that decision is based on. Ideally we
> > _never_ want to decide "this latest frame will be dropped". Rather we
> > want to drop an _earlier_ frame if it still hasn't been shown by the
> > time the next frame after it should be displayed. The possibility of
> > doing that should be investigated first.
>
> Sometimes the latest and sometimes an earlier is best. I am not sure
> this can be decided best in flip_page. better would be at a higher
> level.
I'm not sure whether your "Sometimes the latest" is meant to disagree
with what I said or not. In case it's not clear I meant that we don't
want to make such a decision at the time that latest frame should be
shown (of course that same frame can then get dropped later, or nothing
would ever be dropped).
> Vdpau is missing a cancel queued surface, so it is not easy to remove an
> already queued surface from the presentation queue - if we wanted to
> drop an earlier frame.
This also sounds like a problem for UI functionality. If we use the same
window for UI elements, does queuing multiple frames in the presentation
queue mean we've committed to a significant period of time with zero UI
responsiveness?
More information about the MPlayer-dev-eng
mailing list