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
This commit is contained in:
Niklas Haas 2023-08-07 10:42:08 +02:00
parent f6de44dd6a
commit 35a6b26b78
1 changed files with 1 additions and 1 deletions

View File

@ -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;