diff options
| author | Niklas Haas <git@haasn.dev> | 2023-08-07 10:42:08 +0200 |
|---|---|---|
| committer | Niklas Haas <git@haasn.dev> | 2023-08-07 10:42:08 +0200 |
| commit | 35a6b26b780af4befa4da06a63bebf95571d1279 (patch) | |
| tree | c6e23e37e291537a7f70787cf8ee2894042b22cc /video | |
| parent | f6de44dd6af89a5407d7ed77badde5885c08e59c (diff) | |
| download | mpv-35a6b26b780af4befa4da06a63bebf95571d1279.tar.bz2 mpv-35a6b26b780af4befa4da06a63bebf95571d1279.tar.xz | |
vo_gpu_next: increase non-interpolation queue size
1 is not enough to prevent PL_QUEUE_MORE, because the pl_queue is
designed to always know the next frame (in addition to the current).
Before haasn/libplacebo@112bb886, this was was (wrongly) silently
omitted by the pl_queue code, but that fix exposed this.
While it's technically API misuse on mpv side, due to the mpv vo code
having its own internal queueing and timing control, it shouldn't
actually make any difference in practice (and likely, the error message
showing up is the only meaningful bug here - the issue is entirely
cosmetic).
Fixes: https://github.com/mpv-player/mpv/issues/12101
Diffstat (limited to 'video')
| -rw-r--r-- | video/out/vo_gpu_next.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/video/out/vo_gpu_next.c b/video/out/vo_gpu_next.c index 0e7ac4afa5..bc572be1a5 100644 --- a/video/out/vo_gpu_next.c +++ b/video/out/vo_gpu_next.c @@ -1890,7 +1890,7 @@ static void update_render_options(struct vo *vo) if (p->frame_mixer) { vo_set_queue_params(vo, 0, 2 + ceilf(p->frame_mixer->kernel->radius)); } else { - vo_set_queue_params(vo, 0, 1); + vo_set_queue_params(vo, 0, 2); } p->deband = pl_deband_default_params; |