Niklas Haas

The entire issue seems to stem from a single frame, actually. Here is the relative PTS jumps, starting with the very first frame after hitting 'space' to unpause: ``` 8.666...

FFmpeg is in the process of gaining lock_queue/unlock_queue functions which will solve the queue threading issue (*), in addition to lock_frame/unlock_frame (which we will need to put inside map/unmap respectively)...

> > No, it doesn't. > > The issue is a request for a vulkan hwdec, this is the PR that adds it. Don't we still need extra code to...

The major difference between `gpu` and `gpu-next` is that the former generates 16-bit integer 3DLUTs while the latter generates 32-bit float 3DLUTs. This doubles the VRAM requirement from 1GB to...

Okay, some more poignant notes: 1. I submitted [this MR](https://code.videolan.org/videolan/libplacebo/-/merge_requests/258) changing the 3DLUTs from `rgba32f` to `rgba16`, thus halving the VRAM usage as expected. 2. This does not, however, substantially...

> Does gpu without -next uses rgba16? Yes > Anyway, is this 30 seconds on gpu-next without caching and on gpu? Yes, no > Little CMS really cannot be optimised...

Maybe we should have separate properties for "tagged primaries" and "effective primaries". The latter notably also depends on the VO in use. At the moment only `--vo=gpu-next` will actually apply...

> i quite like the current typing indicator and it feels quite natural in the flow of the conversation. i'm not sure that it _should_ feel separate. the layout changes...

It's not exposed, but this controls it: ```diff diff --git a/libavfilter/vf_libplacebo.c b/libavfilter/vf_libplacebo.c index cfee1117e8..ce0a19dc58 100644 --- a/libavfilter/vf_libplacebo.c +++ b/libavfilter/vf_libplacebo.c @@ -338,6 +338,8 @@ static int process_frames(AVFilterContext *avctx, AVFrame *out, AVFrame...

See also https://code.videolan.org/videolan/libplacebo/-/issues/29