On 23 February 2017 at 17:12, Damien Riegel <
damien.rie...@savoirfairelinux.com> wrote:
> On Wed, Feb 22, 2017 at 09:33:03PM +, Rostislav Pehlivanov wrote:
> > On 22 February 2017 at 20:18, Damien Riegel <
> > damien.rie...@savoirfairelinux.com> wrote:
> >
> > > On Fri, Feb 17, 2017 at 03:01:
On Fri, Feb 24, 2017 at 02:21:06AM +0100, Carl Eugen Hoyos wrote:
> Hi!
>
> Attached patch fixes two warnings here.
>
> Please comment, Carl Eugen
> utils.c |2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
> 9fc49d14374b7fbfdbb6828fa8a439e884a563e8
> 0001-lavc-utils-Make-second-para
Hello,
Is someone able to take a look at this and accept or reject it -- its
been a few days since I submitted.
Sorry to pester -- thanks in advance.
On Mon, Feb 20, 2017 at 7:48 PM, Micah Galizia wrote:
> Signed-off-by: Micah Galizia
> ---
> libavutil/parseutils.c | 28
Sorry, typo below:
Change -preset medium to -preset slow in ii)
Ganapathy
-Original Message-
From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf Of
Ganapathy Raman Kasi
Sent: Thursday, February 23, 2017 6:01 PM
To: FFmpeg development discussions and patches
Subject: Re
Adding on to the previous mail,
To test this patch, please try :
i) ffmpeg -y -i $INPUT -vcodec h264_nvenc -preset medium $OUT_medium.mp4
ii) ffmpeg -y -i $INPUT -vcodec h264_nvenc -preset medium $OUT_slow.mp4
Without patch : $OUT_medium and $OUT_slow will be binary identical since both
use NV_E
Hi,
qmin and qmax are not necessary for nvenc vbr. Enforcing this constraint,
doesn't allow user to use vbr 2 pass mode (
NV_ENC_PARAMS_RC_2_PASS_VBR) without explicity setting the qmin and qmax
options and reverts to the default vbr mode (
NV_ENC_PARAMS_RC_VBR). If needed user can still set
2017-02-24 1:19 GMT+01:00 Michael Niedermayer :
> The problem is that functions like memcpy dont allow NULL even with
> a size of 0
>
> i can add checks for every memcpy() and any other function that ubsan
> finds if thats preferred or add a av_memcpy() that does allow NULL
No, it's preferable to
Hi!
Attached patch fixes two warnings here.
Please comment, Carl Eugen
From 14a80e57463f43bcdc1ef5d87d2e95dc1bf420bc Mon Sep 17 00:00:00 2001
From: Carl Eugen Hoyos
Date: Fri, 24 Feb 2017 02:18:23 +0100
Subject: [PATCH] lavc/utils: Make second parameter to apply_param_change()
const.
MIME-Versi
2017-02-24 1:55 GMT+01:00 Paul B Mahol :
>> What I meant was:
>> How can I create a mov file with FFmpeg that fails without ignore_editlist?
>> The sample you provided was made with FFmpeg / libavformat.
>
> The sample was only trimmed with FFmpeg. For full samples buy certain
> software.
I unde
On 2/24/17, Carl Eugen Hoyos wrote:
> 2017-02-23 15:18 GMT+01:00 Paul B Mahol :
>> On 2/23/17, Carl Eugen Hoyos wrote:
>>> 2017-02-23 8:00 GMT+01:00 Paul B Mahol :
On 2/23/17, Carl Eugen Hoyos wrote:
> 2017-02-22 14:51 GMT+01:00 Paul B Mahol :
>> On 2/22/17, Paul B Mahol wrote:
>>>
2017-02-23 15:18 GMT+01:00 Paul B Mahol :
> On 2/23/17, Carl Eugen Hoyos wrote:
>> 2017-02-23 8:00 GMT+01:00 Paul B Mahol :
>>> On 2/23/17, Carl Eugen Hoyos wrote:
2017-02-22 14:51 GMT+01:00 Paul B Mahol :
> On 2/22/17, Paul B Mahol wrote:
>> Signed-off-by: Paul B Mahol
>> ---
On Thu, Feb 23, 2017 at 05:53:27PM +0100, wm4 wrote:
> On Thu, 23 Feb 2017 17:12:35 +0100
> Michael Niedermayer wrote:
>
> > On Thu, Feb 23, 2017 at 03:26:22PM +0100, wm4 wrote:
> > > On Thu, 23 Feb 2017 15:19:31 +0100
> > > Michael Niedermayer wrote:
> > >
> > > > The size 0 special case cau
On Thu, 23 Feb 2017, Matthias Hunstock wrote:
Am 23.02.2017 um 17:24 schrieb Marton Balint:
The "@mode" syntax does not work for output devices. Let me add a patch,
I will send it tonight.
Please don't. The @mode syntax is insane. You need a different @mode for
different hardware to get the
On 19/02/17 17:23, Mark Thompson wrote:
> (cherry picked from commit ade370a4d7eab1866b6023c91c135d27c77ca465)
> (cherry picked from commit 2d518aec4c781316092be65893b47922c8f71b67)
> ---
> configure | 1 +
> libavfilter/Makefile | 1 +
> libavfilter/allf
Am 23.02.2017 um 21:58 schrieb wm4:
>> +virtual ULONG STDMETHODCALLTYPE AddRef(void)
>> +virtual ULONG STDMETHODCALLTYPE Release(void)
>> +{
>> +int ret = avpriv_atomic_int_add_and_fetch(&_refs, -1);
>> +if (!ret) {
>> +av_frame_free(&_avframe);
> Wouldn'
On Wed, 22 Feb 2017 23:46:51 +0100
Marton Balint wrote:
> Signed-off-by: Marton Balint
> ---
> libavdevice/decklink_enc.cpp | 78
> +---
> libavdevice/decklink_enc_c.c | 4 +--
> libavdevice/version.h| 4 +--
> 3 files changed, 42 insertions(+)
Am 23.02.2017 um 17:24 schrieb Marton Balint:
>> The "@mode" syntax does not work for output devices. Let me add a patch,
>> I will send it tonight.
>
> Please don't. The @mode syntax is insane. You need a different @mode for
> different hardware to get the same output format. @mode may even be
>
On 21/02/17 17:15, Saverio Blasi wrote:
> Hi all,
>
> We have recently circulated this new iteration (see below) of our work
> towards integrating our HEVC Turing codec within FFMpeg. Assuming that there
> are no more requests for changes, we would like to understand what is the
> timeline for
On Wednesday, February 22, 2017, Przemysław Sobala <
przemyslaw.sob...@gmail.com> wrote:
> From: Przemysław Sobala >
>
> Provides a way to change bandwidth (bitrate) parameter after CRF H.264
> encoding (details: http://ffmpeg.org/pipermail/libav-user/2017-February/
> 010141.html)
>
> Signed-off-b
Am 23.02.17 um 21:00 schrieb Lou Logan:
> On Thu, 23 Feb 2017 20:35:21 +0100, Thilo Borgmann wrote:
>
>> Hi,
>>
>> in the aftermath of ELCE 2016 we recieved a donation of 5 displays
>> from a company.
>
> Forgive my ignorance, but what is a "display"? I'm guessing it's what
> we 'Mericans call a
On 2/23/17, Lou Logan wrote:
> On Thu, 23 Feb 2017 20:35:21 +0100, Thilo Borgmann wrote:
>
>> Hi,
>>
>> in the aftermath of ELCE 2016 we recieved a donation of 5 displays
>> from a company.
>
> Forgive my ignorance, but what is a "display"? I'm guessing it's what
> we 'Mericans call a computer mon
On 11/02/17 22:56, Takayuki 'January June' Suwa wrote:
> From: Takayuki 'January June' Suwa
>
> This adds "-profile[:v] profile_name"-style option.
> ---
> libavcodec/omx.c | 31 +++
> 1 file changed, 31 insertions(+)
>
> diff --git a/libavcodec/omx.c b/libavcodec/om
On Thu, 23 Feb 2017 20:35:21 +0100, Thilo Borgmann wrote:
> Hi,
>
> in the aftermath of ELCE 2016 we recieved a donation of 5 displays
> from a company.
Forgive my ignorance, but what is a "display"? I'm guessing it's what
we 'Mericans call a computer monitor.
___
Hi,
in the aftermath of ELCE 2016 we recieved a donation of 5 displays from a
company. These went to Michael Niedermayer, Carl Eugen Hoyos, Ronald Bultje,
Clement Boesch and myself.
Unfortunately, due to lack of experience with that, I had to pay customs for 4
of 5 of these displays which had
On Thu, Feb 23, 2017 at 05:55:15PM +0100, wm4 wrote:
> On Thu, 23 Feb 2017 17:34:42 +0100
> Michael Niedermayer wrote:
>
> > Rodger Combs will be added to the ffmpeg-security alias when this patch is
> > applied
> >
> > Signed-off-by: Michael Niedermayer
> > ---
> > MAINTAINERS | 2 +-
> > 1
On Wed, Feb 22, 2017 at 09:33:03PM +, Rostislav Pehlivanov wrote:
> On 22 February 2017 at 20:18, Damien Riegel <
> damien.rie...@savoirfairelinux.com> wrote:
>
> > On Fri, Feb 17, 2017 at 03:01:05PM -0500, Damien Riegel wrote:
> > > Hi,
> > >
> > > On Thu, Feb 16, 2017 at 06:19:00PM +, Ro
On Thu, 23 Feb 2017 17:34:42 +0100
Michael Niedermayer wrote:
> Rodger Combs will be added to the ffmpeg-security alias when this patch is
> applied
>
> Signed-off-by: Michael Niedermayer
> ---
> MAINTAINERS | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/MAINTAINERS
On Thu, 23 Feb 2017 17:12:35 +0100
Michael Niedermayer wrote:
> On Thu, Feb 23, 2017 at 03:26:22PM +0100, wm4 wrote:
> > On Thu, 23 Feb 2017 15:19:31 +0100
> > Michael Niedermayer wrote:
> >
> > > The size 0 special case causes side data to be created which is
> > > different and a special ca
On 2/23/17, Michael Niedermayer wrote:
> wm4 will be added to the ffmpeg-security alias when this patch is applied
>
> Signed-off-by: Michael Niedermayer
> ---
> MAINTAINERS | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
wm4 certainly have real name, lgtm anyway
_
On 2/23/17, Michael Niedermayer wrote:
> Rodger Combs will be added to the ffmpeg-security alias when this patch is
> applied
>
> Signed-off-by: Michael Niedermayer
> ---
> MAINTAINERS | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
ok
___
f
On 2/23/17, Michael Niedermayer wrote:
> Signed-off-by: Michael Niedermayer
> ---
> MAINTAINERS | 6 +-
> 1 file changed, 1 insertion(+), 5 deletions(-)
>
lgtm
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinf
wm4 will be added to the ffmpeg-security alias when this patch is applied
Signed-off-by: Michael Niedermayer
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index db5534639b..e39cf88798 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -6
Signed-off-by: Michael Niedermayer
---
MAINTAINERS | 6 +-
1 file changed, 1 insertion(+), 5 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 9c12fecce2..db5534639b 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -60,11 +60,7 @@ mailing lists Baptiste Couduri
Rodger Combs will be added to the ffmpeg-security alias when this patch is
applied
Signed-off-by: Michael Niedermayer
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index e39cf88798..6b17b13187 100644
--- a/MAINTAINERS
+++ b/MAINTAI
On Thu, 23 Feb 2017, Matthias Hunstock wrote:
Am 22.02.2017 um 23:46 schrieb Marton Balint:
diff --git a/doc/outdevs.texi b/doc/outdevs.texi
index e68653f..df41cc8 100644
--- a/doc/outdevs.texi
+++ b/doc/outdevs.texi
@@ -131,8 +131,8 @@ and @code{--extra-ldflags}.
On Windows, you need to run
On Thu, Feb 23, 2017 at 03:26:22PM +0100, wm4 wrote:
> On Thu, 23 Feb 2017 15:19:31 +0100
> Michael Niedermayer wrote:
>
> > The size 0 special case causes side data to be created which is
> > different and a special case if for any reasons size = 0 is passed
> >
> > Fixes: multiple runtime erro
Am 22.02.2017 um 23:46 schrieb Marton Balint:
> diff --git a/doc/outdevs.texi b/doc/outdevs.texi
> index e68653f..df41cc8 100644
> --- a/doc/outdevs.texi
> +++ b/doc/outdevs.texi
> @@ -131,8 +131,8 @@ and @code{--extra-ldflags}.
> On Windows, you need to run the IDL files through @command{widl}.
---
libavcodec/aarch64/Makefile | 2 +
libavcodec/aarch64/idct.h | 28 +++
libavcodec/aarch64/idctdsp_init_aarch64.c | 40
libavcodec/aarch64/simple_idct_neon.S | 362 ++
libavcodec/idctdsp.c | 2 +
libav
Hello,
The following patchset add the ff_simple_idct function neon functions for the
aarch64 platform. It's ported from armv7 simple_idct_neon with some
improvements:
* the source idct blocks are now loaded once and kept in v24-v31
* the source idct blocks are no longer overriden in idct_col4_t
---
libavcodec/tests/aarch64/dct.c | 30 ++
libavcodec/tests/dct.c | 4 +++-
2 files changed, 33 insertions(+), 1 deletion(-)
create mode 100644 libavcodec/tests/aarch64/dct.c
diff --git a/libavcodec/tests/aarch64/dct.c b/libavcodec/tests/aarch64/dct.c
new fi
On Thu, Feb 23, 2017 at 07:57:41AM -0500, Ronald S. Bultje wrote:
> Hi,
>
> On Thu, Feb 23, 2017 at 2:19 AM, wm4 wrote:
>
> > On Wed, 22 Feb 2017 19:16:46 +0100
> > Michael Niedermayer wrote:
> >
> > > This enables the extra error messages in case of DEBUG or high assrtion
> > levels.
> > > Hig
On Thu, 23 Feb 2017 15:19:31 +0100
Michael Niedermayer wrote:
> The size 0 special case causes side data to be created which is
> different and a special case if for any reasons size = 0 is passed
>
> Fixes: multiple runtime error: null pointer passed as argument 1, which is
> declared to never
Fixes: runtime error: shift exponent 34 is too large for 32-bit type 'int'
Fixes: 653/clusterfuzz-testcase-5773837415219200
Signed-off-by: Michael Niedermayer
---
libavcodec/wavpack.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/libavcodec/wavpack.c b/libavcodec/wavpack.c
index 24d57f
There should be no case that needs this and its a potential for
creating corner cases
Signed-off-by: Michael Niedermayer
---
libavutil/frame.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/libavutil/frame.c b/libavutil/frame.c
index 8811dcdcfe..69ee240758 100644
--- a/libavutil/frame.c
+
The size 0 special case causes side data to be created which is
different and a special case if for any reasons size = 0 is passed
Fixes: multiple runtime error: null pointer passed as argument 1, which is
declared to never be null
Fixes: 653/clusterfuzz-testcase-5773837415219200
Found-by: conti
Fixes: 653/clusterfuzz-testcase-5773837415219200
Found-by: continuous fuzzing process
https://github.com/google/oss-fuzz/tree/master/targets/ffmpeg
Signed-off-by: Michael Niedermayer
---
libavcodec/wavpack.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libavcodec/wavpack.c
On 2/23/17, Carl Eugen Hoyos wrote:
> 2017-02-23 8:00 GMT+01:00 Paul B Mahol :
>> On 2/23/17, Carl Eugen Hoyos wrote:
>>> 2017-02-22 14:51 GMT+01:00 Paul B Mahol :
On 2/22/17, Paul B Mahol wrote:
> Signed-off-by: Paul B Mahol
> ---
> libavcodec/dnxhddec.c | 2 +-
> 1 file
2017-02-23 8:00 GMT+01:00 Paul B Mahol :
> On 2/23/17, Carl Eugen Hoyos wrote:
>> 2017-02-22 14:51 GMT+01:00 Paul B Mahol :
>>> On 2/22/17, Paul B Mahol wrote:
Signed-off-by: Paul B Mahol
---
libavcodec/dnxhddec.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
>>
On 2/23/17, Carl Eugen Hoyos wrote:
> 2017-02-23 8:06 GMT+01:00 Paul B Mahol :
>> On 2/23/17, Carl Eugen Hoyos wrote:
>
>>> Attached patch adds gray10 and gray12 native endian
>>> encoding support to libx265.
>
>> Does this get decoded with native hevc?
>
> Yes, which sample fails for you?
I hav
2017-02-23 8:06 GMT+01:00 Paul B Mahol :
> On 2/23/17, Carl Eugen Hoyos wrote:
>> Attached patch adds gray10 and gray12 native endian
>> encoding support to libx265.
> Does this get decoded with native hevc?
Yes, which sample fails for you?
Carl Eugen
__
On Thu, 23 Feb 2017 07:57:41 -0500
"Ronald S. Bultje" wrote:
> Hi,
>
> On Thu, Feb 23, 2017 at 2:19 AM, wm4 wrote:
>
> > On Wed, 22 Feb 2017 19:16:46 +0100
> > Michael Niedermayer wrote:
> >
> > > This enables the extra error messages in case of DEBUG or high assrtion
> > levels.
> > >
Hi,
On Thu, Feb 23, 2017 at 2:19 AM, wm4 wrote:
> On Wed, 22 Feb 2017 19:16:46 +0100
> Michael Niedermayer wrote:
>
> > This enables the extra error messages in case of DEBUG or high assrtion
> levels.
> > High assertion levels imply slow checks in inner loops so any extra
> error should
> > be
On Thu, Feb 23, 2017 at 08:05:24AM +0100, Paul B Mahol wrote:
> On 2/23/17, Michael Niedermayer wrote:
> > On Wed, Feb 22, 2017 at 09:25:04PM +0100, Paul B Mahol wrote:
> >> ffmpeg | branch: master | Paul B Mahol | Wed Feb 22
> >> 15:32:26 2017 +0100| [fb5c9be82ea870fd0a7643214ebf8728d8e29991] |
Am 23.02.2017 um 02:07 schrieb Michael Niedermayer:
> On Wed, Feb 22, 2017 at 11:15:45PM +, Stefan _ wrote:
>
>> From: sfan5
> Is it intended that theres no full name in the git author field ?
>
> [...]
Yes that's intended.
___
ffmpeg-devel mailing
On 23/02/17 00:44, Jun Zhao wrote:
> Ping? I know the commit "eefa4b" give a fix, but I think this one more
> better for this issue :)
Would you care to offer any reasoning for why you think this is better?
> On 2017/2/8 15:39, Jun Zhao wrote:
>> From e37b2598d372b790c0a496c7b750802a1aa102be M
av_malloc prefers posix_malloc over _aligned_alloc so realloc and free
functions must be used when posix_malloc is available. This fixes mingw32
builds when using custom allocators.
---
libavutil/mem.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/libavutil/mem.c b/liba
56 matches
Mail list logo
