[FFmpeg-devel] Hardware acceleration decoding question

Hello all, I am using FFmpeg libarary in my software to do HW decoding for video (H.264\H.265) on windows machine. My decoding is based on 'hw_decode.c' example, and after i call decode a frame i am using AVFrame::data[3] to get the pointer to the IDirect3DSurface9 and use it in my video player.

Re: [FFmpeg-devel] Hardware acceleration decoding question

Thanks Timo for the reply , no it's clear to me, and sorry for the question location i made. On Thu, May 23, 2019 at 12:29 PM Timo Rothenpieler wrote: > On 23.05.2019 10:06, Asaf Kave wrote: > > Hello all, > > I am using FFmpeg libarary in my software to do HW decoding for vid

Re: [FFmpeg-devel] [PATCH 1/1] libavcodec/h264: Handle ENOMEM error when decoding slice nal unit.

Hello all, Long time pass, can somebody look at this? Thanks On Wed, Jul 17, 2019 at 11:35 AM Asaf Kave wrote: > Populate the real error when alloc_picture failed, during decoding h264 > slice. > When this error occurred, need to break the decoding process of the rest > nal

[FFmpeg-devel] [PATCH 1/1] libavcodec/h264: Handle ENOMEM error when decoding slice nal unit.

Populate the real error when alloc_picture failed, during decoding h264 slice. When this error occurred, need to break the decoding process of the rest nal's, and need to rise this error back to the user, to indicate that there is decoder memory issue. --- libavcodec/h264_slice.c | 5 +++--

[FFmpeg-devel] Motion vectors implementation for HEVC

Hi all, I am intersting on extracting motion vectors in the HEVC decoder, get it from the side_data of the decoded frame like we doing in the h.264, good example is the extarct_mvs.c file . So i will be glad if someone will give me the entry points for : - Is there a reason why this is not

Re: [FFmpeg-devel] [PATCH v2] HEVC: Export motion vectors to frame side data.

On Wed, Feb 12, 2020 at 4:02 PM Paul B Mahol wrote: > On 2/12/20, Asaf Kave wrote: > > On Wed, Feb 12, 2020 at 11:35 AM Paul B Mahol wrote: > > > >> On 2/12/20, Asaf Kave wrote: > >> > On Sun, Feb 9, 2020 at 10:59 AM Asaf Kave wrote: > >> > >

Re: [FFmpeg-devel] [PATCH v2] HEVC: Export motion vectors to frame side data.

On Sun, Feb 9, 2020 at 10:59 AM Asaf Kave wrote: > > > On Thu, Feb 6, 2020 at 4:10 PM Lynne wrote: > >> Feb 6, 2020, 11:17 by kavea...@gmail.com: >> >> > On Sun, Feb 2, 2020 at 11:15 AM Asaf Kave wrote: >> > >> >> >>

Re: [FFmpeg-devel] [PATCH v2] HEVC: Export motion vectors to frame side data.

On Thu, Feb 6, 2020 at 4:10 PM Lynne wrote: > Feb 6, 2020, 11:17 by kavea...@gmail.com: > > > On Sun, Feb 2, 2020 at 11:15 AM Asaf Kave wrote: > > > >> > >> > >> On Tue, Jan 28, 2020 at 11:44 PM Asaf Kave wrote: > >> > >

Re: [FFmpeg-devel] [PATCH v2] HEVC: Export motion vectors to frame side data.

On Wed, Feb 12, 2020 at 11:35 AM Paul B Mahol wrote: > On 2/12/20, Asaf Kave wrote: > > On Sun, Feb 9, 2020 at 10:59 AM Asaf Kave wrote: > > > >> > >> > >> On Thu, Feb 6, 2020 at 4:10 PM Lynne wrote: > >> > >>> Feb 6, 2020, 11:17

Re: [FFmpeg-devel] [PATCH 4/4] libavutil: AVEncodeInfo data structures

On Sat, Feb 29, 2020 at 2:23 PM Michael Niedermayer wrote: > From: Juan De León > > AVEncodeInfoFrame data structure to store as AVFrameSideData of type > AV_FRAME_DATA_ENCODE_INFO. > The structure stores quantization index for each plane, DC/AC deltas > for luma and chroma planes, and an array

Re: [FFmpeg-devel] [PATCH v2] HEVC: Export motion vectors to frame side data.

On Wed, Jan 22, 2020 at 1:09 PM Asaf Kave wrote: > > > On Tue, Jan 21, 2020 at 8:17 PM Lynne wrote: > >> Jan 20, 2020, 08:42 by kavea...@gmail.com: >> >> > Ping >> > >> >> https://ffmpeg.org/pipermail/ffmpeg-devel/2019-August/248836.html

Re: [FFmpeg-devel] [PATCH v2] HEVC: Export motion vectors to frame side data.

On Sun, Jan 26, 2020, 12:31 Asaf Kave wrote: > > > On Wed, Jan 22, 2020 at 1:09 PM Asaf Kave wrote: > >> >> >> On Tue, Jan 21, 2020 at 8:17 PM Lynne wrote: >> >>> Jan 20, 2020, 08:42 by kavea...@gmail.com: >>> >>> > Ping &

Re: [FFmpeg-devel] [PATCH v2] HEVC: Export motion vectors to frame side data.

On Sun, Feb 2, 2020 at 11:15 AM Asaf Kave wrote: > > > On Tue, Jan 28, 2020 at 11:44 PM Asaf Kave wrote: > >> >> >> On Sun, Jan 26, 2020, 12:31 Asaf Kave wrote: >> >>> >>> >>> On Wed, Jan 22, 2020 at 1:09 PM Asaf Kave wrote:

Re: [FFmpeg-devel] [PATCH v2] HEVC: Export motion vectors to frame side data.

On Tue, Jan 28, 2020 at 11:44 PM Asaf Kave wrote: > > > On Sun, Jan 26, 2020, 12:31 Asaf Kave wrote: > >> >> >> On Wed, Jan 22, 2020 at 1:09 PM Asaf Kave wrote: >> >>> >>> >>> On Tue, Jan 21, 2020 at 8:17 PM Lynne wrote: >&

Re: [FFmpeg-devel] [PATCH v2] HEVC: Export motion vectors to frame side data.

On Thu, Feb 13, 2020 at 3:54 PM Paul B Mahol wrote: > On 2/13/20, Asaf Kave wrote: > > On Wed, Feb 12, 2020 at 4:02 PM Paul B Mahol wrote: > > > >> On 2/12/20, Asaf Kave wrote: > >> > On Wed, Feb 12, 2020 at 11:35 AM Paul B Mahol > wrote: >

Re: [FFmpeg-devel] [PATCH] HEVC: Export motion vectors to frame side data.

On Wed, Jan 8, 2020 at 11:30 AM Asaf Kave wrote: > > > On Tue, Jan 7, 2020 at 4:49 AM Zhong Li wrote: > >> Haven't tested but patch LGTM >> > > Thanks Li for the feedback. > > >> >> Asaf Kave 于2019年12月29日周日 下午10:08写道： >> > >>

[FFmpeg-devel] [PATCH v2] HEVC: Export motion vectors to frame side data.

--- libavcodec/hevc_refs.c | 15 libavcodec/hevcdec.c | 179 - libavcodec/hevcdec.h | 13 +++ 3 files changed, 206 insertions(+), 1 deletion(-) diff --git a/libavcodec/hevc_refs.c b/libavcodec/hevc_refs.c index 7870a72fd6..20f028fa73 100644 ---

Re: [FFmpeg-devel] [PATCH v2] HEVC: Export motion vectors to frame side data.

On Thu, Jan 16, 2020 at 4:19 PM Carl Eugen Hoyos wrote: > Am Do., 16. Jan. 2020 um 14:10 Uhr schrieb Lynne : > > > > Jan 15, 2020, 09:19 by kavea...@gmail.com: > > > > > --- > > > libavcodec/hevc_refs.c | 15 > > > libavcodec/hevcdec.c | 179 - > >

Re: [FFmpeg-devel] [PATCH] HEVC: Export motion vectors to frame side data.

u for your time. Will update patch soon. I had a quick look code and have comments below: > > On Sun, 29. Dec 16:08, Asaf Kave wrote: > > --- > > libavcodec/hevc_refs.c | 15 > > libavcodec/hevcdec.c | 173 - > > libavcode

Re: [FFmpeg-devel] [PATCH v2] HEVC: Export motion vectors to frame side data.

Ping On Thu, Jan 16, 2020 at 4:59 PM Asaf Kave wrote: > > > On Thu, Jan 16, 2020 at 4:19 PM Carl Eugen Hoyos > wrote: > >> Am Do., 16. Jan. 2020 um 14:10 Uhr schrieb Lynne : >> > >> > Jan 15, 2020, 09:19 by kavea...@gmail.com: >> >

Re: [FFmpeg-devel] [PATCH v2] HEVC: Export motion vectors to frame side data.

On Tue, Jan 21, 2020 at 8:17 PM Lynne wrote: > Jan 20, 2020, 08:42 by kavea...@gmail.com: > > > Ping > > > > https://ffmpeg.org/pipermail/ffmpeg-devel/2019-August/248836.html > > > I've okayed it, its just not been pushed yet. > You'll need to add the vectors to the block struct. int16_t [2]

Re: [FFmpeg-devel] [PATCH] HEVC: Export motion vectors to frame side data.

On Sun, Dec 29, 2019 at 4:08 PM Asaf Kave wrote: > --- > libavcodec/hevc_refs.c | 15 > libavcodec/hevcdec.c | 173 - > libavcodec/hevcdec.h | 13 > 3 files changed, 200 insertions(+), 1 deletion(-) > > diff --git a/l

[FFmpeg-devel] [PATCH] HEVC: Export motion vectors to frame side data.

--- libavcodec/hevc_refs.c | 15 libavcodec/hevcdec.c | 173 - libavcodec/hevcdec.h | 13 3 files changed, 200 insertions(+), 1 deletion(-) diff --git a/libavcodec/hevc_refs.c b/libavcodec/hevc_refs.c index 7870a72fd6..20f028fa73 100644 ---

Re: [FFmpeg-devel] [PATCH] HEVC: Export motion vectors to frame side data.

On Thu, Jan 2, 2020 at 11:59 AM Asaf Kave wrote: > > > On Sun, Dec 29, 2019 at 4:08 PM Asaf Kave wrote: > >> --- >> libavcodec/hevc_refs.c | 15 >> libavcodec/hevcdec.c | 173 - >> libavcodec/hevcdec.h

Re: [FFmpeg-devel] [PATCH] HEVC: Export motion vectors to frame side data.

On Tue, Jan 7, 2020 at 4:49 AM Zhong Li wrote: > Haven't tested but patch LGTM > Thanks Li for the feedback. > > Asaf Kave 于2019年12月29日周日 下午10:08写道： > > > > --- > > libavcodec/hevc_refs.c | 15 > > libavcodec/hevcdec.c | 173 +

[FFmpeg-devel] [PATCH] Enhancement for defect #6827

Adding error logs to identify special failure, when Directd3d 9 is not supported. see defect #6827 --- libavutil/hwcontext_dxva2.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/libavutil/hwcontext_dxva2.c b/libavutil/hwcontext_dxva2.c