[MPlayer-dev-eng] [PATCH] Better double frame rate output and frame limit option.

[wm4]

On Sun, 06 Jan 2013 14:21:03 +0100
Dan Oscarsson <Dan.Oscarsson at tieto.com> wrote:

> I looked at this when adding my patches (will check your patches soon
> and compare to mine - my patches use pts for timing and schedules
> frame display to best vsync (works with vdpau)). As my patches do
> frame scheduling in mplayer core I would have to add to the protocol
> to call vo code to handle deinterlacing code working inside vo. So I
> did not fix it. Though, as my patches add code to vdpau that makes
> the vo drop frames when to many frames are queued for display, it
> should work quite well for hardware deinterlacing when display
> refresh rate is around double the frame rate. As vdpau displays
> frames on vsync, extra deinterlaced frames will be shown at next
> vsync and my code will drop frames if there are to many queued.  I
> could do better if I expanded the protocol taking to the vo, but I
> wanted to avoid that as it is difficult enough to get things accepted
> in mplayer.

Are you aware that mplayer2 extended support for correct vsync aware
frame timing and such for vdpau? I don't know how much has been done
compared to mplayer, but apparently it's quite a bit. Though the most
annoying thing about the mplayer2 solution is that it's quite vdpau
specific, and rather hard to allow other VOs to do something similar
(such as high FPS playback for vo_gl).

Also, mplayer2 has updated some filters to handle PTS correctly.

I haven't really been following the discussion. Are your patches
publicly available somewhere?