---
libavfilter/vf_overlay.c| 22 +-
tests/fate/filter-video.mak | 10 ++
tests/filtergraphs/overlay_nv12 | 5 +
tests/filtergraphs/overlay_nv21 | 5 +
4 files changed, 37 insertions(+), 5 deletions(-)
create mode 100644 tests/filtergraphs/overlay
On 20.10.2016 18:01, Dave Rice wrote:
On Oct 20, 2016, at 3:28 AM, Tobias Rapp wrote:
On 19.10.2016 23:15, Michael Niedermayer wrote:
On Wed, Oct 19, 2016 at 02:35:21PM +0200, Tobias Rapp wrote:
From: Rodger Combs
Reviewed-by: Tobias Rapp
---
doc/ffprobe.xsd
On Tue, Oct 25, 2016 at 1:50 AM, Andreas Cadhalpun
wrote:
> This should reduce the impact of a demuxer (or API user) setting bogus
> codec parameters.
>
>
This seems rather noisy and doesn't really solve anything, does it?
Decoders still need to validate values instead of blindly trusting
them, a
On 21.10.2016 11:58, Tobias Rapp wrote:
On 20.10.2016 09:36, Tobias Rapp wrote:
On 19.10.2016 23:06, Michael Niedermayer wrote:
On Wed, Oct 19, 2016 at 02:35:22PM +0200, Tobias Rapp wrote:
Signed-off-by: Tobias Rapp
---
tests/fate/mxf.mak| 19 ++-
tests/ref/fate/m
LGTM
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
On 10/22/16, Michael Niedermayer wrote:
> The subsequent huffman code performs several memory allocations, MMX state
> thus needs to be cleared between
>
> Signed-off-by: Michael Niedermayer
> ---
> libavcodec/utvideoenc.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/libavcodec/utvid
On 10/23/16, Andreas Cadhalpun wrote:
> A negative sample rate doesn't make sense and triggers assertions in
> av_rescale_rnd.
>
> Signed-off-by: Andreas Cadhalpun
> ---
> libavformat/adxdec.c | 5 +
> 1 file changed, 5 insertions(+)
>
> diff --git a/libavformat/adxdec.c b/libavformat/adxdec
Hi!
Attached patch may fix an issue reported on the gusari forum.
Please comment, Carl Eugen
From 20d2713bc1d4997a03bde52afd4192bbb48d3bb8 Mon Sep 17 00:00:00 2001
From: Carl Eugen Hoyos
Date: Tue, 25 Oct 2016 12:55:54 +0200
Subject: [PATCH] lavc/utvideoenc: Set bits_per_coded_sample for rgba in
On 10/25/16, Carl Eugen Hoyos wrote:
> Hi!
>
> Attached patch may fix an issue reported on the gusari forum.
>
> Please comment, Carl Eugen
>
Please clearly explain what is actual problem and what this patch
actually solves. I do not have time of all existence to search forums
on internet.
__
2016-10-25 13:01 GMT+02:00 Paul B Mahol :
> On 10/25/16, Carl Eugen Hoyos wrote:
>> Hi!
>>
>> Attached patch may fix an issue reported on the gusari forum.
> Please clearly explain what is actual problem and what this patch
> actually solves. I do not have time of all existence to search forums
>
On 10/25/16, Carl Eugen Hoyos wrote:
> 2016-10-25 13:01 GMT+02:00 Paul B Mahol :
>> On 10/25/16, Carl Eugen Hoyos wrote:
>>> Hi!
>>>
>>> Attached patch may fix an issue reported on the gusari forum.
>
>> Please clearly explain what is actual problem and what this patch
>> actually solves. I do no
On Tue, Oct 25, 2016 at 01:50:47AM +0200, Andreas Cadhalpun wrote:
> This should reduce the impact of a demuxer (or API user) setting bogus
> codec parameters.
>
> Suggested-by: wm4
> Signed-off-by: Andreas Cadhalpun
> ---
> libavcodec/utils.c | 82
>
2016-10-25 13:42 GMT+02:00 Paul B Mahol :
> On 10/25/16, Carl Eugen Hoyos wrote:
>> 2016-10-25 13:01 GMT+02:00 Paul B Mahol :
>>> On 10/25/16, Carl Eugen Hoyos wrote:
Attached patch may fix an issue reported on the gusari forum.
>>
>>> Please clearly explain what is actual problem and what
On Mon, Oct 24, 2016 at 09:53:22PM +0200, Henrik Gramner wrote:
> The decision to issue emms manually instead of after every MMX
> function was a deliberate decision. I'd hardly call it "misdesigned"
> to make SIMD code twice as fast at the cost of technically abusing the
It would be nice to look
On Tue, 25 Oct 2016 09:47:29 +0200
Hendrik Leppkes wrote:
> On Tue, Oct 25, 2016 at 1:50 AM, Andreas Cadhalpun
> wrote:
> > This should reduce the impact of a demuxer (or API user) setting bogus
> > codec parameters.
> >
> >
>
> This seems rather noisy and doesn't really solve anything, does
On Tue, Oct 25, 2016 at 2:39 PM, wm4 wrote:
> On Tue, 25 Oct 2016 09:47:29 +0200
> Hendrik Leppkes wrote:
>
>> On Tue, Oct 25, 2016 at 1:50 AM, Andreas Cadhalpun
>> wrote:
>> > This should reduce the impact of a demuxer (or API user) setting bogus
>> > codec parameters.
>> >
>> >
>>
>> This seem
Gentle ping!
On Wed, Oct 19, 2016 at 12:14 PM, Suman Kancherla (సుమన్) <
sumankanche...@google.com> wrote:
> Thanks for taking time to review my patch! I appreciate it very much!!
>
> "Suman-" is my ID on github; Unless it is objectionable, I intend to use
> it for code submissions.
>
> Thanks!
>
On date Wednesday 2016-10-19 17:37:36 +0200, Moritz Barsnick encoded:
> On Tue, Oct 18, 2016 at 13:33:27 +0200, Stefano Sabatini wrote:
> > > Latest patch in attachment with ffprobe demuxer disabled by default,
> > > and extended documentation. (I'm also attaching the ff_get_line2 patch
> > > which
On date Tuesday 2016-10-18 16:06:47 +0200, Michael Niedermayer encoded:
> On Tue, Oct 18, 2016 at 01:33:27PM +0200, Stefano Sabatini wrote:
> > On date Thursday 2016-10-13 19:46:41 +0200, Stefano Sabatini encoded:
> > > On date Thursday 2016-09-29 21:55:11 +0200, wm4 encoded:
> > [...]
> > > > This
The dynamic buffer does not contain the CRC32 element so calls to avio_tell()
don't take it into account. This resulted in CueRelativePosition values being
six bytes short.
This is a regression since 6724525a1576ca334d2ffdc085620bb44aea7394
Instead of adding yet another custom check for CRC32 to f
On Tue, Oct 25, 2016 at 2:28 PM, wrote:
> It would be nice to look at a benchmarking comparison, to be able to
> see the actual practical performance gain of the decision not to follow
> the ABI.
Just a quick comparison from adding EMMS to a random MMX function
(from x264, because I happened to
Bud-Id: https://bugs.gentoo.org/show_bug.cgi?id=598054
Signed-off-by: Andreas Cadhalpun
---
configure | 8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/configure b/configure
index 481f692..14a20ed 100755
--- a/configure
+++ b/configure
@@ -1147,8 +1147,14 @@ check_func_he
On Sun, Oct 23, 2016 at 02:29:37PM +0200, Nicolas George wrote:
> The framework will allocate a buffer and copy the data to it,
> that takes time. But it avoids constently creating and
> destroyng the shared memory segment, and that saves more time.
>
> On my setup,
> from ~200 to ~300 FPS at full
On Sun, Oct 23, 2016 at 02:29:37PM +0200, Nicolas George wrote:
> The framework will allocate a buffer and copy the data to it,
> that takes time. But it avoids constently creating and
> destroyng the shared memory segment, and that saves more time.
>
> On my setup,
> from ~200 to ~300 FPS at full
On 25.10.2016 12:58, Paul B Mahol wrote:
> patch(es)have good intent, but better fix is doing/checking it in single
> place.
I don't agree.
In general, validity checks should be where the values are actually read.
This eliminates the risk that bogus values could cause problems between being
set
On Sun, Oct 23, 2016 at 02:29:37PM +0200, Nicolas George wrote:
> The framework will allocate a buffer and copy the data to it,
> that takes time. But it avoids constently creating and
> destroyng the shared memory segment, and that saves more time.
>
> On my setup,
> from ~200 to ~300 FPS at full
John Warburton 于2016年9月28日 周三下午6:22写道：
> On Sun, Sep 4, 2016 at 10:34 PM, Thomas Volkert wrote:
>
> > Hi,
> >
> > Some guys at the VDD asked for FFmpeg T-shirts.
> > I'd like to do a new T-shirt order. The shirts could be given to
> > multimedia devs who stop at one of our next booths.
> >
> > I
Le quartidi 4 brumaire, an CCXXV, Clement Boesch a écrit :
> > The framework will allocate a buffer and copy the data to it,
> > that takes time.
> Sorry if this is a dumb question but: can you describe what happens if the
> previous packet still held the same pkt->data = c->buffer?
>
> That is,
On Tue, Oct 25, 2016 at 07:58:56PM +0200, Nicolas George wrote:
> Le quartidi 4 brumaire, an CCXXV, Clement Boesch a écrit :
> > > The framework will allocate a buffer and copy the data to it,
> > > that takes time.
>
> > Sorry if this is a dumb question but: can you describe what happens if the
>
On 23/10/16 13:29, Nicolas George wrote:
The framework will allocate a buffer and copy the data to it,
that takes time. But it avoids constently creating and
destroyng the shared memory segment, and that saves more time.
On my setup,
from ~200 to ~300 FPS at full screen (1920×1200),
from ~1400 t
On Tue, Oct 25, 2016 at 05:48:50PM +0200, Henrik Gramner wrote:
> On Tue, Oct 25, 2016 at 2:28 PM, wrote:
> > It would be nice to look at a benchmarking comparison, to be able to
> > see the actual practical performance gain of the decision not to follow
> > the ABI.
>
> Just a quick comparison
On Tue, Oct 25, 2016 at 01:52:28AM -0500, Rodger Combs wrote:
> ---
> libavfilter/vf_overlay.c| 22 +-
> tests/fate/filter-video.mak | 10 ++
> tests/filtergraphs/overlay_nv12 | 5 +
> tests/filtergraphs/overlay_nv21 | 5 +
> 4 files changed, 37 in
On Sat, Oct 22, 2016 at 11:40:42PM -0700, Thomas Turner wrote:
> Function(s) Tested: av_packet_clone().
>
> This test checks if av_packet_clone() can successfully make a copy of an
> AVPacket.
> Compares all data members in AVPacket EXCEPT for "buf" because "buf" is
> initialized
> to NIL in the
On Tue, Oct 25, 2016 at 11:39:01AM +0200, Timo Rothenpieler wrote:
> LGTM
applied
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
It is dangerous to be right in matters on which the established authorities
are wrong. -- Voltaire
signature.asc
Description:
On Tue, Oct 25, 2016 at 14:28:38 +0200, u-9...@aetey.se wrote:
> In a perfect world the user might be offered a build time choice:
> either lose N% of the performance or take the consequences of not
> following the ABI.
That was exactly my thought too, assuming it doesn't pollute the code
even mor
On Sat, Oct 22, 2016 at 22:02:15 -0400, Ronald S. Bultje wrote:
> I was hoping for documentation on what it expects, not what can be changed
> about it :) Anyway, I'll change it, I don't really care.
I had found this to be quite clear:
> End with a comment. The checker assumes that this comment is
On Tue, Oct 25, 2016 at 07:45:25PM +0200, Andreas Cadhalpun wrote:
> On 25.10.2016 12:58, Paul B Mahol wrote:
> > patch(es)have good intent, but better fix is doing/checking it in single
> > place.
>
> I don't agree.
> In general, validity checks should be where the values are actually read.
> Th
2016-10-25 19:19 GMT+02:00 Andreas Cadhalpun :
> +# LTO could optimize out the test functions without this
> +echo "#if defined(__GNUC__) && __GNUC__ >= 4"
> +echo " #define USED __attribute__((used))"
> +echo "#else"
> +echo " #define USED"
> +ech
Hi,
On Tue, Oct 25, 2016 at 5:12 PM, Moritz Barsnick wrote:
> On Tue, Oct 25, 2016 at 14:28:38 +0200, u-9...@aetey.se wrote:
> > In a perfect world the user might be offered a build time choice:
> > either lose N% of the performance or take the consequences of not
> > following the ABI.
>
> That
On Tue, Oct 25, 2016 at 14:24:34 +0800, qw wrote:
> I have one question about some rare usage for avfilter graph:
Wrong list for usage.
> Sometimes, I want to change the setting in avfilter graph. For
> example, fps filter is used to set output frame rate, and it's
> expected that fps can be chan
On Mon, Oct 24, 2016 at 11:24 PM, qw wrote:
> Hi,
>
>
> I have one question about some rare usage for avfilter graph:
>
>
> Sometimes, I want to change the setting in avfilter graph. For example,
> fps filter is used to set output frame rate, and it's expected that fps can
> be changed in accorda
Fixes out of array read
Found-by: Thomas Garnier using libFuzzer
Signed-off-by: Michael Niedermayer
---
libavcodec/dvdsubdec.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libavcodec/dvdsubdec.c b/libavcodec/dvdsubdec.c
index b81b481..18475ec 100644
--- a/libavcodec/dvdsub
On Mon, Oct 24, 2016 at 11:06:13PM +0200, Martin Vignali wrote:
> Hello,
>
> In attach a patch to add 2 test for aphasemeter metadata
>
> The sample can be found here :
>
> https://we.tl/AP7SY8eNSe
uploaded
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FA
Hi all,
Am 21.10.2016 um 10:32 schrieb Michael Behrisch:
> Am 20.10.2016 um 10:00 schrieb Clément Bœsch:
>> On Thu, Oct 20, 2016 at 09:55:17AM +0200, Nicolas George wrote:
>>> Le nonidi 29 vendémiaire, an CCXXV, Clement Boesch a écrit :
it's really a trivial and harmless patch.
>>>
>>> Which
On 25.10.2016 23:34, Carl Eugen Hoyos wrote:
> 2016-10-25 19:19 GMT+02:00 Andreas Cadhalpun
> :
>
>> +# LTO could optimize out the test functions without this
>> +echo "#if defined(__GNUC__) && __GNUC__ >= 4"
>> +echo " #define USED __attribute__((used))"
>> +echo
On Wed, Oct 26, 2016 at 01:16:13AM +0200, Andreas Cadhalpun wrote:
> On 25.10.2016 23:34, Carl Eugen Hoyos wrote:
> > 2016-10-25 19:19 GMT+02:00 Andreas Cadhalpun
> > :
> >
> >> +# LTO could optimize out the test functions without this
> >> +echo "#if defined(__GNUC__) && __GNUC__
On Wed, Sep 28, 2016 at 05:11:23PM +0200, Carl Eugen Hoyos wrote:
> 2016-09-27 15:30 GMT+02:00 Michael Niedermayer :
>
> > Its long since FFmpeg 3.1, so its time to make 3.2
>
> The configure option --enable-incompatible-libav-abi was intentionally
> broken some time ago, if it cannot get removed
On 26.10.2016 01:26, Michael Niedermayer wrote:
> On Wed, Oct 26, 2016 at 01:16:13AM +0200, Andreas Cadhalpun wrote:
>> configure |7 ++-
>> 1 file changed, 6 insertions(+), 1 deletion(-)
>> 742684cf379693d08075d43fdfb75ed5e2e936c6
>> 0001-configure-make-sure-LTO-does-not-optimize-out-th
On 25.10.2016 13:43, Michael Niedermayer wrote:
> On Tue, Oct 25, 2016 at 01:50:47AM +0200, Andreas Cadhalpun wrote:
>> This should reduce the impact of a demuxer (or API user) setting bogus
>> codec parameters.
>>
>> Suggested-by: wm4
>> Signed-off-by: Andreas Cadhalpun
>> ---
>> libavcodec/util
On Tue, Oct 25, 2016 at 05:07:34PM +0200, Stefano Sabatini wrote:
> On date Tuesday 2016-10-18 16:06:47 +0200, Michael Niedermayer encoded:
> > On Tue, Oct 18, 2016 at 01:33:27PM +0200, Stefano Sabatini wrote:
> > > On date Thursday 2016-10-13 19:46:41 +0200, Stefano Sabatini encoded:
> > > > On da
On Mon, Oct 24, 2016 at 03:20:14PM -0600, Roger Pack wrote:
> On 10/16/16, Michael Niedermayer wrote:
> > On Mon, Oct 10, 2016 at 02:56:24PM -0600, Roger Pack wrote:
> >> On 9/22/16, Roger Pack wrote:
> >> > On 1/4/12, Yuval Adam wrote:
> >> >> From: Yuval Adam
> >> >>
> >> >> The image2 muxer
On 25.10.2016 14:56, Hendrik Leppkes wrote:
> On Tue, Oct 25, 2016 at 2:39 PM, wm4 wrote:
>> On Tue, 25 Oct 2016 09:47:29 +0200
>> Hendrik Leppkes wrote:
>>
>>> On Tue, Oct 25, 2016 at 1:50 AM, Andreas Cadhalpun
>>> wrote:
This should reduce the impact of a demuxer (or API user) setting bog
On Tue, Oct 25, 2016 at 10:25:22AM +0200, Tobias Rapp wrote:
> On 21.10.2016 11:58, Tobias Rapp wrote:
> >On 20.10.2016 09:36, Tobias Rapp wrote:
> >>On 19.10.2016 23:06, Michael Niedermayer wrote:
> >>>On Wed, Oct 19, 2016 at 02:35:22PM +0200, Tobias Rapp wrote:
> Signed-off-by: Tobias Rapp
>
On Wed, Oct 26, 2016 at 01:35:34AM +0200, Andreas Cadhalpun wrote:
> On 26.10.2016 01:26, Michael Niedermayer wrote:
> > On Wed, Oct 26, 2016 at 01:16:13AM +0200, Andreas Cadhalpun wrote:
> >> configure |7 ++-
> >> 1 file changed, 6 insertions(+), 1 deletion(-)
> >> 742684cf379693d08075d4
On Wed, Oct 19, 2016 at 12:14:57PM -0700, Suman Kancherla (సుమన్) wrote:
> Thanks for taking time to review my patch! I appreciate it very much!!
>
> "Suman-" is my ID on github; Unless it is objectionable, I intend to use it
> for code submissions.
patch applied
thanks
[...]
--
Michael Gn
On 10/25/16, Michael Niedermayer wrote:
> On Mon, Oct 24, 2016 at 03:20:14PM -0600, Roger Pack wrote:
>> On 10/16/16, Michael Niedermayer wrote:
>> > On Mon, Oct 10, 2016 at 02:56:24PM -0600, Roger Pack wrote:
>> >> On 9/22/16, Roger Pack wrote:
>> >> > On 1/4/12, Yuval Adam wrote:
>> >> >> Fro
Hi All:
Do someone encountered this situation like the attach showed ?
If so ,could you give some tips about it ?
What's the problem could it be ?
I gave the theme about this as follow:
I was used ffmpeg AVIOContext from other source.
On 26/10/16 02:30, chengmo wrote:
Hi All:
Do someone encountered this situation like the attach showed ?
If so ,could you give some tips about it ?
What's the problem could it be ?
A couple of things... "libav" and "ffmpeg" are not the same project. So please
---
libavfilter/vf_overlay.c| 22 +-
tests/fate/filter-video.mak | 10 ++
tests/filtergraphs/overlay_nv12 | 5 +
tests/filtergraphs/overlay_nv21 | 5 +
4 files changed, 37 insertions(+), 5 deletions(-)
create mode 100644 tests/filtergraphs/overlay
According to spec ISO_IEC_15444_12 "For any media stream for which no segment
index is present, referred to as non‐indexed stream, the media stream
associated with the first Segment Index box in the segment serves as a
reference stream in a sense that it also describes the subsegments for any
n
60 matches
Mail list logo
