diff options
| author | wm4 <wm4@nowhere> | 2017-02-28 00:54:54 +0100 |
|---|---|---|
| committer | wm4 <wm4@nowhere> | 2017-02-28 00:57:51 +0100 |
| commit | 75fc2bee1e47f93f1ad40331cbb34667c810ca9a (patch) | |
| tree | 802f5404e86c3305e229741a2ddfa7cf9beecb5a /DOCS | |
| parent | d015aab42835d20679ec4fe0d8b3a31a81f7a168 (diff) | |
| download | mpv-75fc2bee1e47f93f1ad40331cbb34667c810ca9a.tar.bz2 mpv-75fc2bee1e47f93f1ad40331cbb34667c810ca9a.tar.xz | |
vf_vavpp: add advanced deint bug compatibility for Intel vaapi drivers
I'm not sure what's going on here, but it appears kodi switches forward
and backwards references for advanced VPP deinterlacing modes. This in
turn makes deinterlacing with these modes apparently work. If you don't
switch the directions, you get a stuttering mess.
As far as the libva trace dump is concerned, this makes mpv's libva
deinterlacing API use behave like kodi's, and appears to reproduce
smooth video with advanced libva deinterlacing enabled.
I'm hearing that Mesa actually does it correctly, and I'm not sure what
will happen there. For now, passing "reversal-bug=no" as sub-option to
the vavpp filter will undo this behavior.
Diffstat (limited to 'DOCS')
| -rw-r--r-- | DOCS/man/vf.rst | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/DOCS/man/vf.rst b/DOCS/man/vf.rst index 22423513a0..c0614d968f 100644 --- a/DOCS/man/vf.rst +++ b/DOCS/man/vf.rst @@ -754,6 +754,13 @@ Available filters are: :no: Deinterlace all frames. :yes: Only deinterlace frames marked as interlaced (default). + ``reversal-bug=<yes|no>`` + :no: Use the API as it appears to be documented. Reported to work well + with Mesa drivers. + :yes: Switch surface forward and backwards references (default). Appears + to work (or work better than ``no``) with Intel drivers. Matters + only for the advanced deinterlacing algorithms. + ``vdpaupp`` VDPAU video post processing. Works with ``--vo=vdpau`` and ``--vo=opengl`` only. This filter is automatically inserted if deinterlacing is requested |