[libav-devel] [PATCH 1/2] apetag: fix flag value to signal footer presence

According to the spec[1], a value of 0 means the footer is present and a value of 1 means it's absent, the exact opposite of header presence flag where 1 means present and 0 absent. The reason for this is compatibility with APEv1 tags, where there's no header, footer presence was mandatory for all

[libav-devel] [PATCH 2/2] apetag: account for header size if present when returning the start position

The size field in the header/footer accounts for the entire APE tag structure except the 32 bytes from header, for compatibility with APEv1. Signed-off-by: James Almer --- libavformat/apetag.c | 7 ++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git

[libav-devel] [PATCH] h264: Correctly initialize interlaced_frame if tff is set

In particular cases, it is possible to initialize top_field_first but not interlaced_frame. Make sure to correctly tag a frame as interlaced when this happens. Signed-off-by: Vittorio Giovara --- libavcodec/h264_slice.c | 10 ++ 1 file changed, 6

Re: [libav-devel] [PATCH 5/5] mkv: Export bounds and padding from spherical metadata

On 2/10/2017 6:37 PM, James Almer wrote: > On 2/10/2017 6:08 PM, Vittorio Giovara wrote: >> --- >> libavformat/matroskadec.c | 34 +- >> 1 file changed, 33 insertions(+), 1 deletion(-) >> >> diff --git a/libavformat/matroskadec.c b/libavformat/matroskadec.c >>

Re: [libav-devel] [PATCH 5/5] mkv: Export bounds and padding from spherical metadata

On 2/10/2017 6:08 PM, Vittorio Giovara wrote: > --- > libavformat/matroskadec.c | 34 +- > 1 file changed, 33 insertions(+), 1 deletion(-) > > diff --git a/libavformat/matroskadec.c b/libavformat/matroskadec.c > index a44ceeb..ebfd414 100644 > ---

Re: [libav-devel] [PATCH] aarch64: vp9itxfm: Avoid reloading the idct32 coefficients

On 2017-02-09 13:27:04 +0200, Martin Storsjö wrote: > The idct32x32 function actually backed up and restored d8-d15 even ... pushed onto the stack ... is imo clearer even though there are no explicit push/pop instructions > though it didn't clobber them; there are plenty of registers that > can

[libav-devel] [PATCH 1/5] mov: Fix spherical metadata_source parsing

From: Aaron Colwell Signed-off-by: James Almer --- libavformat/mov.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/libavformat/mov.c b/libavformat/mov.c index 2810960..4a6f9c0 100644 --- a/libavformat/mov.c +++

[libav-devel] [PATCH 5/5] mkv: Export bounds and padding from spherical metadata

--- libavformat/matroskadec.c | 34 +- 1 file changed, 33 insertions(+), 1 deletion(-) diff --git a/libavformat/matroskadec.c b/libavformat/matroskadec.c index a44ceeb..ebfd414 100644 --- a/libavformat/matroskadec.c +++ b/libavformat/matroskadec.c @@ -1601,17

[libav-devel] [PATCH 4/5] mov: Export bounds and padding from spherical metadata

Update the fate test as needed. --- libavformat/mov.c| 46 +++- tests/fate/mov.mak | 2 +- tests/ref/fate/mov-spherical | 6 +- 3 files changed, 51 insertions(+), 3 deletions(-) diff --git a/libavformat/mov.c b/libavformat/mov.c

[libav-devel] [PATCH 2/5] matroskadec: add support for Spherical Video elements

From: James Almer Signed-off-by: James Almer Signed-off-by: Vittorio Giovara --- libavformat/matroska.h| 14 +++ libavformat/matroskadec.c | 63 +++ 2 files changed, 77

[libav-devel] [PATCH 3/5] spherical: Add tiled equirectangular type and projection-specific properties

Signed-off-by: Vittorio Giovara --- avprobe.c | 15 +++--- doc/APIchanges| 5 + libavformat/dump.c| 10 + libavutil/spherical.h | 56 +++ libavutil/version.h | 2 +- 5

Re: [libav-devel] [PATCH 6/6] arm: vp9lpf: Implement the mix2_44 function with one single filter pass

On 2017-01-15 22:55:52 +0200, Martin Storsjö wrote: > For this case, with 8 inputs but only changing 4 of them, we can fit > all 16 input pixels into a q register, and still have enough temporary > registers for doing the loop filter. > > The wd=8 filters would require too many temporary

Re: [libav-devel] [PATCH 5/6] aarch64: vp9lpf: Interleave the start of flat8in into the calculation above

On 2017-01-15 22:55:51 +0200, Martin Storsjö wrote: > --- > libavcodec/aarch64/vp9lpf_neon.S | 16 +--- > 1 file changed, 13 insertions(+), 3 deletions(-) > > diff --git a/libavcodec/aarch64/vp9lpf_neon.S > b/libavcodec/aarch64/vp9lpf_neon.S > index 4553173..3894307 100644 > ---

