On 08/07/16 22:22, Martin Storsjö wrote:
> ---
> libavcodec/libopenh264dec.c | 2 ++
> libavcodec/libopenh264enc.c | 26 --
> 2 files changed, 26 insertions(+), 2 deletions(-)
OK.
___
libav-devel mailing list
libav-devel@libav.
---
libavcodec/libopenh264dec.c | 2 ++
libavcodec/libopenh264enc.c | 26 --
2 files changed, 26 insertions(+), 2 deletions(-)
diff --git a/libavcodec/libopenh264dec.c b/libavcodec/libopenh264dec.c
index 2e8f52a..cdbea7b 100644
--- a/libavcodec/libopenh264dec.c
+++ b/liba
On Fri, 8 Jul 2016, Ronald S. Bultje wrote:
Hi,
On Thu, Jul 7, 2016 at 7:08 PM, Janne Grunau wrote:
+#define SRC_BUF_STRIDE 32
+#define SRC_BUF_SIZE ((size + 5) * SRC_BUF_STRIDE)
+// The 2 * stride + 2 offset is necessary to avoid reading out of
bounds,
that sounds a little misleading. jus
On Fri, Jul 8, 2016 at 3:47 AM, Janne Grunau wrote:
> Fixes a regression in ca2f19b9cc3 with some mov/mp4 files. The files have
> several NAL units in the supposed single NAL unit after the size field.
> Annex B start code prefixes are used to separate them. The first NAL unit
> is correctly parse
My fellow members of the libav multimedia community,
As it is now customary, I'd like to invite you to VideoLAN Dev Days
2016, on the 1st week-end of September: 2-4 September 2016, in Berlin.
This 8th edition of VDD is a bit special, as it collocated within QtCon,
a larger open source conferen
Hi,
On Thu, Jul 7, 2016 at 7:08 PM, Janne Grunau wrote:
> > +#define SRC_BUF_STRIDE 32
> > +#define SRC_BUF_SIZE ((size + 5) * SRC_BUF_STRIDE)
> > +// The 2 * stride + 2 offset is necessary to avoid reading out of
> bounds,
>
> that sounds a little misleading. just stating that the mc sub pixel
On Fri, 8 Jul 2016, Janne Grunau wrote:
On 2016-07-05 00:26:28 +0300, Martin Storsjö wrote:
The tests are inspired by similar tests for vp9 by
Ronald Bultje.
---
Amended the includes as suggested by Diego, added missing
tests for the simple variant of loop filters.
---
tests/checkasm/Makefile
On 08/07/16 09:47, Janne Grunau wrote:
> Fixes a regression in ca2f19b9cc3 with some mov/mp4 files. The files have
> several NAL units in the supposed single NAL unit after the size field.
> Annex B start code prefixes are used to separate them. The first NAL unit
> is correctly parsed but the buff
Fixes a regression in ca2f19b9cc3 with some mov/mp4 files. The files have
several NAL units in the supposed single NAL unit after the size field.
Annex B start code prefixes are used to separate them. The first NAL unit
is correctly parsed but the buffer does not point to the next size field.
Inste
