On Ma, 2024-02-26 at 06:11 +, Xiang, Haihao wrote:
> On So, 2024-02-25 at 19:51 +, Mark Thompson wrote:
> > Since e0da916b8f5b079a4865eef7f64863f50785463d the ffmpeg utility has
> > held multiple frames output by the filter graph in internal queues
> > without telling the filter which creat
On So, 2024-02-25 at 19:51 +, Mark Thompson wrote:
> Since e0da916b8f5b079a4865eef7f64863f50785463d the ffmpeg utility has
> held multiple frames output by the filter graph in internal queues
> without telling the filter which created the frames that it is going to
> do so. This broke many VAA
Since e0da916b8f5b079a4865eef7f64863f50785463d the ffmpeg utility has
held multiple frames output by the filter graph in internal queues
without telling the filter which created the frames that it is going to
do so. This broke many VAAPI filter->encode cases because a fixed-size
frame pool is use
