Re: [libav-devel] [PATCH] aac: Rework extradata parsing code

On Fri, 13 Apr 2018 09:22:30 +0900 Luca Barbato wrote: > On 13/04/2018 06:44, Vittorio Giovara wrote: > > -if (new_extradata && 0) { > > Uh? faa2930f191099621e03c55cca32662467d3cc15 flvdec: reenable extradata passing code

Re: [libav-devel] [PATCH] Add Haivision Open SRT protocol

On Thu, 22 Mar 2018 14:42:40 +0100 "Sven Dueking" <s...@nablet.com> wrote: > > -Ursprüngliche Nachricht- > > Von: libav-devel [mailto:libav-devel-boun...@libav.org] Im Auftrag von > > wm4 > > Gesendet: Donnerstag, 22. März 2018 14:38 > > An:

Re: [libav-devel] [PATCH] Add Haivision Open SRT protocol

On Thu, 22 Mar 2018 14:24:08 +0100 "Sven Dueking" <s...@nablet.com> wrote: > > -Ursprüngliche Nachricht- > > Von: libav-devel [mailto:libav-devel-boun...@libav.org] Im Auftrag von > > wm4 > > Gesendet: Donnerstag, 22. März 2018 14:03 > > An:

Re: [libav-devel] [PATCH] Add Haivision Open SRT protocol

On Thu, 22 Mar 2018 13:17:16 +0100 Diego Biurrun wrote: > On Thu, Mar 22, 2018 at 12:34:29PM +0100, Sven Dueking wrote: > > > On Wed, Mar 21, 2018 at 04:03:18PM +0100, Sven Dueking wrote: > > > > > On Wed, Mar 21, 2018 at 03:00:37PM +0100, Luca Barbato wrote: > > > > > > On

Re: [libav-devel] [PATCH 3/7] x265: Use the framerate information instead of the timebase

On Fri, 16 Feb 2018 18:02:05 +0100 Luca Barbato wrote: > Unbreaks the rate-control behaviour. > --- > libavcodec/libx265.c | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git a/libavcodec/libx265.c b/libavcodec/libx265.c > index fd5452193b..73aff2caef

Re: [libav-devel] [PATCH] network: use strncmp() to avoid an OOB read

On Tue, 13 Feb 2018 17:31:56 +0100 Hendrik Leppkes wrote: > On Tue, Feb 13, 2018 at 5:16 PM, Sean McGovern wrote: > > > > I discovered this while doing a full valgrind FATE run on a POWER7 > > machine -- among others, fate-noproxy failed. > > > > The

Re: [libav-devel] [PATCH 6/8] vf_hwupload/hwmap: Support setting a fixed pool size

On Sun, 11 Feb 2018 23:09:51 + Mark Thompson wrote: > On 11/02/18 07:21, Song, Ruiling wrote: > > I have run some test against the patches. It works as described. > > Great - there is general agreement on that part now so I've applied that > series. > > > Are you still

Re: [libav-devel] [PATCH 10/16] cbs: Refcount all the things!

On Sun, 11 Feb 2018 18:14:34 + Mark Thompson wrote: > --- > libavcodec/cbs.c | 168 +--- > libavcodec/cbs.h | 51 - > libavcodec/cbs_h264.h | 4 + > libavcodec/cbs_h2645.c | 341

Re: [libav-devel] [PATCH] Add AV1 video decoding support through libaom

On Sun, 11 Feb 2018 18:44:44 + Mark Thompson wrote: > On 10/02/18 16:29, Luca Barbato wrote: > > On 10/02/2018 16:59, Diego Biurrun wrote: > >> Looks OK in general. > >> > >> On Fri, Feb 09, 2018 at 10:51:36AM +0100, Luca Barbato wrote: > >>> --- /dev/null > >>> +++

Re: [libav-devel] [PATCH] Add AV1 video decoding support through libaom

On Sun, 11 Feb 2018 18:44:44 + Mark Thompson wrote: > On 10/02/18 16:29, Luca Barbato wrote: > > On 10/02/2018 16:59, Diego Biurrun wrote: > >> Looks OK in general. > >> > >> On Fri, Feb 09, 2018 at 10:51:36AM +0100, Luca Barbato wrote: > >>> --- /dev/null > >>> +++

Re: [libav-devel] [PATCH] Add AV1 video decoding support through libaom

On Sun, 11 Feb 2018 18:44:44 + Mark Thompson wrote: > On 10/02/18 16:29, Luca Barbato wrote: > > On 10/02/2018 16:59, Diego Biurrun wrote: > >> Looks OK in general. > >> > >> On Fri, Feb 09, 2018 at 10:51:36AM +0100, Luca Barbato wrote: > >>> --- /dev/null > >>> +++

Re: [libav-devel] Add HW H.264 and HEVC encoding for AMD GPUs based on AMF SDK

On Wed, 7 Feb 2018 19:35:05 + "Mironov, Mikhail" wrote: > Regarding PRId64 macro: > Started to look into this and found that at least in Microsoft's version of > inttypes.h there no definitions for Unicode strings. All AMF tracing /logging > is Unicode. > So the

Re: [libav-devel] [PATCH 1/8] lavc: Add support for increasing hardware frame pool sizes

On Sun, 4 Feb 2018 14:27:10 + Mark Thompson wrote: > AVCodecContext.extra_hw_frames is added to the size of hardware frame > pools created by libavcodec for APIs which require fixed-size pools. > This allows the user to keep references to a greater number of frames > after

Re: [libav-devel] [PATCH 08/12] vf_hwupload/hwmap: Support setting a fixed pool size

On Sun, 4 Feb 2018 14:26:51 + Mark Thompson <s...@jkqxz.net> wrote: > On 30/01/18 05:34, wm4 wrote: > > On Mon, 29 Jan 2018 23:01:25 + > > Mark Thompson <s...@jkqxz.net> wrote: > > > >> These filters do not directly know whether the API they

Re: [libav-devel] [PATCH] avpacket: Initialize the allocated padding area in side data

On Thu, 1 Feb 2018 15:02:37 +0200 Martin Storsjö wrote: > This makes sure that consumers of the side data actually can > rely on the padding as intended, without having the callers of > av_packet_new_side_data to explicitly zero initialize it. > --- > libavcodec/avpacket.c |

Re: [libav-devel] [PATCH 01/12] lavc: Add support for increasing hardware frame pool sizes

frames > after decode, which may be necessary for some use-cases. > > It is also added to the initial_pool_size value returned by > avcodec_get_hw_frames_parameters() if a fixed-size pool is required. > --- > On 26/01/18 23:39, wm4 wrote: > > On Fri, 26 Jan 2018 23:30:48

Re: [libav-devel] [PATCH 08/12] vf_hwupload/hwmap: Support setting a fixed pool size

On Mon, 29 Jan 2018 23:01:25 + Mark Thompson wrote: > These filters do not directly know whether the API they are using will > support dynamic frame pools, so this is somewhat tricky. If the user > set extra_hw_frames, we assume that they are aware of the problem and > set a

Re: [libav-devel] [PATCH 04/12] lavc/dxva2: Don't add per-thread surfaces twice

On Mon, 29 Jan 2018 23:01:21 + Mark Thompson wrote: > This is already accounted for in the generic code, so it shouldn't also > be added here. > --- > libavcodec/dxva2.c | 4 > 1 file changed, 4 deletions(-) > > diff --git a/libavcodec/dxva2.c b/libavcodec/dxva2.c >

Re: [libav-devel] [PATCH 1/8] lavfi: Add support for modifying hardware frame pool sizes

On Fri, 26 Jan 2018 23:30:48 + Mark Thompson wrote: > On 26/01/18 23:13, Mark Thompson wrote: > > AVFilterContext.extra_hw_frames functions identically to the field of > > the same name in AVCodecContext. > > Of course, that field doesn't actually exist before this patch

Re: [libav-devel] [PATCH 1/8] lavfi: Add support for modifying hardware frame pool sizes

On Fri, 26 Jan 2018 23:13:36 + Mark Thompson wrote: > AVFilterContext.extra_hw_frames functions identically to the field of > the same name in AVCodecContext. > --- > doc/APIchanges | 3 +++ > libavfilter/avfilter.c | 23 +++ >

Re: [libav-devel] qsv: How about replace software parsers with MFXVideoDECODE_DecodeHeader

> > leverages the software decoder for the parsing and a little more. > > > > In my opinion it boils down to either have a uniform behavior in parsing and > > formatting the input with its many quirks or using more of the hwaccel/sdk. > > > > I do not have a str

Re: [libav-devel] [PATCH] hwcontext_qsv: Fix qsv hwupload failure issue

On Fri, 26 Jan 2018 11:04:12 + Mark Thompson <s...@jkqxz.net> wrote: > On 26/01/18 09:15, wm4 wrote: > > On Fri, 26 Jan 2018 05:56:46 + > > "Li, Zhong" <zhong...@intel.com> wrote: > > > >>> From: libav-devel [mailto:libav-d

Re: [libav-devel] [PATCH] hwcontext_qsv: Fix qsv hwupload failure issue

On Fri, 26 Jan 2018 05:56:46 + "Li, Zhong" wrote: > > From: libav-devel [mailto:libav-devel-boun...@libav.org] On Behalf Of > > Ruiling Song > > Sent: Friday, January 26, 2018 9:17 AM > > To: libav-devel@libav.org > > Subject: [libav-devel] [PATCH] hwcontext_qsv: Fix qsv

Re: [libav-devel] qsv: How about replace software parsers with MFXVideoDECODE_DecodeHeader

On Tue, 23 Jan 2018 05:28:35 + "Li, Zhong" <zhong...@intel.com> wrote: > > wm4 <nfx...@googlemail.com> wrote: > > > > > > Appreciated for any comment. If we are agree with that, patches will > > be sent soon (about following next two

Re: [libav-devel] qsv: How about replace software parsers with MFXVideoDECODE_DecodeHeader

On Mon, 22 Jan 2018 14:52:00 +0100 wm4 <nfx...@googlemail.com> wrote: > > Appreciated for any comment. If we are agree with that, patches will be > > sent soon (about following next two weeks). > > I don't know how qsvdec works in particular (doesn't it pretty mu

Re: [libav-devel] qsv: How about replace software parsers with MFXVideoDECODE_DecodeHeader

On Mon, 22 Jan 2018 11:20:08 + "Li, Zhong" wrote: > MSDK provides an API (MFXVideoDECODE_DecodeHeader) to parse video > parameters. Currently it hasn't been used. > Instead, software parsers are used. It works well for h264 decoder, and > basically works well for hevc

Re: [libav-devel] [RFC] [PATCH] Set video strides to a custom type in preparation of a change to ptrdiff_t

ch to ptrdiff_t, a > better suited type to represent this type of data, in a way that it is > atomically changed at the version bump. > --- > > This is a work in progress change that I was preparing and briefly discussed > on IRC today, based on suggestion by wm4. I wanted to sh

Re: [libav-devel] [PATCH] mmaldec: Fix compilation after 2fcb0090

On Wed, 20 Dec 2017 09:45:37 +0200 Martin Storsjö wrote: > --- > libavcodec/mmaldec.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/libavcodec/mmaldec.c b/libavcodec/mmaldec.c > index 10a48d3e0f..504e765d07 100644 > --- a/libavcodec/mmaldec.c > +++

Re: [libav-devel] [RFC] Getting rid of the global log callback

On Sun, 17 Dec 2017 16:17:47 +0200 Rémi Denis-Courmont <r...@remlab.net> wrote: > Le sunnuntaina 17. joulukuuta 2017, 14.35.13 EET Luca Barbato a écrit : > > On 11/12/2017 14:48, wm4 wrote: > > > The log callback, set with av_log_set_callback(), is gl

[libav-devel] [PATCH v2] avcodec: add metadata to identify wrappers and hardware decoders

Explicitly identify decoder/encoder wrappers with a common name. This saves API users from guessing by the name suffix. For example, they don't have to guess that "h264_qsv" is the h264 QSV implementation, and instead they can just check the AVCodec .codec and .wrapper_name fields. Explicitly

Re: [libav-devel] [PATCH 1/9] lavc: Add codec metadata to indicate hardware support

On Sun, 10 Dec 2017 23:05:39 + Mark Thompson wrote: > --- > doc/APIchanges | 3 +++ > libavcodec/avcodec.h | 74 > > libavcodec/hwaccel.h | 18 + > libavcodec/utils.c | 12 + > 4 files

[libav-devel] [PATCH] [RFC] avcodec: add metadata to identify wrappers and hardware decoders

Explicitly identify decoder/encoder wrappers with a common name. This saves API users from guessing by the name suffix. For example, they don't have to guess that "h264_qsv" is the h264 QSV implementation, and instead they can just check the AVCodec .codec and .wrapper_name fields. Explicitly

[libav-devel] [RFC] Getting rid of the global log callback

The log callback, set with av_log_set_callback(), is global mutable state, and as such not something we want in Libav, at all. but getting rid of it is very complicated, because in most cases, av_log() does not have enough context available to find per-context log callbacks. av_log() has a

Re: [libav-devel] [PATCH] qsv/vp8dec: fix memory leak issue

On Thu, 7 Dec 2017 13:25:10 +0100 Luca Barbato wrote: > On 07/12/2017 08:26, Zhong Li wrote: > > Signed-off-by: Zhong Li > > --- > > libavcodec/qsvdec_other.c | 5 + > > 1 file changed, 5 insertions(+) > > > > diff --git

Re: [libav-devel] API breakage with old avcodec_decode_* functions

On Mon, 30 Oct 2017 15:50:58 + James Cowgill wrote: > Hi, > > This is an issue which was reported in a number of places. I'm asking > here since libav was the origin of the commit which broke things and > hopefully someone here has an answer. > >

Re: [libav-devel] [PATCH 1/9] lavc: Add codec metadata to indicate hardware support

On Fri, 27 Oct 2017 12:37:18 +0100 Mark Thompson wrote: > >> Can you suggest the sort of names you're thinking of here? I think this > >> might depend on (3) as well to be useful. > > > > I was thinking maybe "hwaccel_vaapi" etc. > > I feel like this sort of name is

Re: [libav-devel] [PATCH 1/9] lavc: Add codec metadata to indicate hardware support

On Thu, 26 Oct 2017 13:27:01 +0100 Mark Thompson <s...@jkqxz.net> wrote: > On 26/10/17 11:36, wm4 wrote: > > On Thu, 26 Oct 2017 00:18:39 +0100 > > Mark Thompson <s...@jkqxz.net> wrote: > > > >> --- > >> Rebased on the frame parameter change

Re: [libav-devel] [PATCH 1/9] lavc: Add codec metadata to indicate hardware support

On Thu, 26 Oct 2017 00:18:39 +0100 Mark Thompson wrote: > --- > Rebased on the frame parameter changes, and incorporating all review comments > from last time. > > > doc/APIchanges | 3 +++ > libavcodec/avcodec.h | 74 >

Re: [libav-devel] [RFC] [PATCH] Drop non-refcounted-frame code on the next version bump

On Sun, 22 Oct 2017 07:57:42 +0200 Diego Biurrun wrote: > --- > libavcodec/decode.c | 11 +++ > libavcodec/version.h | 3 +++ > libavfilter/vsrc_movie.c | 5 + > 3 files changed, 19 insertions(+) > > diff --git a/libavcodec/decode.c

[libav-devel] [PATCH] lavc: fix hw_device_ctx operation

Commit b46a77f19d accidentally broke this (requested change that was added to the patch later and which was not fully tested). --- Tested/confirmed by jkqxz on IRC. --- libavcodec/decode.c | 6 ++ 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/libavcodec/decode.c

Re: [libav-devel] [libav-commits] lavc: external hardware frame pool initialization

On Sun, 22 Oct 2017 02:15:07 +0200 Diego Biurrun <di...@biurrun.de> wrote: > On Thu, Oct 19, 2017 at 05:25:17PM +0200, wm4 wrote: > > Module: libav > > Author:wm4 <nfx...@googlemail.com> > > Committer: Anton Khirnov <an...@khirnov.net> > &

[libav-devel] [PATCH v4] lavc: external hardware frame pool initialization

This adds a new API, which allows the API user to query the required AVHWFramesContext parameters. This also reduces code duplication across the hwaccels by introducing ff_decode_get_hw_frames_ctx(), which uses the new API function. It takes care of initializing the hw_frames_ctx if needed, and

[libav-devel] [PATCH v3] lavc: external hardware frame pool initialization

This adds a new API, which allows the API user to query the required AVHWFramesContext parameters. This also reduces code duplication across the hwaccels by introducing ff_decode_get_hw_frames_ctx(), which uses the new API function. It takes care of initializing the hw_frames_ctx if needed, and

Re: [libav-devel] [PATCH] configure: fix libxavs check

On Thu, 12 Oct 2017 19:17:32 +0200 Diego Biurrun wrote: > On Thu, Oct 12, 2017 at 01:02:57AM -0300, James Almer wrote: > > libxavs may require pthreads and libm at link time, and without > > said ldflags available as global extralibs, the check will fail. > > > > Regression

Re: [libav-devel] [PATCH v2] lavc: external hardware frame pool initialization

On Wed, 11 Oct 2017 01:48:51 +0200 Anton Khirnov <an...@khirnov.net> wrote: > Quoting wm4 (2017-09-26 17:09:56) > > From: wm4 <nfx...@googlemail.com> > > > > This adds a new API, which allows the API user to query the required > > AVHWFramesContext paramet

Re: [libav-devel] [PATCH 1/7] lavc: Add codec metadata to indicate hardware support

On Wed, 4 Oct 2017 23:27:18 +0100 Mark Thompson <s...@jkqxz.net> wrote: > On 04/10/17 23:16, wm4 wrote: > > On Wed, 4 Oct 2017 23:01:47 +0100 > > Mark Thompson <s...@jkqxz.net> wrote: > >>> > >>> In addition to this, should there be an

Re: [libav-devel] [PATCH 2/9] lavc: Add a new file listing all hwaccels as external declarations

On Thu, 5 Oct 2017 08:47:59 +0100 Mark Thompson <s...@jkqxz.net> wrote: > On 05/10/17 08:43, wm4 wrote: > > On Wed, 4 Oct 2017 23:30:52 +0100 > > Mark Thompson <s...@jkqxz.net> wrote: > > > >> These are needed for the config structures in the fo

Re: [libav-devel] [PATCH 1/9] lavc: Add codec metadata to indicate hardware support

On Wed, 4 Oct 2017 23:30:51 +0100 Mark Thompson wrote: > --- > Bikeshed painters welcome for naming. > /** > + * Retrieve supported hardware configurations for a codec. > + */ > +const AVCodecHWConfig *avcodec_get_hw_config(const AVCodec *codec, int > index); Should

Re: [libav-devel] [PATCH 2/9] lavc: Add a new file listing all hwaccels as external declarations

On Wed, 4 Oct 2017 23:30:52 +0100 Mark Thompson wrote: > These are needed for the config structures in the following patch. > --- > Fake hwaccels are omitted, they would just be deleted in a later patch > without ever being used. > > > libavcodec/hwaccels.h | 59 >

Re: [libav-devel] [PATCH 1/7] lavc: Add codec metadata to indicate hardware support

On Wed, 4 Oct 2017 23:01:47 +0100 Mark Thompson wrote: > > > > In addition to this, should there be an AVCodec flag that tells the API > > user whether this decoder can do half-transparent software fallback? > > Half-transparent as in it can call get_format mid-stream to

Re: [libav-devel] [PATCH 2/7] lavc: Add hardware config metadata for decoders supporting hardware output

On Wed, 4 Oct 2017 23:04:04 +0100 Mark Thompson <s...@jkqxz.net> wrote: > On 04/10/17 09:54, wm4 wrote: > > On Wed, 4 Oct 2017 09:07:11 +0100 > > Mark Thompson <s...@jkqxz.net> wrote: > > > >> --- > >> libavcodec/h263dec.c |

Re: [libav-devel] [PATCH 7/7] lavc: Deprecate av_hwaccel_next()

On Wed, 4 Oct 2017 09:07:16 +0100 Mark Thompson wrote: > --- > libavcodec/avcodec.h | 6 ++ > libavcodec/decode.c | 2 +- > libavcodec/internal.h | 2 ++ > libavcodec/utils.c| 9 - > libavcodec/version.h | 3 +++ > 5 files changed, 20 insertions(+), 2

Re: [libav-devel] [PATCH 2/7] lavc: Add hardware config metadata for decoders supporting hardware output

On Wed, 4 Oct 2017 09:07:11 +0100 Mark Thompson wrote: > --- > libavcodec/h263dec.c | 10 ++ > libavcodec/h264dec.c | 19 +++ > libavcodec/hevcdec.c | 19 +++ > libavcodec/hwaccel.h | 27 +++

Re: [libav-devel] [PATCH 1/7] lavc: Add codec metadata to indicate hardware support

On Wed, 4 Oct 2017 09:07:10 +0100 Mark Thompson wrote: > --- > doc/APIchanges | 3 +++ > libavcodec/avcodec.h | 74 > > libavcodec/utils.c | 11 > 3 files changed, 88 insertions(+) > > diff --git

Re: [libav-devel] [PATCH] stereo3d: Support view type for frame sequence type

On Tue, 3 Oct 2017 09:26:39 -0400 Vittorio Giovara wrote: > Implement detection in h264 and hevc and insertion in framepack filter. > > Signed-off-by: Vittorio Giovara > --- > doc/APIchanges | 3 +++ > libavcodec/h264_sei.c

[libav-devel] [PATCH v2] lavc: external hardware frame pool initialization

From: wm4 <nfx...@googlemail.com> This adds a new API, which allows the API user to query the required AVHWFramesContext parameters. This also reduces code duplication across the hwaccels by introducing ff_decode_get_hw_frames_ctx(), which uses the new API function. It takes care of initia

[libav-devel] [PATCH] lavc: external hardware frame pool initialization

From: wm4 <nfx...@googlemail.com> This adds a new API, which allows the API user to query the required AVHWFramesContext parameters. This also reduces code duplication across the hwaccels by introducing ff_decode_get_hw_frames_ctx(), which uses the new API function. TODO: - reindent that

[libav-devel] [PATCH] [RFC] lavc: external hardware frame pool initialization, take 1246

From: wm4 <nfx...@googlemail.com> I feel like this has been beaten to death, but let's do it one more time. No code, this is just about the API itself. I also found a way to make one of Mark T.'s RFCs do what I want, so another proposal is included in the doxygen comments. --- liba

Re: [libav-devel] [PATCH] h264_sei: handle stereoscopy frame sequential flags

On Thu, 21 Sep 2017 19:15:37 +0200 Vittorio Giovara wrote: > On Thu, Sep 21, 2017 at 5:40 PM, Steve Lhomme wrote: > > > On Thu, Sep 21, 2017 at 4:58 PM, Vittorio Giovara > > wrote: > > > On Thu, Sep 21, 2017 at 4:03

Re: [libav-devel] [PATCH] pixdesc: Add API to map color property name to enum value

On Wed, 20 Sep 2017 13:33:13 +0200 Vittorio Giovara wrote: > Signed-off-by: Vittorio Giovara > --- > TODO: version bump, APIdoc entry. > Vittorio > Suggestion: create a table with int/string pairs, and a shared lookup function, so that

Re: [libav-devel] [PATCH 1/6] lavc: Add codec metadata to indicate hardware support

On Fri, 8 Sep 2017 10:16:51 +0200 Hendrik Leppkes wrote: > On Fri, Sep 8, 2017 at 6:28 AM, Luca Barbato wrote: > > On 07/09/2017 21:49, Mark Thompson wrote: > >> > >> + * The array is terminated by a configuration with a pix_fmt of > >> + *

Re: [libav-devel] [PATCH 1/6] lavc: Add codec metadata to indicate hardware support

On Thu, 7 Sep 2017 20:49:04 +0100 Mark Thompson wrote: > --- > (Also version bump.) > > Written intending to also be useful for encoders, but there won't actually be > any implementations. > > > doc/APIchanges | 3 +++ > libavcodec/avcodec.h | 69 >

Re: [libav-devel] [PATCH 11/14] lavc/vaapi: Support context reuse

On Thu, 7 Sep 2017 21:04:16 +0100 Mark Thompson <s...@jkqxz.net> wrote: > On 06/09/17 21:28, wm4 wrote: > > On Wed, 6 Sep 2017 21:07:53 +0100 > > Mark Thompson <s...@jkqxz.net> wrote: > > > >> On 06/09/17 17:27, wm4 wrote: > >>> On

Re: [libav-devel] [PATCH 11/14] lavc/vaapi: Support context reuse

On Wed, 6 Sep 2017 21:07:53 +0100 Mark Thompson <s...@jkqxz.net> wrote: > On 06/09/17 17:27, wm4 wrote: > > On Wed, 6 Sep 2017 16:49:11 +0100 > > Mark Thompson <s...@jkqxz.net> wrote: > > > >> On 06/09/17 15:33, wm4 wrote: > >>> On

Re: [libav-devel] [PATCH 12/14] lavc: Add codec metadata to indicate hardware support

On Wed, 6 Sep 2017 20:18:19 +0100 Mark Thompson <s...@jkqxz.net> wrote: > On 06/09/17 19:14, wm4 wrote: > > On Wed, 6 Sep 2017 18:55:46 +0100 > > Mark Thompson <s...@jkqxz.net> wrote: > > > >> On 06/09/17 17:29, wm4 wrote: > >>> On

Re: [libav-devel] [PATCH 12/14] lavc: Add codec metadata to indicate hardware support

On Wed, 6 Sep 2017 18:55:46 +0100 Mark Thompson <s...@jkqxz.net> wrote: > On 06/09/17 17:29, wm4 wrote: > > On Wed, 6 Sep 2017 16:53:04 +0100 > > Mark Thompson <s...@jkqxz.net> wrote: > > > >> On 06/09/17 15:37, wm4 wrote: > >>> On

Re: [libav-devel] [PATCH 12/14] lavc: Add codec metadata to indicate hardware support

On Wed, 6 Sep 2017 16:53:04 +0100 Mark Thompson <s...@jkqxz.net> wrote: > On 06/09/17 15:37, wm4 wrote: > > On Tue, 5 Sep 2017 23:59:31 +0100 > > Mark Thompson <s...@jkqxz.net> wrote: > > > >> --- > >> doc/APIcha

Re: [libav-devel] [PATCH 11/14] lavc/vaapi: Support context reuse

On Wed, 6 Sep 2017 16:49:11 +0100 Mark Thompson <s...@jkqxz.net> wrote: > On 06/09/17 15:33, wm4 wrote: > > On Tue, 5 Sep 2017 23:59:30 +0100 > > Mark Thompson <s...@jkqxz.net> wrote: > > > >> --- > >> Saves the VA config, the frame pool, an

Re: [libav-devel] [PATCH 12/14] lavc: Add codec metadata to indicate hardware support

On Tue, 5 Sep 2017 23:59:31 +0100 Mark Thompson wrote: > --- > doc/APIchanges | 3 +++ > libavcodec/avcodec.h | 23 +++ > 2 files changed, 26 insertions(+) > > diff --git a/doc/APIchanges b/doc/APIchanges > index 6f70f3c96..f21dc4db0 100644 > ---

Re: [libav-devel] [PATCH 11/14] lavc/vaapi: Support context reuse

On Tue, 5 Sep 2017 23:59:30 +0100 Mark Thompson wrote: > --- > Saves the VA config, the frame pool, and the VA context (in that order). The > device reference is held so that freeing the persistent data is possible (the > transient context is already gone when it happens). >

Re: [libav-devel] [PATCH 03/14] lavc/vaapi: Support external hardware frame pool initialisation

On Tue, 5 Sep 2017 23:59:22 +0100 Mark Thompson wrote: > --- > libavcodec/vaapi_decode.c | 8 > 1 file changed, 8 insertions(+) > > diff --git a/libavcodec/vaapi_decode.c b/libavcodec/vaapi_decode.c > index a63c4c62e..847db1a42 100644 > --- a/libavcodec/vaapi_decode.c

Re: [libav-devel] [PATCH] cpu: split flag checks per arch in av_cpu_max_align()

On Mon, 28 Aug 2017 12:53:09 -0300 James Almer <jamr...@gmail.com> wrote: > On 8/28/2017 12:08 PM, wm4 wrote: > > On Mon, 28 Aug 2017 11:52:52 -0300 > > James Almer <jamr...@gmail.com> wrote: > > > >> AV_CPU_FLAG_MMX == AV_CPU_FLAG_ARMV6 == AV_

Re: [libav-devel] [PATCH] cpu: split flag checks per arch in av_cpu_max_align()

On Mon, 28 Aug 2017 11:52:52 -0300 James Almer wrote: > AV_CPU_FLAG_MMX == AV_CPU_FLAG_ARMV6 == AV_CPU_FLAG_ALTIVEC > AV_CPU_FLAG_3DNOWEXT == AV_CPU_FLAG_NEON > AV_CPU_FLAG_SSE == AV_CPU_FLAG_VFP > > Signed-off-by: James Almer > --- >

Re: [libav-devel] [PATCH 1/5] msvc: Properly specify dllexport for data symbols shared across dll boundaries

On Fri, 25 Aug 2017 10:46:40 +0300 Martin Storsjö wrote: > We currently only have exported data symbols within libavcodec, but > the concept is easy to extend to other libraries if necessary. > The attribute declaration needs to be in a private header though, > since we can't

Re: [libav-devel] [PATCH] configure: Include d3d11va_extralibs in libavutil

On Thu, 24 Aug 2017 22:20:19 +0300 Martin Storsjö wrote: > This fixes shared WinRT/UWP builds with d3d11va enabled. > --- > configure | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/configure b/configure > index 3e5784f..6bbde1e 100755 > ---

Re: [libav-devel] [PATCH] lavf: make avio_read_partial() public

On Fri, 18 Aug 2017 15:22:28 +0200 Anton Khirnov <an...@khirnov.net> wrote: > Quoting wm4 (2017-08-18 14:44:45) > > On Fri, 18 Aug 2017 15:40:32 +0300 (EEST) > > Martin Storsjö <mar...@martin.st> wrote: > > > > > On Fri, 18 Aug 2017, Anton Khirnov wr

Re: [libav-devel] [PATCH] lavf: make avio_read_partial() public

On Fri, 18 Aug 2017 15:40:32 +0300 (EEST) Martin Storsjö <mar...@martin.st> wrote: > On Fri, 18 Aug 2017, Anton Khirnov wrote: > > > Quoting wm4 (2017-08-17 15:01:44) > >> Main use-case is proxying avio through a foreign I/O layer and a custom > >>

[libav-devel] [PATCH] lavf: make avio_read_partial() public

Main use-case is proxying avio through a foreign I/O layer and a custom AVIO context, without losing latency and performance characteristics. --- doc/APIchanges | 3 +++ libavformat/avio.h | 9 + libavformat/avio_internal.h | 8 libavformat/aviobuf.c |

Re: [libav-devel] [PATCH 1/2] libavfilter/overlay_qsv: Add QSV overlay vpp filter

On Mon, 31 Jul 2017 09:25:08 +0800 "Huang, Zhengxu" wrote: > Wasn't the plan to use slightly more portable APIs like OpenCL instead for such things? ___ libav-devel mailing list libav-devel@libav.org

Re: [libav-devel] [PATCH 10/10] RFC: generic hwaccel everywhere

On Sat, 5 Aug 2017 23:53:11 +0100 Mark Thompson wrote: > --- > This is several patches squashed together to invite thoughts. > > The idea here is that we add a new array of possible hardware configurations > to codec definitions, expressed as a hardware device type and the

Re: [libav-devel] [PATCH 06/10] lavfi: Add support for modifying hardware frame pool sizes

On Sat, 5 Aug 2017 23:53:07 +0100 Mark Thompson wrote: > AVFilterContext.extra_hw_frames functions identically to the field of > the same name in AVCodecContext. > --- > Implemented in such a way that an init_hw_frames callback could be added here > as well, if anyone had a

Re: [libav-devel] [PATCH 01/10] lavc: Add support for external hardware frame pool initialisation

VA. (Suggested by > wm4 <nfx...@googlemail.com>). > > Also adds a field extra_hw_frames, which supports simple cases where the > only modification to the default parameters required is to increase the > size of a fixed-size pool. > --- > As discussed quite a while ago

[libav-devel] [PATCH v3 1/2] lavc, lavu: move frame cropping to a convenience function

--- doc/APIchanges | 3 ++ libavcodec/decode.c | 89 ++ libavutil/frame.c | 100 libavutil/frame.h | 34 ++ libavutil/version.h | 2 +- 5 files changed, 140

[libav-devel] [PATCH v3 2/2] imgutils: add function to clear an image to black

Black isn't always just memset(ptr, 0, size). Limited YUV in particular requires relatively non-obvious values, and filling a frame with repeating 0 bytes is disallowed in some contexts. With component sizes larger than 8 or packed YUV, this can become relatively complicated. So having a generic

Re: [libav-devel] [PATCH v2] lavc, lavu: move frame cropping to a convenience function

On Fri, 21 Jul 2017 23:02:12 +0200 Anton Khirnov <an...@khirnov.net> wrote: > Quoting wm4 (2017-07-21 22:56:43) > > On Fri, 21 Jul 2017 22:32:43 +0200 > > Anton Khirnov <an...@khirnov.net> wrote: > > > > > Quoting wm4 (2017-07-12 17:02:49) > >

Re: [libav-devel] [PATCH v2] lavc, lavu: move frame cropping to a convenience function

On Fri, 21 Jul 2017 22:32:43 +0200 Anton Khirnov <an...@khirnov.net> wrote: > Quoting wm4 (2017-07-12 17:02:49) > > +int av_frame_apply_cropping(AVFrame *frame, int flags) > > +{ > > +const AVPixFmtDescriptor *desc; > > +size_t offsets[4]; > > +i

Re: [libav-devel] [PATCH] lavf: allow avformat_close_input() with NULL

On Fri, 21 Jul 2017 22:09:03 +0200 Anton Khirnov <an...@khirnov.net> wrote: > Quoting wm4 (2017-07-16 12:43:09) > > Behaves more like FFmpeg, makes some API users not crash on exit. > > --- > > libavformat/utils.c | 7 ++- > > 1 file changed, 6 insertion

Re: [libav-devel] [PATCH] png: Report more details regarding unsupported pixel formats

On Sun, 16 Jul 2017 14:27:50 +0200 Luca Barbato <lu_z...@gentoo.org> wrote: > On 7/16/17 2:12 PM, wm4 wrote: > > On Sun, 16 Jul 2017 13:46:19 +0200 > > Luca Barbato <lu_z...@gentoo.org> wrote: > > > >> --- > >> libavcodec/pngdec.c | 2 ++ &

Re: [libav-devel] [PATCH] png: Report more details regarding unsupported pixel formats

On Sun, 16 Jul 2017 13:46:19 +0200 Luca Barbato wrote: > --- > libavcodec/pngdec.c | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/libavcodec/pngdec.c b/libavcodec/pngdec.c > index 927248f2e3..6be463344a 100644 > --- a/libavcodec/pngdec.c > +++

[libav-devel] [PATCH] lavf: allow avformat_close_input() with NULL

Behaves more like FFmpeg, makes some API users not crash on exit. --- libavformat/utils.c | 7 ++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/libavformat/utils.c b/libavformat/utils.c index eaba473914..24a4335016 100644 --- a/libavformat/utils.c +++ b/libavformat/utils.c @@

[libav-devel] [PATCH v2] imgutils: add function to clear an image to black

Black isn't always just memset(ptr, 0, size). Limited YUV in particular requires relatively non-obvious values, and filling a frame with repeating 0 bytes is disallowed in some contexts. With component sizes larger than 8 or packed YUV, this can become relatively complicated. So having a generic

Re: [libav-devel] [PATCH] imgutils: add function to clear an image to black

On Sun, 16 Jul 2017 01:08:37 +0200 Luca Barbato <lu_z...@gentoo.org> wrote: > On 7/14/17 7:14 PM, wm4 wrote: > > +} else if (clear_size == 4) { > > +uint32_t val = AV_RN32(clear); > > +for (; dst_size >= 4; dst_size -= 4) { >

[libav-devel] [PATCH] imgutils: add function to clear an image to black

Black isn't always just memset(ptr, 0, size). Limited YUV in particular requires relatively non-obvious values, and filling a frame with repeating 0 bytes is disallowed in some contexts. With component sizes larger than 8 or packed YUV, this can become relatively complicated. So having a generic

[libav-devel] [PATCH v2] lavc, lavu: move frame cropping to a convenience function

TODO: APIchanges entry, version bump. --- Now with flags instead of a bool parameter. --- libavcodec/decode.c | 89 ++--- libavutil/frame.c | 101 libavutil/frame.h | 32 + 3 files

[libav-devel] [PATCH] lavc, lavu: move frame cropping to a convenience function

TODO: APIchanges entry, version bump. --- libavcodec/decode.c | 88 + libavutil/frame.c | 101 libavutil/frame.h | 20 +++ 3 files changed, 122 insertions(+), 87 deletions(-) diff --git

[libav-devel] [PATCH] dxva: DXVA2_ModeHEVC_VLD_Main10 does not support Main

This mode apparently does not support decoding of HEVC Main (8 bit). With D3D11 and Intel drivers on Windows 10 I get green corruption, while using DXVA2_ModeHEVC_VLD_Main works. --- libavcodec/dxva2.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/libavcodec/dxva2.c

Re: [libav-devel] [PATCH] Add a new channel layout API

On Fri, 30 Jun 2017 12:51:16 -0400 Vittorio Giovara <vittorio.giov...@gmail.com> wrote: > On Fri, Jun 30, 2017 at 4:38 AM, wm4 <nfx...@googlemail.com> wrote: > > On Thu, 29 Jun 2017 17:28:51 -0400 > > Vittorio Giovara <vittorio.giov...@gmail.com> wrot

Re: [libav-devel] [PATCH 2/2] os_support: Use HAVE_UWP instead of manually checking WINAPI_FAMILY

On Wed, 5 Jul 2017 12:42:22 +0300 Martin Storsjö wrote: > --- > libavformat/os_support.h | 14 +- > 1 file changed, 1 insertion(+), 13 deletions(-) > > diff --git a/libavformat/os_support.h b/libavformat/os_support.h > index 965e16f..55c2fdb 100644 > ---

Re: [libav-devel] [PATCH 1/2] d3d11va: Check WINAPI_FAMILY instead of HAVE_LOADLIBRARY

On Wed, 5 Jul 2017 12:42:21 +0300 Martin Storsjö wrote: > If using the winstore compat library, a fallback LoadLibrary > function does exist, that only calls LoadPackagedLibrary though > (which doesn't work for dynamically loading d3d11 DLLs). > > Therefore explicitly check

Re: [libav-devel] [PATCH] d3d11va: Check WINAPI_FAMILY instead of HAVE_LOADLIBRARY

On Tue, 4 Jul 2017 22:57:41 +0300 (EEST) Martin Storsjö <mar...@martin.st> wrote: > On Tue, 4 Jul 2017, wm4 wrote: > > > On Tue, 4 Jul 2017 22:18:21 +0300 > > Martin Storsjö <mar...@martin.st> wrote: > > > >> If using the winstore compat libra

  1   2   3   4   5   6   7   8   9   >