On Di, 2023-05-16 at 16:22 +0800, zhilizhao(赵志立) wrote:
>
> > On May 16, 2023, at 15:52, Hendrik Leppkes wrote:
> >
> > On Tue, May 16, 2023 at 4:07 AM Xiang, Haihao
> > wrote:
> > >
> > > From: Haihao Xiang
> > >
> > > Intel MediaSDK and oneVPL expect contiguous allocation for data[i],
> >
> On May 16, 2023, at 15:52, Hendrik Leppkes wrote:
>
> On Tue, May 16, 2023 at 4:07 AM Xiang, Haihao
> wrote:
>>
>> From: Haihao Xiang
>>
>> Intel MediaSDK and oneVPL expect contiguous allocation for data[i],
>> however there are mandatory padding bytes between data[i] and data[i+1].
>> whe
On Tue, May 16, 2023 at 4:07 AM Xiang, Haihao
wrote:
>
> From: Haihao Xiang
>
> Intel MediaSDK and oneVPL expect contiguous allocation for data[i],
> however there are mandatory padding bytes between data[i] and data[i+1].
> when calling av_frame_get_buffer. So adding av_frame_get_buffer2 to
> al
From: Haihao Xiang
Intel MediaSDK and oneVPL expect continuous allocation for data[i],
however there are mandatory padding bytes between data[i] and data[i+1].
when calling av_frame_get_buffer. So adding av_frame_get_buffer2 to
allow caller to specify the length of padding bytes.
Signed-off-by:
