[libav-devel] [PATCH] Adding / Changing some NVENC options Naming

Change profile option high_444 to high444p. And add auto option in level. This is to keep consistent naming between libav and ffmpeg and avoid confusion for users. Thanks, Ben --- This email message is for the sole

Re: [libav-devel] [PATCH 03/10] lavc: Add a new function to probe hardware support

On Tue, 28 Mar 2017 13:27:49 +0100 Mark Thompson wrote: > On 28/03/17 11:18, wm4 wrote: > > On Mon, 27 Mar 2017 21:38:12 +0100 > > Mark Thompson wrote: > [...] > >> +int avcodec_probe_hw(AVCodecContext *avctx, AVBufferRef *hw_frames_ref); > > > > This API

Re: [libav-devel] [PATCH 03/10] lavc: Add a new function to probe hardware support

On 28/03/17 11:18, wm4 wrote: > On Mon, 27 Mar 2017 21:38:12 +0100 > Mark Thompson wrote: > >> This also adds a new field to AVHWAccel to set supported hardware device >> types, so that we can query the right hwaccel. >> --- >> Not entirely sure that the AVCodecContext should be

Re: [libav-devel] [PATCH 09/10] lavfi/qsv: Use extra_hw_frames setting when allocating output frames

On 27/03/2017 22:38, Mark Thompson wrote: > The deinterlacer does not change, because it does not allocate any new > frames (for output it uses the same pool as the input). > --- > libavfilter/vf_scale_qsv.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git

Re: [libav-devel] [RFC] Changing AV_PIX_FMT_NONE from -1 to 0

On 28/03/2017 12:43, wm4 wrote: > I propose that AV_PIX_FMT_NONE is changed from -1 to 0. The reason is > that default-initializing an AVPixelFormat should set an invalid or > neutral value, instead of a "random" valid value. > > Currently, 0 means AV_PIX_FMT_YUV420P, which is confusing and can

