diff options
author | wm4 <wm4@nowhere> | 2020-05-11 19:56:20 +0200 |
---|---|---|
committer | wm4 <wm4@nowhere> | 2020-05-11 19:57:34 +0200 |
commit | 3451908a34437b69cd984198642b4f954cf6c4bf (patch) | |
tree | 75f67c20beb818b5c13d97915c8ae64e2e23e56a /test/scale_zimg.c | |
parent | 55e1f15cdb9d73af56715ffe030a626697c1b917 (diff) | |
download | mpv-3451908a34437b69cd984198642b4f954cf6c4bf.tar.bz2 mpv-3451908a34437b69cd984198642b4f954cf6c4bf.tar.xz |
vo_vaapi: use new overlay API
This will probably make it slower. But since I don't care about
vo_vaapi, that's perfectly OK. It serves mostly as a test for the
previous commit. In addition, this code was pretty bad (custom broken
scaling and not-blending that probably broke in some situation). If that
wasn't enough, some vaapi drivers also provide only a single overlay at
a time, while this code required a bunch.
There also seems to be a Mesa bug: the overlay gets stretched when
src_x/y was not 0. Or maybe I misunderstood how this is supposed to
work. A bug is probably more likely? Nobody cares about this API.
Diffstat (limited to 'test/scale_zimg.c')
0 files changed, 0 insertions, 0 deletions