On 7/8/2019 2:45 PM, Yan Wang wrote:
On 7/7/2019 9:49 PM, Fu, Linjie wrote:
-Original Message-
From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf
Of Mark Thompson
Sent: Sunday, July 7, 2019 19:51
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH 2/2
which is AVFrame in fact and pass them into
libva when re-creating new va_context.
Thanks.
Yan Wang
As libva allows re-create surface separately without changing the
context, this issue could be handled by only recreating hw_frames_ctx.
Could be verified by:
ffmpeg -hwaccel vaapi -hwa
On 5/30/2019 7:39 AM, Mark Thompson wrote:
On 28/05/2019 08:46, Yan Wang wrote:
On 5/28/2019 3:16 PM, Hendrik Leppkes wrote:
On Tue, May 28, 2019 at 8:57 AM Yan Wang wrote:
When the format change, the VAAPI context cannot be destroyed.
Otherwise, the reference frame surface will lost
On 5/28/2019 4:43 PM, Hendrik Leppkes wrote:
On Tue, May 28, 2019 at 9:46 AM Yan Wang wrote:
On 5/28/2019 3:16 PM, Hendrik Leppkes wrote:
On Tue, May 28, 2019 at 8:57 AM Yan Wang wrote:
When the format change, the VAAPI context cannot be destroyed.
Otherwise, the reference frame surface
On 5/28/2019 3:16 PM, Hendrik Leppkes wrote:
On Tue, May 28, 2019 at 8:57 AM Yan Wang wrote:
When the format change, the VAAPI context cannot be destroyed.
Otherwise, the reference frame surface will lost.
Signed-off-by: Yan Wang
---
libavcodec/decode.c | 6 ++
1 file changed, 6
When the format change, the VAAPI context cannot be destroyed.
Otherwise, the reference frame surface will lost.
Signed-off-by: Yan Wang
---
libavcodec/decode.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/libavcodec/decode.c b/libavcodec/decode.c
index 6c31166ec2..3eda1dc42c