Re: [libav-devel] [PATCH 4/6] arm: vp9lpf: Interleave the start of flat8in into the calculation above

On 2017-01-15 22:55:50 +0200, Martin Storsjö wrote: > This adds lots of extra .ifs, but speeds it up by a couple cycles, > by avoiding stalls. > --- > libavcodec/arm/vp9lpf_neon.S | 8 ++-- > 1 file changed, 6 insertions(+), 2 deletions(-) > > diff --git a/libavcodec/arm/vp9lpf_neon.S

Re: [libav-devel] [PATCH 3/6] arm: vp9lpf: Use orrs instead of orr+cmp

On 2017-01-15 22:55:49 +0200, Martin Storsjö wrote: > --- > libavcodec/arm/vp9lpf_neon.S | 12 > 1 file changed, 4 insertions(+), 8 deletions(-) > > diff --git a/libavcodec/arm/vp9lpf_neon.S b/libavcodec/arm/vp9lpf_neon.S > index 5e154f6..9be4cef 100644 > ---

Re: [libav-devel] [PATCH 2/6] arm/aarch64: vp9lpf: Keep the comparison to E within 8 bit

On 2017-01-15 22:55:48 +0200, Martin Storsjö wrote: > The theoretical maximum value of E is 193, so we can just > saturate the addition to 255. > > Before: Cortex A7 A8 A9 A53 A53/AArch64 > vp9_loop_filter_v_4_8_neon: 143.0 127.7 114.888.0

Re: [libav-devel] [PATCH 1/6] arm/aarch64: vp9lpf: Calculate !hev directly

On 2017-01-15 22:55:47 +0200, Martin Storsjö wrote: > Previously we first calculated hev, and then negated it. > > Since we were able to schedule the negation in the middle > of another calculation, we don't see any gain in all cases. > > Before: Cortex A7 A8 A9

Re: [libav-devel] [PATCH 1/2] arm: vp9itxfm: Optimize 16x16 and 32x32 idct dc by unrolling

On 2017-01-05 09:35:36 +0200, Martin Storsjö wrote: > This work is sponsored by, and copyright, Google. > > Before:Cortex A7 A8 A9 A53 > vp9_inv_dct_dct_16x16_sub1_add_neon: 273.0 189.5 211.7 235.8 > vp9_inv_dct_dct_32x32_sub1_add_neon: 752.0

Re: [libav-devel] [PATCH 6/6] aarch64: vp9mc: Calculate less unused data in the 4 pixel wide horizontal filter

On 2017-01-02 14:17:56 +0200, Martin Storsjö wrote: > No measured speedup on an Cortex A53, but other cores might benefit. A little surprised that it didn't made a difference on the cortex-a53 since certain sites reported the NEON unit isn't fully 128-bit wide, So unlikely that it makes a

Re: [libav-devel] [PATCH 4/6] aarch64: vp9mc: Simplify the extmla macro parameters

On 2017-01-02 14:17:54 +0200, Martin Storsjö wrote: > Fold the field lengths into the macro. > > This makes the macro invocations much more readable, when the > lines are shorter. > > This also makes it easier to use only half the registers within > the macro. > --- >

Re: [libav-devel] [PATCH 5/6] arm: vp9mc: Calculate less unused data in the 4 pixel wide horizontal filter

On 2017-01-02 14:17:55 +0200, Martin Storsjö wrote: > Before:Cortex A7 A8 A9 A53 > vp9_put_8tap_smooth_4h_neon: 378.1 273.2 340.7 229.5 > After: > vp9_put_8tap_smooth_4h_neon: 352.1 222.2 290.5 229.5 > --- > libavcodec/arm/vp9mc_neon.S | 33

[libav-devel] [PATCH] configure: Move up the avbuild directory creation

The early check for inconsistent in-source vs out-of-source build would not be able to generate a config.log otherwise. --- configure | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/configure b/configure index 9ebc3bf..69f5863 100755 --- a/configure +++ b/configure @@

[libav-devel] [PATCH 2/2] build: Move cli tool sources to a separate subdirectory

This unclutters the top-level directory and groups related files together. --- Got rid of some code duplication that was still present in the previous version. Makefile | 49 -- avtools/Makefile | 44

[libav-devel] [PATCH 1/2] build: Drop leftover LIB_EXAMPLES reference

--- doc/Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/Makefile b/doc/Makefile index bda8153..bd5c2e4 100644 --- a/doc/Makefile +++ b/doc/Makefile @@ -73,7 +73,7 @@ $(DOCS) doc/doxy/html: | doc/ $(DOC_EXAMPLES:%$(EXESUF)=%.o): | doc/examples OBJDIRS +=

