Hi,
On Sun, Nov 20, 2016 at 9:16 AM, Michael Niedermayer wrote:
> On Sun, Nov 20, 2016 at 08:56:15AM -0500, Ronald S. Bultje wrote:
> > Hi,
> >
> > On Sun, Nov 20, 2016 at 6:57 AM, Michael Niedermayer
> > > wrote:
> >
> > > @@ -131,6 +132,20 @@ stat
Hi,
On Sun, Nov 20, 2016 at 6:57 AM, Michael Niedermayer wrote:
> @@ -131,6 +132,20 @@ static int write_number(void *obj, const AVOption *o,
> void *dst, double num, int
> if (intnum == 1 && d == (double)INT64_MAX) *(int64_t *)dst =
> INT64_MAX;
> else
Hi,
On Sat, Nov 19, 2016 at 7:07 PM, Andreas Cadhalpun <
andreas.cadhal...@googlemail.com> wrote:
> gcc before gcc-5 reserves a register on x86_32 for the GOT, when PIE is
> enabled.
>
> This fixes build failures due to:
> error: 'asm' operand has impossible constraints
>
> Signed-off-by: Andreas
Hi,
On Thu, Nov 17, 2016 at 5:02 PM, Vittorio Giovara <
vittorio.giov...@gmail.com> wrote:
> On Thu, Nov 17, 2016 at 4:11 PM, Ronald S. Bultje
> wrote:
> > Hi,
> >
> > On Thu, Nov 17, 2016 at 4:09 PM, Vittorio Giovara
> > wrote:
> >>
> >> T
Hi,
On Thu, Nov 17, 2016 at 4:11 PM, Michael Niedermayer wrote:
> On Thu, Nov 17, 2016 at 09:13:55PM +0100, Carl Eugen Hoyos wrote:
> > 2016-11-17 14:49 GMT+01:00 Rostislav Pehlivanov :
> > > On 16 November 2016 at 11:15, Carl Eugen Hoyos
> wrote:
> > >
> > >> Hi!
> > >>
> > >> Attached patch i
Hi,
On Thu, Nov 17, 2016 at 4:09 PM, Vittorio Giovara <
vittorio.giov...@gmail.com> wrote:
> This prevents writing past bounds.
>
> Signed-off-by: Vittorio Giovara
> ---
> Updated according review.
> Vittorio
>
> doc/filters.texi| 1 +
> libavfilter/vf_colorspace.c | 9 -
>
Hi,
On Thu, Nov 17, 2016 at 3:53 PM, Vittorio Giovara <
vittorio.giov...@gmail.com> wrote:
> This prevents writing past bounds.
>
> Signed-off-by: Vittorio Giovara
> ---
> Any opinions about this?
Hm... I agree right now it's probably broken, but I'd argue that we should
fix it, not forbid it.
Hi Carl,
On Thu, Nov 17, 2016 at 3:10 PM, Carl Eugen Hoyos
wrote:
> 2016-11-17 19:34 GMT+01:00 Ronald S. Bultje :
> > Carl, the reason the patch is wrong is that luma range does not scale up
> > from 16< > This is documented in numerous places, see e.g.
> > https
Hi,
On Thu, Nov 17, 2016 at 1:06 PM, Kieran Kunhya wrote:
> On Thu, 17 Nov 2016 at 18:05 Kieran Kunhya wrote:
>
> > On Wed, 16 Nov 2016 at 23:49 Kieran Kunhya wrote:
> >
> > It was lossless before and is lossless after the patch but it
> > output the 16bit format that you don't like and of whi
Hi Kieran,
On Tue, Nov 15, 2016 at 7:18 PM, Kieran O Leary
wrote:
> From: kieranjol
Is your name spelled like this intentionally? Maybe change your git config
so this has your full name instead of what appears to be your login?
Ronald
___
ffmpeg-de
Hi,
On Mon, Nov 14, 2016 at 9:29 AM, Michael Niedermayer wrote:
> On Mon, Nov 14, 2016 at 12:32:19PM +0200, Martin Storsjö wrote:
> > Make them aligned, to allow efficient access to them from simd.
> >
> > This is an adapted cherry-pick from libav commit
> > a4cfcddcb0f76e837d5abc06840c2b26c0e8a
Hi,
On Mon, Nov 14, 2016 at 4:26 PM, James Almer wrote:
> On 11/8/2016 1:22 PM, Ronald S. Bultje wrote:
> > Also a small cosmetic change to the avx2 idct16 version to make it
> > explicit that one of the arguments to the write-out macros is unused
> > for >=avx2 (it
Hi,
On Mon, Nov 14, 2016 at 5:32 AM, Martin Storsjö wrote:
> Make them aligned, to allow efficient access to them from simd.
>
> This is an adapted cherry-pick from libav commit
> a4cfcddcb0f76e837d5abc06840c2b26c0e8aefc.
> ---
> libavcodec/vp9dsp.c | 56 +++
Hi,
assume this is my reply on all patches in the range 2-9:
On Mon, Nov 14, 2016 at 5:32 AM, Martin Storsjö wrote:
> We reset .Lpic_gp to zero at the start of each function, which means
> that the logic within movrelx for clearing gp when necessary will
> be missed.
>
> This fixes using movrel
Hi Andreas,
On Nov 12, 2016 5:52 PM, "Andreas Cadhalpun" <
andreas.cadhal...@googlemail.com> wrote:
>
> The handling of the other block sizes was disabled for 'SCALED == 0' in
> commit dc96c0f9fc96bf4167633befc074394062793322, so this assert should
> be disabled, too, as it can now be triggered.
>
Hi,
On Tue, Nov 8, 2016 at 6:33 PM, compn wrote:
> On Tue, 8 Nov 2016 14:44:32 -0500
> "Ronald S. Bultje" wrote:
>
> > >> x86-32 linux gets stomach ache from this:
> > >>
> > >> YASMlibavcodec/x86/vp9itxfm.o
> > >>
Hi,
On Tue, Nov 8, 2016 at 2:43 PM, Ronald S. Bultje wrote:
> Hi,
>
> On Tue, Nov 8, 2016 at 2:39 PM, Michael Niedermayer <
> mich...@niedermayer.cc> wrote:
>
>> On Tue, Nov 08, 2016 at 11:22:31AM -0500, Ronald S. Bultje wrote:
>> > Also a small cosmetic
Hi,
On Tue, Nov 8, 2016 at 2:39 PM, Michael Niedermayer
wrote:
> On Tue, Nov 08, 2016 at 11:22:31AM -0500, Ronald S. Bultje wrote:
> > Also a small cosmetic change to the avx2 idct16 version to make it
> > explicit that one of the arguments to the write-out macros is unused
>
Also a small cosmetic change to the avx2 idct16 version to make it
explicit that one of the arguments to the write-out macros is unused
for >=avx2 (it uses pmovzxbw instead of punpcklbw).
---
libavcodec/x86/vp9dsp_init.c | 8 +-
libavcodec/x86/vp9itxfm.asm | 188
Hi,
On Sun, Oct 30, 2016 at 9:14 AM, Ronald S. Bultje
wrote:
> Hi,
>
> On Sun, Oct 30, 2016 at 3:07 AM, Vittorio Giovara <
> vittorio.giov...@gmail.com> wrote:
>
>> Signed-off-by: Vittorio Giovara
>> ---
>> This is a little hackish, not sure how to rep
Hi,
On Mon, Oct 31, 2016 at 2:49 PM, Ronald S. Bultje
wrote:
> Hi,
>
> On Mon, Oct 31, 2016 at 2:43 PM, Vittorio Giovara <
> vittorio.giov...@gmail.com> wrote:
>
>> Signed-off-by: Vittorio Giovara
>> ---
>> This is the last easy picking, the remai
Hi,
On Tue, Nov 1, 2016 at 8:09 AM, Ronald S. Bultje wrote:
> Hi,
>
> On Mon, Oct 31, 2016 at 5:51 PM, Vittorio Giovara <
> vittorio.giov...@gmail.com> wrote:
>
>> On Mon, Oct 31, 2016 at 4:08 PM, Ronald S. Bultje
>> wrote:
>> > Hi,
>> >
>
Hi,
On Mon, Oct 31, 2016 at 5:51 PM, Vittorio Giovara <
vittorio.giov...@gmail.com> wrote:
> On Mon, Oct 31, 2016 at 4:08 PM, Ronald S. Bultje
> wrote:
> > Hi,
> >
> > On Mon, Oct 31, 2016 at 3:31 PM, Vittorio Giovara
> > wrote:
> >>
> >
Hi,
On Mon, Oct 31, 2016 at 3:31 PM, Vittorio Giovara <
vittorio.giov...@gmail.com> wrote:
> On Mon, Oct 31, 2016 at 2:53 PM, Ronald S. Bultje
> wrote:
> > Hi,
> >
> > On Mon, Oct 31, 2016 at 11:13 AM, Vittorio Giovara
> > wrote:
> >>
> >
Hi,
On Mon, Oct 31, 2016 at 11:13 AM, Vittorio Giovara <
vittorio.giov...@gmail.com> wrote:
> On Mon, Oct 31, 2016 at 7:43 AM, Ronald S. Bultje
> wrote:
> > Hi,
> >
> > On Mon, Oct 31, 2016 at 5:50 AM, Kevin Wheatley <
> kevin.j.wheat...@gmail.com>
> &g
Hi,
On Mon, Oct 31, 2016 at 2:43 PM, Vittorio Giovara <
vittorio.giov...@gmail.com> wrote:
> Signed-off-by: Vittorio Giovara
> ---
> This is the last easy picking, the remaining trc/prm require more
> convoluted
> changes to the filter that will need more discussion.
> Please CC.
> Vittorio
>
>
Hi,
On Mon, Oct 31, 2016 at 5:50 AM, Kevin Wheatley
wrote:
> On Sun, Oct 30, 2016 at 1:18 PM, Ronald S. Bultje
> wrote:
> > Hmm... So, the wikipedia page https://en.wikipedia.org/wiki/DCI-P3
> refers
> > to the two whitepoints here as DCI-P3 D65 and DCI-P3 Theater. Callin
Hi Kieran,
On Sun, Oct 30, 2016 at 10:06 AM, Kieran O Leary
wrote:
> Hi,
>
> On Sun, Oct 30, 2016 at 7:07 AM, Vittorio Giovara <
> vittorio.giov...@gmail.com> wrote:
>
> > Signed-off-by: Vittorio Giovara
> > ---
> > I couldn't find any reference to the name of the whitepoint used for 431,
> > s
Hi,
On Sun, Oct 30, 2016 at 3:07 AM, Vittorio Giovara <
vittorio.giov...@gmail.com> wrote:
> Signed-off-by: Vittorio Giovara
> ---
> This is a little hackish, not sure how to represent the matrix otherwise.
Haha :) I have to admit I hadn't put much thought into YCgCo yet. It's a
little hacky b
Hi,
On Sun, Oct 30, 2016 at 3:07 AM, Vittorio Giovara <
vittorio.giov...@gmail.com> wrote:
> Signed-off-by: Vittorio Giovara
> ---
> I couldn't find any reference to the name of the whitepoint used for 431,
> so I came up with DCI, since it looks like it is only used there.
> Please CC.
> Vittor
Hi,
On Sun, Oct 30, 2016 at 3:07 AM, Vittorio Giovara <
vittorio.giov...@gmail.com> wrote:
> Signed-off-by: Vittorio Giovara
> ---
> As described in http://www.color.org/chardata/rgb/xvycc.xalter
> Please CC.
> Vittorio
>
> libavfilter/vf_colorspace.c | 3 +++
> 1 file changed, 3 insertions(+)
Hi,
On Thu, Oct 27, 2016 at 2:36 PM, Reynaldo H. Verdejo Pinochet <
reyna...@osg.samsung.com> wrote:
> Hello
>
> On 10/27/2016 11:25 AM, James Almer wrote:
>
>> [..]
>>
>> This is not how things were agreed.
>>
>>
> I haven't agreed to this.
Agreement that does not have to be unanimous.
Ronald
Hi,
On Wed, Oct 26, 2016 at 12:04 PM, wrote:
> On Wed, Oct 26, 2016 at 05:08:56PM +0200, Hendrik Leppkes wrote:
> > you just have to replace this stuff.
> > For $100 you can buy a system at least 10 times as fast then those.
> > Heck even a RPi might rival those for $20 or so.
>
> Such arguments
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
Hi,
On Mon, Oct 24, 2016 at 4:26 PM, Henrik Gramner wrote:
> On Mon, Oct 24, 2016 at 9:59 PM, Ronald S. Bultje
> wrote:
> > Good idea to reference Hendrik Gramner here, who keeps insisting we get
> rid
> > of all MMX code in ffmpeg (at least as an option) for future Inte
Hi,
On Sat, Oct 22, 2016 at 10:02 PM, Ronald S. Bultje
wrote:
> Hi,
>
> On Sat, Oct 22, 2016 at 12:19 PM, Moritz Barsnick
> wrote:
>
>> On Sat, Oct 22, 2016 at 08:43:26 -0400, Ronald S. Bultje wrote:
>> > Is there documentation on what coverity expects?
>&
Hi,
On Fri, Oct 14, 2016 at 2:09 PM, James Zern wrote:
> Ronald,
>
> On Fri, Oct 14, 2016 at 10:01 AM, Ronald S. Bultje
> wrote:
> > This is intended to workaround bug "665 Integer Divide Instruction May
> > Cause Unpredictable Behavior" on some early AMD CP
Hi,
On Thu, Oct 20, 2016 at 12:37 PM, Michael Niedermayer <
mich...@niedermayer.cc> wrote:
> On Tue, Oct 18, 2016 at 03:17:26PM -0400, Vittorio Giovara wrote:
> > Signed-off-by: Vittorio Giovara
> > ---
> > Special thanks to Andrew Roland for helping me figure out these numbers.
> > Please keep
Hi,
On Mon, Oct 24, 2016 at 3:34 PM, wm4 wrote:
> On Mon, 24 Oct 2016 21:19:46 +0200
> Andreas Cadhalpun wrote:
>
> > On 24.10.2016 16:14, Ronald S. Bultje wrote:
> > > On Mon, Oct 24, 2016 at 8:47 AM, wm4 wrote:
> > >> On Mon, 24 Oct 2016 07:54:47 -0
Hi,
On Mon, Oct 24, 2016 at 8:47 AM, wm4 wrote:
> On Mon, 24 Oct 2016 07:54:47 -0400
> "Ronald S. Bultje" wrote:
>
> > Hi,
> >
> > On Mon, Oct 24, 2016 at 3:36 AM, wm4 wrote:
> >
> > > On Sun, 23 Oct 2016 13:02:01 -0400
> > > "
Hi,
On Mon, Oct 24, 2016 at 3:36 AM, wm4 wrote:
> On Sun, 23 Oct 2016 13:02:01 -0400
> "Ronald S. Bultje" wrote:
>
> > Hi,
> >
> > On Sat, Oct 22, 2016 at 11:36 PM, Michael Niedermayer <
> > mich...@niedermayer.cc> wrote:
> >
> >
Hi,
On Mon, Oct 24, 2016 at 7:24 AM, Michael Niedermayer wrote:
> On Mon, Oct 24, 2016 at 09:38:00AM +0200, wm4 wrote:
> > On Sun, 23 Oct 2016 05:37:25 +0200
> > Michael Niedermayer wrote:
> >
> > > Signed-off-by: Michael Niedermayer
> > > ---
> > > libavutil/x86/emms.h | 2 ++
> > > 1 file c
Hi,
On Sun, Oct 23, 2016 at 4:33 PM, Michael Niedermayer wrote:
> On Sun, Oct 23, 2016 at 01:02:01PM -0400, Ronald S. Bultje wrote:
> > Hi,
> >
> > On Sat, Oct 22, 2016 at 11:36 PM, Michael Niedermayer <
> > mich...@niedermayer.cc> wrote:
> >
> &g
Hi,
On Sat, Oct 22, 2016 at 11:36 PM, Michael Niedermayer <
mich...@niedermayer.cc> wrote:
> On Sat, Oct 22, 2016 at 10:10:01PM -0400, Ronald S. Bultje wrote:
> > Hi,
> >
> > general comment about all other dec patches.
> >
> > On Sat, Oct 22, 2016 at 3:
Hi,
general comment about all other dec patches.
On Sat, Oct 22, 2016 at 3:02 PM, Michael Niedermayer wrote:
> Signed-off-by: Michael Niedermayer
> ---
> libavcodec/svq1dec.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/libavcodec/svq1dec.c b/libavcodec/svq1dec.c
> index 2b72e08
Hi,
On Sat, Oct 22, 2016 at 3:02 PM, Michael Niedermayer wrote:
> Signed-off-by: Michael Niedermayer
> ---
> libavcodec/vp56.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/libavcodec/vp56.c b/libavcodec/vp56.c
> index 6319248..2125000 100644
> --- a/libavcodec/vp56.c
> +++ b/libavc
Hi,
On Sat, Oct 22, 2016 at 3:02 PM, Michael Niedermayer wrote:
> This decreases the number of FPU state violations in fate on x86-64 from
> 309 to 79
>
> Signed-off-by: Michael Niedermayer
> ---
> libavcodec/pthread_frame.c | 3 +++
> libavcodec/utils.c | 2 ++
> 2 files changed, 5 in
Hi,
On Sat, Oct 22, 2016 at 12:19 PM, Moritz Barsnick wrote:
> On Sat, Oct 22, 2016 at 08:43:26 -0400, Ronald S. Bultje wrote:
> > Is there documentation on what coverity expects?
>
> I found this:
> https://lost-contact.mit.edu/afs/cs.stanford.edu/pkg/
> prevent-4.3.1/i38
Hi,
On Fri, Oct 21, 2016 at 4:36 PM, Moritz Barsnick wrote:
> On Thu, Oct 20, 2016 at 12:06:14 -0400, Ronald S. Bultje wrote:
> > +s->did_range_warn = 1;
> > +}
> > // fall-through
> > +}
> > case AVCOL_RANGE_MPEG
Hi,
On Thu, Oct 20, 2016 at 11:14 PM, James Zern wrote:
> On Thu, Oct 20, 2016 at 8:31 AM, Kagami Hiiragi
> wrote:
> > vp9_cx_iface actually allows values in range [0..2].
> > This fixes ticket #5894.
> >
> > Signed-off-by: Kagami Hiiragi
> > ---
> > libavcodec/libvpxenc.c | 7 ++-
> > 1
Hi,
On Thu, Oct 20, 2016 at 1:08 PM, Josh de Kock wrote:
> On 20/10/2016 17:06, Ronald S. Bultje wrote:
>
>> ---
>> libavfilter/vf_colorspace.c | 12 ++--
>> 1 file changed, 10 insertions(+), 2 deletions(-)
>>
>> diff --git a/libavfilter/vf_colors
---
libavfilter/vf_colorspace.c | 12 ++--
1 file changed, 10 insertions(+), 2 deletions(-)
diff --git a/libavfilter/vf_colorspace.c b/libavfilter/vf_colorspace.c
index c74fe00..f64163f 100644
--- a/libavfilter/vf_colorspace.c
+++ b/libavfilter/vf_colorspace.c
@@ -163,6 +163,8 @@ typedef
Hi,
On Tue, Oct 18, 2016 at 3:17 PM, Vittorio Giovara <
vittorio.giov...@gmail.com> wrote:
> Signed-off-by: Vittorio Giovara
> ---
> Special thanks to Andrew Roland for helping me figure out these numbers.
> Please keep me in CC.
> Vittorio
>
> libavfilter/vf_colorspace.c | 3 +++
> 1 file chan
Hi,
On Wed, Oct 19, 2016 at 5:11 PM, Michael Behrisch wrote:
> Signed-off-by: Michael Behrisch
> ---
> libavutil/log.h| 2 +-
> libavutil/pixfmt.h | 12 ++--
> 2 files changed, 7 insertions(+), 7 deletions(-)
FWIW I still have doubts about this.
Ronald
_
Hi Ali,
On Tue, Oct 18, 2016 at 3:57 PM, Ali KIZIL wrote:
> 2016-10-18 22:44 GMT+03:00 Sven C. Dack :
>
> > On 18/10/16 20:26, Ali KIZIL wrote:
> >
> >> Hi Everyone,
> >>
> >> Today, I was analyzing memcpy duration in FFmpeg. I noticed that it is
> >> taking longer time compared to an optimized
Hi Vittorio,
On Mon, Oct 17, 2016 at 5:28 PM, Vittorio Giovara <
vittorio.giov...@gmail.com> wrote:
> On Mon, Sep 19, 2016 at 8:36 AM, Ronald S. Bultje
> wrote:
> > Hi,
> >
> > On Fri, Sep 16, 2016 at 9:27 AM, Clément Bœsch wrote:
> >>
> >> On
Hi Michael,
On Mon, Oct 17, 2016 at 5:23 PM, Michael Behrisch wrote:
> Hi Ronald,
>
> Am 17.10.2016 um 21:37 schrieb Ronald S. Bultje:
> > Hi Michael,
> >
> > On Mon, Oct 17, 2016 at 3:16 PM, Michael Behrisch
> > wrote:
> >
> >> Am 17.10.2016 um
Hi Michael,
On Mon, Oct 17, 2016 at 3:16 PM, Michael Behrisch wrote:
> Am 17.10.2016 um 15:29 schrieb Michael Niedermayer:
> > On Mon, Oct 17, 2016 at 01:34:55PM +0200, wm4 wrote:
> >> On Mon, 17 Oct 2016 13:09:36 +0200
> >> Michael Niedermayer wrote:
> >>
> >>> On Mon, Oct 17, 2016 at 10:07:42
Hi,
On Sun, Oct 16, 2016 at 6:11 PM, Michael Behrisch wrote:
> Am 16.10.2016 um 23:24 schrieb Clément Bœsch:
> > On Sun, Oct 16, 2016 at 09:46:20PM +0200, Michael Behrisch wrote:
> >> Hi all,
> >> first of all thanks for providing this great library.
> >>
> >> Today my pull request https://githu
Hi Michael,
On Fri, Oct 14, 2016 at 2:31 PM, Michael Niedermayer wrote:
> On Fri, Oct 14, 2016 at 08:29:37PM +0200, Michael Niedermayer wrote:
> > On Fri, Oct 14, 2016 at 11:09:30AM -0700, James Zern wrote:
> > > Ronald,
> > >
> > > On Fri, Oct 14, 2016 at
This is intended to workaround bug "665 Integer Divide Instruction May
Cause Unpredictable Behavior" on some early AMD CPUs, which causes a
div-by-zero in this codepath, such as reported in Mozilla bug #1293996.
Note that this isn't guaranteed to fix the bug, since a compiler is free
to reorder in
Hi,
On Oct 11, 2016 2:40 PM, "Alexey Eromenko" wrote:
>
> On Tue, Oct 11, 2016 at 8:29 PM, Josh de Kock wrote:
> > On 11/10/2016 18:24, Alexey Eromenko wrote:
> >>
> >> ---
> >> libavformat/movenc.c | 14 +-
> >> 1 file changed, 9 insertions(+), 5 deletions(-)
> >>
> >> diff --git a
Hi,
On Sun, Oct 9, 2016 at 7:32 AM, Steven Liu wrote:
> 2016-09-16 15:07 GMT+08:00 Michael Niedermayer :
>
> > On Thu, Sep 15, 2016 at 05:53:58PM -0800, Lou Logan wrote:
> > > On Wed, 7 Sep 2016 14:27:07 +0200, Michael Niedermayer wrote:
> > >
> > > > yes one can ignore it but its alot more usef
Hi,
On Mon, Oct 3, 2016 at 4:11 PM, Clément Bœsch wrote:
> On Mon, Oct 03, 2016 at 09:48:47PM +0200, Nicolas George wrote:
> > Le duodi 12 vendémiaire, an CCXXV, u-9...@aetey.se a écrit :
> > > The author of the referred code acts in his actual area of competence
> > > (C libraries and standards
Hi Rune,
On Mon, Oct 3, 2016 at 10:26 AM, wrote:
> On Mon, Oct 03, 2016 at 08:01:05AM -0400, Ronald S. Bultje wrote:
> > > Ping on the patch:
>
> > The patch is unlikely to assist in fixing the issue and is likely to
> cause
> > further inflammation. Therefore I
Hi,
On Mon, Oct 3, 2016 at 8:46 AM, Carl Eugen Hoyos wrote:
> 2016-10-03 13:57 GMT+02:00 Hendrik Leppkes :
>
> > The underlying problem is that mmx code is mixed with allocations,
>
> Definitely.
>
> > which seems like an unusual case to begin with
>
> I am not sure if I understand this but one
Hi,
On Sun, Oct 2, 2016 at 11:04 PM, compn wrote:
> On Sun, 2 Oct 2016 08:29:22 -0400
> "Ronald S. Bultje" wrote:
>
> > I also think we could contact musl developers and see what's going on
> > there. We certainly shouldn't blindly fix this bug by ad
Hi,
On Mon, Oct 3, 2016 at 7:37 AM, Carl Eugen Hoyos wrote:
> Hi!
>
> 2016-10-03 13:05 GMT+02:00 Guillaume POIRIER :
> > Hello,
> >
> > On Mon, Oct 3, 2016 at 11:38 AM, Carl Eugen Hoyos
> wrote:
> >> 2016-10-03 3:52 GMT+02:00 Carl Eugen Hoyos :
> >>
> >>> New patch attached.
> >>
> >>> +Compila
Hi,
On Sun, Oct 2, 2016 at 8:42 PM, Carl Eugen Hoyos wrote:
> 2016-10-03 2:36 GMT+02:00 Ronald S. Bultje :
> > Hi,
> >
> > On Sun, Oct 2, 2016 at 7:51 PM, Carl Eugen Hoyos
> wrote:
> >
> >> Attached patch adds a musl section to doc/platform.
> >
&
Hi,
On Sun, Oct 2, 2016 at 7:51 PM, Carl Eugen Hoyos wrote:
> Hi!
>
> Attached patch adds a musl section to doc/platform.
This is counter-productive... Let's work with the musl-devs and fix their
libc-alternative?
Ronald
___
ffmpeg-devel mailing lis
Hi,
On Sun, Oct 2, 2016 at 6:41 PM, Carl Eugen Hoyos wrote:
> 2016-10-02 14:29 GMT+02:00 Ronald S. Bultje :
> > I also think we could contact musl developers and see what's
> > going on there.
>
> I suspect I found the responsible code:
> http://git.musl-libc.
Hi,
On Sun, Oct 2, 2016 at 4:24 PM, Carl Eugen Hoyos wrote:
> 2016-10-02 16:01 GMT+02:00 Carl Eugen Hoyos :
>
> > PS: There are several unrelated build issues.
>
> The build issues were just seen here because I
> had to add "-melf_i386" to the musl spec file.
> After adding it, building works pe
Hi,
On Sun, Oct 2, 2016 at 2:17 AM, wrote:
> Hello Henrik,
>
> On Sun, Oct 02, 2016 at 01:18:29AM +0200, Henrik Gramner wrote:
> > Ensuring that emms is issued before every single libc function call is
> > likely problematic.
> >
> > What if we simply document the requirement that C standard lib
Hi,
On Sat, Oct 1, 2016 at 4:12 PM, wrote:
> Hello Ronald,
>
> On Sat, Oct 01, 2016 at 03:11:38PM -0400, Ronald S. Bultje wrote:
> > I'm not sure we want to go down the rabbit hole of allowing any code to
> be
> > executed inside frame en/decoding routines
Hi,
On Sat, Oct 1, 2016 at 2:27 PM, wrote:
> Hello,
>
> It looks like some general information is due:
>
> Musl libc is a high quality standard C library for Linux
> with emphasis on "quality" and "standard"
> http://www.musl-libc.org/
>
> On
Hi,
On Sat, Oct 1, 2016 at 12:25 PM, James Almer wrote:
> Signed-off-by: James Almer
> ---
> configure | 4
> libavcodec/aarch64/neontest.c | 10 ++
> libavcodec/arm/neontest.c | 10 ++
> libavcodec/x86/w64xmmtest.c | 10 ++
> 4 files cha
Hi,
On Sat, Oct 1, 2016 at 11:56 AM, wrote:
> On Sat, Oct 01, 2016 at 05:44:13PM +0200, wm4 wrote:
> > AFAIK most MMX code in FFmpeg does not run emms (i.e. keeps the FPU
> > state trashed) until returning to the API user.
>
> This means when malloc()/free()/... happens to be called internally,
Hi,
On Sat, Sep 24, 2016 at 9:11 AM, Carl Eugen Hoyos
wrote:
> Hi!
>
> 2016-09-24 14:58 GMT+02:00 Ronald S. Bultje :
> >
> > On Fri, Sep 23, 2016 at 6:00 PM, Carl Eugen Hoyos
> wrote:
> >>
> >> I use this patch locally for some time. It fixes
&g
Hi,
On Fri, Sep 23, 2016 at 6:00 PM, Carl Eugen Hoyos wrote:
> Hi!
>
> I use this patch locally for some time. It fixes
> many misdetections, a similar patch was applied to
> loas detection three years ago.
> An alternative would be to return "1" for two frames.
Is there any point in detecting
Hi,
On Fri, Sep 23, 2016 at 4:21 AM, Hendrik Leppkes
wrote:
> Fixes trac 5579
> ---
> libavcodec/x86/h264_weight.asm | 12 ++--
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/libavcodec/x86/h264_weight.asm b/libavcodec/x86/h264_weight.
> asm
> index 6c57d57..0975d74
Hi,
On Mon, Sep 19, 2016 at 9:47 PM, Lukasz Marek
wrote:
> On Sep 18, 2016 04:57, "Ronald S. Bultje" wrote:
> >
> > Hi,
> >
> > On Sat, Sep 17, 2016 at 4:26 PM, Marton Balint wrote:
> >
> > > I think we should wait until Lukasz does the p
Hi,
On Fri, Sep 16, 2016 at 9:27 AM, Clément Bœsch wrote:
> On Fri, Sep 16, 2016 at 03:20:49PM +0200, Vittorio Giovara wrote:
> > This is the assumption that is made in pixel format conversion do
> > throughout the code (in particular swscale), and BT-specifications
> > mandate.
> >
> > Add a wa
Hi,
On Sat, Sep 17, 2016 at 4:26 PM, Marton Balint wrote:
> I think we should wait until Lukasz does the port of the opengl device to
> SDL2, and do the switch after that.
When do we think that'll be finished?
Ronald
___
ffmpeg-devel mailing list
ff
Hi,
On Fri, Sep 16, 2016 at 12:22 PM, Carl Eugen Hoyos
wrote:
> 2016-09-16 18:19 GMT+02:00 Ronald S. Bultje :
> > Hi,
> >
> > On Fri, Sep 16, 2016 at 12:16 PM, Carl Eugen Hoyos
> > wrote:
> >
> >> 2016-09-16 16:07 GMT+02:00 Hendrik Leppkes :
> &
Hi,
On Fri, Sep 16, 2016 at 12:16 PM, Carl Eugen Hoyos
wrote:
> 2016-09-16 16:07 GMT+02:00 Hendrik Leppkes :
>
> > You want other developers to do more work
>
> Of which work are you talking about?
Installing libsdl1.
Ronald
___
ffmpeg-devel mailing
Hi,
On Fri, Sep 16, 2016 at 9:20 AM, Vittorio Giovara <
vittorio.giov...@gmail.com> wrote:
> This is the assumption that is made in pixel format conversion do
> throughout the code (in particular swscale), and BT-specifications
> mandate.
>
> Add a warning to inform the user that an automatic sel
Hi,
On Fri, Sep 16, 2016 at 8:48 AM, Carl Eugen Hoyos
wrote:
> Do we allow developers to continue to use sdl1 to test on their
> old (but supported) Linux distributions or do we forcibly stop
> them from contributing here?
All developers are welcome. You'll just have to install libsdl2 yoursel
Hi folks,
On Thu, Sep 15, 2016 at 1:36 PM, James Almer wrote:
> The vote will end 1 week from now, simple majority wins, and
> it's open only to those in the voting committee[1].
> Marton Balint, while not in the committee, should IMO also
> have the chance to vote or at least comment since he's
Hi,
On Fri, Sep 16, 2016 at 8:01 AM, Carl Eugen Hoyos
wrote:
> 2016-09-16 13:32 GMT+02:00 Paul B Mahol :
>
> >>> That's why i started this vote, to see how many devs are
> >>> effectively in favor or against and make the final decision
> >>> official.
> >>
> >> A vote on how evil the FFmpeg comm
Hi,
On Thu, Sep 15, 2016 at 9:32 AM, Vittorio Giovara <
vittorio.giov...@gmail.com> wrote:
>
> On Sep 15, 2016, at 2:45 PM, Ronald S. Bultje wrote:
>
> Hi Vittorio,
>
> On Thu, Sep 15, 2016 at 8:33 AM, Vittorio Giovara <
> vittorio.giov...@gmail.com> wrote:
>
Hi Vittorio,
On Thu, Sep 15, 2016 at 8:33 AM, Vittorio Giovara <
vittorio.giov...@gmail.com> wrote:
> I agree we should always be very very careful about automatic assignments,
> although this one seems pretty safe.
>
> I don't think it's necessary, but if you prefer I can add a warning
> wheneve
Hi,
On Wed, Sep 14, 2016 at 5:09 PM, Vittorio Giovara <
vittorio.giov...@gmail.com> wrote:
> This is the assumption that is made in pixel format conversion do
> throughout the code (in particular swscale and vf_colormatrix).
>
> Signed-off-by: Vittorio Giovara
> ---
> libavfilter/vf_colorspace.
Hi,
On Wed, Sep 14, 2016 at 5:09 PM, Vittorio Giovara <
vittorio.giov...@gmail.com> wrote:
> Allows to use values returned from API and from ffprobe directly.
>
> Signed-off-by: Vittorio Giovara
> ---
> libavfilter/vf_colorspace.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/libav
Hi,
On Wed, Sep 14, 2016 at 1:46 PM, Carl Eugen Hoyos
wrote:
> 2016-09-14 19:21 GMT+02:00 Ronald S. Bultje :
>
> [...]
>
> >> I wondered if somebody can easily fix muxing / demuxing which
> >> could be considered a nicer solution.
> >
> > You m
Hi,
On Wed, Sep 14, 2016 at 12:18 PM, Carl Eugen Hoyos
wrote:
> 2016-09-14 18:15 GMT+02:00 James Almer :
>
> > Configure failed to detect it
>
> configure requires 2.0.1
>
> Carl Eugen (who wonders how Ronald tests...)
ffmpeg (the tool), of course! :)
Ronald
__
Hi,
On Wed, Sep 14, 2016 at 12:29 PM, Carl Eugen Hoyos
wrote:
> Hi!
>
> 2016-09-14 18:05 GMT+02:00 Ronald S. Bultje :
> >
> > On Wed, Sep 14, 2016 at 12:01 PM, Carl Eugen Hoyos wrote:
> >
> >> 2016-09-12 12:52 GMT+02:00 Carl Eugen Hoyos :
> >>
>
Hi,
On Wed, Sep 14, 2016 at 12:04 PM, Carl Eugen Hoyos
wrote:
> 2016-09-14 17:59 GMT+02:00 Michael Niedermayer :
> > On Wed, Sep 14, 2016 at 05:34:05PM +0200, Carl Eugen Hoyos wrote:
> >> 2016-09-12 20:58 GMT+02:00 Josh de Kock :
> >> > From: Marton Balint
> >> >
> >> > Depends on the other SDL
Hi,
On Wed, Sep 14, 2016 at 12:01 PM, Carl Eugen Hoyos
wrote:
> 2016-09-12 12:52 GMT+02:00 Carl Eugen Hoyos :
>
> > Attached patch "fixes" ticket #5829, I am happy if a better
> > solution can be found.
>
> Ping.
What makes you believe this is not the right solution? As in: why was the
rogue t
Hi,
On Mon, Sep 12, 2016 at 6:01 AM, Paul B Mahol wrote:
> On 9/12/16, Thilo Borgmann wrote:
> > Hi,
> >
> > these are the resulting notes we've taken during the FFmpeg technical
> > discussion
> > during VDD 2016. We've ended up with two slides on the board and compn
> took
> > pictures of the
Hi,
On Mon, Sep 12, 2016 at 1:46 PM, Ronald S. Bultje
wrote:
> Hi,
>
> On Mon, Sep 12, 2016 at 1:44 PM, Vittorio Giovara <
> vittorio.giov...@gmail.com> wrote:
>
>> Allows to use values returned from API and from ffprobe directly.
>>
>> Signed-off-by: V
801 - 900 of 1999 matches
Mail list logo