[libav-devel] [PATCH 2/2] Use LOCAL_ALIGNED_32 instead of LOCAL_ALIGNED(32

This allows using compiler attributes for aligning the local variables, in the cases where the compiler supports such alignment for stack variables. libavutil/internal.h needs to include mem.h, since it uses the DECLARE_ALIGNED macro. --- libavcodec/dcadec.c | 4 ++-- libavcodec/lpc.c

[libav-devel] [PATCH 1/2] atrac3plusdsp: Use LOCAL_ALIGNED for stack variables

This fixes warnings like these with ARMCC: alignment for an auto object may not be larger than 8 --- libavcodec/atrac3plusdsp.c | 10 ++ 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/libavcodec/atrac3plusdsp.c b/libavcodec/atrac3plusdsp.c index 468f098..c1a54ae 100644 ---

Re: [libav-devel] [PATCH] hevcdec: Use LOCAL_ALIGNED_* for declaring local variables with alignment

On Tue, Mar 28, 2017 at 12:58:06PM +0300, Martin Storsjö wrote: > --- a/libavcodec/hevcdec.c > +++ b/libavcodec/hevcdec.c > @@ -917,8 +917,8 @@ static void hls_residual_coding(HEVCContext *s, int x0, > int y0, > -DECLARE_ALIGNED(32, int16_t, coeffs[MAX_TB_SIZE * MAX_TB_SIZE]) = { 0 }; > -

Re: [libav-devel] [RFC] Changing AV_PIX_FMT_NONE from -1 to 0

On Tue, Mar 28, 2017 at 12:43 PM, wm4 wrote: > I propose that AV_PIX_FMT_NONE is changed from -1 to 0. The reason is > that default-initializing an AVPixelFormat should set an invalid or > neutral value, instead of a "random" valid value. > > Currently, 0 means

[libav-devel] [RFC] Changing AV_PIX_FMT_NONE from -1 to 0

I propose that AV_PIX_FMT_NONE is changed from -1 to 0. The reason is that default-initializing an AVPixelFormat should set an invalid or neutral value, instead of a "random" valid value. Currently, 0 means AV_PIX_FMT_YUV420P, which is confusing and can lead to errors, especially since almost all

Re: [libav-devel] [PATCH 10/10] avconv: Test avcodec_probe_hw()

On Mon, 27 Mar 2017 21:38:19 +0100 Mark Thompson wrote: > Test only, not to commit in this form. > --- > avtools/avconv_hw.c | 29 - > 1 file changed, 28 insertions(+), 1 deletion(-) > > diff --git a/avtools/avconv_hw.c b/avtools/avconv_hw.c > index

Re: [libav-devel] [PATCH 07/10] lavfi: Add a way to control how many hardware frames are allocated for filtering

On Mon, 27 Mar 2017 21:38:16 +0100 Mark Thompson wrote: > This functions identically to the same field in AVCodecContext. > --- > doc/APIchanges | 3 +++ > libavfilter/avfilter.c | 2 ++ > libavfilter/avfilter.h | 13 + > 3 files changed, 18 insertions(+) >

Re: [libav-devel] [PATCH 05/10] lavc: Add a way to control how many hardware frames are allocated for decode

On Mon, 27 Mar 2017 21:38:14 +0100 Mark Thompson wrote: > --- > doc/APIchanges | 3 +++ > libavcodec/avcodec.h | 14 ++ > libavcodec/options_table.h | 1 + > 3 files changed, 18 insertions(+) > > diff --git a/doc/APIchanges b/doc/APIchanges >

Re: [libav-devel] [PATCH 03/10] lavc: Add a new function to probe hardware support

On Mon, 27 Mar 2017 21:38:12 +0100 Mark Thompson wrote: > This also adds a new field to AVHWAccel to set supported hardware device > types, so that we can query the right hwaccel. > --- > Not entirely sure that the AVCodecContext should be the first argument of > probe_hw() -

[libav-devel] [PATCH] hevcdec: Use LOCAL_ALIGNED_* for declaring local variables with alignment

Not all compilers can do alignment larger than the normal stack alignment for variables on the stack. In these cases, the LOCAL_ALIGNED_* macros produce the workaround alignment wrapper consisting of a padded array and a pointer variable. This fixes the hevc fate tests on RVCT/ARMCC after adding

Re: [libav-devel] [PATCH 05/10] lavc: Add a way to control how many hardware frames are allocated for decode

On 27/03/2017 22:38, Mark Thompson wrote: > --- > doc/APIchanges | 3 +++ > libavcodec/avcodec.h | 14 ++ > libavcodec/options_table.h | 1 + > 3 files changed, 18 insertions(+) Seems fine. ___ libav-devel mailing list

Re: [libav-devel] [PATCH 06/10] vaapi: Use extra_hw_frames setting when allocating frames

On 27/03/2017 22:38, Mark Thompson wrote: > --- > libavcodec/vaapi_decode.c | 3 ++- > 1 file changed, 2 insertions(+), 1 deletion(-) > > diff --git a/libavcodec/vaapi_decode.c b/libavcodec/vaapi_decode.c > index 82e919858..6910ecab6 100644 > --- a/libavcodec/vaapi_decode.c > +++

Re: [libav-devel] [PATCH 01/10] lavc: Add flag to allow profile mismatch with hardware decoding

On 28/03/17 10:06, wm4 wrote: > On Mon, 27 Mar 2017 21:38:10 +0100 > Mark Thompson wrote: > >> --- >> For naughty people only - this won't be set by default anywhere. >> >> >> doc/APIchanges | 3 +++ >> libavcodec/avcodec.h | 14 ++ >> 2 files changed, 17

Re: [libav-devel] [PATCH 01/10] lavc: Add flag to allow profile mismatch with hardware decoding

On Mon, 27 Mar 2017 21:38:10 +0100 Mark Thompson wrote: > --- > For naughty people only - this won't be set by default anywhere. > > > doc/APIchanges | 3 +++ > libavcodec/avcodec.h | 14 ++ > 2 files changed, 17 insertions(+) > > diff --git

Re: [libav-devel] [PATCH] arm: Always build the hevcdsp_init_arm.c file

On Tue, Mar 28, 2017 at 11:09:45AM +0300, Martin Storsjö wrote: > The main hevcdsp.c file calls this init function if HAVE_ARM is set, > regardless of whether neon support is available or not. > > This fixes builds where neon isn't supported by the build tools at all. > --- >

[libav-devel] [PATCH] arm: Always build the hevcdsp_init_arm.c file

The main hevcdsp.c file calls this init function if HAVE_ARM is set, regardless of whether neon support is available or not. This fixes builds where neon isn't supported by the build tools at all. --- libavcodec/arm/Makefile | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git

Re: [libav-devel] [PATCH 2/3] Add FM Screen Capture Codec decoder

On Fri, Mar 24, 2017 at 04:47:55PM +0100, Vittorio Giovara wrote: > On Fri, Mar 24, 2017 at 4:10 PM, Diego Biurrun wrote: > > --- a/Changelog > > +++ b/Changelog > > @@ -12,6 +12,7 @@ version : > > - The x86 assembler default switched from yasm to nasm, pass > >

Re: [libav-devel] [PATCH 1/3] Add av_calloc() helper

On Fri, Mar 24, 2017 at 04:20:40PM +0100, Luca Barbato wrote: > On 24/03/2017 16:10, Diego Biurrun wrote: > > --- a/libavutil/mem.c > > +++ b/libavutil/mem.c > > @@ -193,6 +193,13 @@ void *av_mallocz(size_t size) > > +void *av_calloc(size_t nmemb, size_t size) > > +{ > > +if (size <= 0 ||

Re: [libav-devel] [PATCH 2/3] Add FM Screen Capture Codec decoder

On Mon, Mar 27, 2017 at 12:59:13PM +0200, Vittorio Giovara wrote: > On Mon, Mar 27, 2017 at 12:17 PM, Diego Biurrun wrote: > > On Fri, Mar 24, 2017 at 04:47:55PM +0100, Vittorio Giovara wrote: > >> On Fri, Mar 24, 2017 at 4:10 PM, Diego Biurrun wrote: > >> > +