[libav-devel] [PATCH 2/2] lavc: vdpau: implement AV_HWACCEL_FLAG_CACHE_FRAMES

--- libavcodec/vdpau.c | 47 +++ 1 file changed, 35 insertions(+), 12 deletions(-) diff --git a/libavcodec/vdpau.c b/libavcodec/vdpau.c index 68d0813f65..a84ff81d7d 100644 --- a/libavcodec/vdpau.c +++ b/libavcodec/vdpau.c @@ -152,22 +152,45 @@ int

[libav-devel] [PATCH 1/2] lavc: allow reuse of hwaccel frames contexts when parameters don't change

From: Mark Thompson Basically a RFC, based on Mark Thompson's patch. Adds the AV_HWACCEL_FLAG_CACHE_FRAMES flag. Requires a few other ML patches to be applied. Does the cached context need to be synced in update_context_from_thread? --- libavcodec/avcodec.h | 7 +++

Re: [libav-devel] [PATCH] hwcontext_dxva2: support D3D9Ex

On Fri, Feb 10, 2017 at 12:17 PM, wm4 wrote: > D3D9Ex uses different driver paths. This helps with "headless" > configurations when no user logs in. Plain D3D9 device creation will > fail if no user is logged in, while it works with D3D9Ex. > --- >

[libav-devel] [PATCH] hwcontext_dxva2: support D3D9Ex

D3D9Ex uses different driver paths. This helps with "headless" configurations when no user logs in. Plain D3D9 device creation will fail if no user is logged in, while it works with D3D9Ex. --- libavutil/hwcontext_dxva2.c | 117 1 file changed, 87

[libav-devel] [PATCH 3/3] avconv: use new vdpau decoding API

--- actually not fully sure how to use hw_device_ctx here, and obviously it violates the API. but for now it's modeled after the preliminary avconv_vaapi patch for the same thing. --- avconv_vdpau.c | 39 +-- 1 file changed, 1 insertion(+), 38 deletions(-)

[libav-devel] [PATCH 1/3] lavc: Add hwaccel_flags field to AVCodecContext

This "reuses" the flags introduced for the av_vdpau_bind_context() API function, and makes them available to all hwaccels. This does not affect the current vdpau API, as av_vdpau_bind_context() should obviously override the AVCodecContext.hwaccel_flags flags for the sake of compatibility. ---

[libav-devel] [PATCH 2/3] lavc: vdpau: add support for new hw_frames_ctx and hw_device_ctx API

This supports retrieving the device from a provided hw_frames_ctx, and automatically creating a hw_frames_ctx if hw_device_ctx is set. The old API is not deprecated yet. The user can still use av_vdpau_bind_context() (with or without setting hw_frames_ctx), or use the API before that by

Re: [libav-devel] [PATCH 5/5] vf_interlace/x86: process only one block per iteration

Quoting Anton Khirnov (2017-02-08 11:51:00) > Nothing guarantees that the line is large enough for two blocks, so > current code may result in invalid memory access. This change makes the > function ~5% slower, but since this is a highly obscure filter that > nobody should use, its performance is

Re: [libav-devel] [PATCH] h264dec: fix dropped initial SEI recovery point

Quoting John Stebbins (2017-02-08 22:52:28) > --- > libavcodec/h264dec.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/libavcodec/h264dec.c b/libavcodec/h264dec.c > index 5137039..6d7aa7b 100644 > --- a/libavcodec/h264dec.c > +++ b/libavcodec/h264dec.c > @@ -452,7

Re: [libav-devel] [PATCH] hlsenc: Correctly write down all 16 bytes in hex

Quoting Luca Barbato (2017-02-09 23:27:41) > --- > libavformat/hlsenc.c | 11 ++- > 1 file changed, 6 insertions(+), 5 deletions(-) > > diff --git a/libavformat/hlsenc.c b/libavformat/hlsenc.c > index 05c9adb..7aef02b 100644 > --- a/libavformat/hlsenc.c > +++ b/libavformat/hlsenc.c > @@

Re: [libav-devel] [PATCH 1/6] lavc: Add device context field to AVCodecContext

Quoting Mark Thompson (2017-02-02 13:48:47) > For use by codec implementations which can allocate frames internally. > --- > Go back to setting hw_device_ctx before avcodec_open2() only. Clarify > interaction with hw_frames_ctx, including the possibility that a device is > required for

Re: [libav-devel] [PATCH] travis: Ignore the filter-fade test

Quoting Luca Barbato (2017-02-10 02:30:54) > On 26/01/2017 12:42, Luca Barbato wrote: > > It glitches with the stale travis linux target. > > --- > > > > .travis.yml | 2 +- > > 1 file changed, 1 insertion(+), 1 deletion(-) > > > > diff --git a/.travis.yml b/.travis.yml > > index