On Tue, 2021-12-14 at 05:53 +, Eoff, Ullysses A wrote:
> > -Original Message-
> > From: ffmpeg-devel On Behalf Of Chen,
> > Wenbin
> > Sent: Monday, December 13, 2021 6:24 PM
> > To: ffmpeg-devel@ffmpeg.org
> > Subject: Re: [FFmpeg-devel] [PATCH] li
> -Original Message-
> From: ffmpeg-devel On Behalf Of Chen, Wenbin
> Sent: Monday, December 13, 2021 6:24 PM
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] [PATCH] libavutil/hwcontext_qsv: clean padding
> when upload qsv frames
>
> > On Thu
> On Thu, 2021-12-02 at 15:40 +0800, Wenbin Chen wrote:
> > When we upload a frame that is not padded as MSDK requires, we create a
> > new AVFrame to copy data. The frame's padding data is uninitialized so
> > it brings run to run problem. For example, If we run the following
> > command serveral
On Thu, 2021-12-02 at 15:40 +0800, Wenbin Chen wrote:
> When we upload a frame that is not padded as MSDK requires, we create a
> new AVFrame to copy data. The frame's padding data is uninitialized so
> it brings run to run problem. For example, If we run the following
> command serveral times we
ng
> when upload qsv frames
>
> > -Original Message-
> > From: ffmpeg-devel On Behalf Of Wenbin
> > Chen
> > Sent: Wednesday, December 01, 2021 11:41 PM
> > To: ffmpeg-devel@ffmpeg.org
> > Cc: Chen, Wenbin
> > Subject: [FFmpeg-devel] [PATC
> -Original Message-
> From: ffmpeg-devel On Behalf Of Wenbin Chen
> Sent: Wednesday, December 01, 2021 11:41 PM
> To: ffmpeg-devel@ffmpeg.org
> Cc: Chen, Wenbin
> Subject: [FFmpeg-devel] [PATCH] libavutil/hwcontext_qsv: clean padding when
> upload qsv frames
>
When we upload a frame that is not padded as MSDK requires, we create a
new AVFrame to copy data. The frame's padding data is uninitialized so
it brings run to run problem. For example, If we run the following
command serveral times we will get different outputs.
ffmpeg -init_hw_device qsv=qsv:hw
