Re: [FFmpeg-devel] [PATCH 1/2] libavcodec/amfenc_hevc.c: Fix constant QP settings for I, P

> 28 янв. 2020 г., в 19:53, OvchinnikovDmitrii > написал(а): > > --- > libavcodec/amfenc_hevc.c | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git a/libavcodec/amfenc_hevc.c b/libavcodec/amfenc_hevc.c > index 7c9a33ab33..8b4d289fac 100644 > --- a/libavcodec/amfenc_hevc.c

Re: [FFmpeg-devel] [PATCH] lavc/amfenc: Reference to input AVFrame (hwaccel) is retained during the encoding process

> > Put email comments on a patch below the "---" line (otherwise they end up in > the commit message when applied). > Sorry, I am not sure I understand you correctly here > > +#define AMF_AV_GET_PROPERTY_INTERFACE(res, pThis, name, TargetType, val) \ > > +{ \ > > +AMFVariantStruct v

[FFmpeg-devel] [PATCH] lavc/amfenc: Reference to input AVFrame (hwaccel) is retained during the encoding process

An additional reference to input AVFrame (hwaccel) is retained during the encoding process. This postpone reusing frames by decoder while they are used by encoder and prevents frame corruption Issue with frame corruption was reproduced using: ffmpeg.exe -y -hwaccel d3d11va -hwaccel_output_format

[FFmpeg-devel] [PATCH] AMF Encoder: fix issue with frame corruption if encoder connected directly to decoder

Hello, I am collaborating with AMD to integrate and support AMF integration FFmpeg This patch solves issue with frame corruption if encoder connected directly to decoder Solution: storing frame reference while it is used during encoding From 0fae3679bae8e121ed7b997d7eabd533deb113fb Mon Sep 17 00