summaryrefslogtreecommitdiffstats
path: root/player/video.c
diff options
context:
space:
mode:
authorDudemanguy <random342@airmail.cc>2024-01-20 13:24:27 -0600
committerDudemanguy <random342@airmail.cc>2024-01-27 05:12:12 +0000
commitc243946338dcdcdbed9cfdc9d662d5612649932d (patch)
tree142feb8517881592e2422812af736eb1cee24da2 /player/video.c
parentded181f642bc8915e3569d718d404e915cb62c27 (diff)
downloadmpv-c243946338dcdcdbed9cfdc9d662d5612649932d.tar.bz2
mpv-c243946338dcdcdbed9cfdc9d662d5612649932d.tar.xz
vo_dmabuf_wayland: scale smarter in hidpi situations
Previously, all scaling was forced to 1 with this vo and all coordinates were calculated as if the scale was 1. This works since viewport relies on the compositor completely for scaling so it doesn't really matter if we don't draw directly to the correct size since the compositor will just scale the rest for us. This does have some downsides however since the OSD text might not be drawn at the actual resolution of the final size of the video. We can instead handle this by getting rid of the dmabuf_wayland specific scaling logic and using the same values as everything else. In the resize in vo_dmabuf_wayland, we just need to adjust the viewport destination calls so they go to the wayland local coordinates and not the physical ones. This should ensure that vo_dmabuf_wayland directly goes to the desired size and the compositor doesn't need to operate on it after the fact.
Diffstat (limited to 'player/video.c')
0 files changed, 0 insertions, 0 deletions