Hi!
Attached patch silences two warnings when compiling with gcc-7:
libavcodec/utvideodec.c:242:107: warning: ‘~’ on a boolean expression
[-Wbool-operation]
const int cmask = c->interlaced ? ~(1 + 2 * (!plane_no &&
c->avctx->pix_fmt == AV_PIX_FMT_YUV420P)) : ~(!plane_no &&
c->avctx->pix_fmt
Hi,
On Sat, Oct 7, 2017 at 7:14 PM, Carl Eugen Hoyos wrote:
> 2017-05-05 1:32 GMT+02:00 Carl Eugen Hoyos :
> > Hi!
> >
> > It may be better to disable the warning.
>
> Ping, one of the two patches should be applied,
> we currently have one vote for each.
>
On Sat, Oct 07, 2017 at 11:39:40AM -0400, Ronald S. Bultje wrote:
> Hi,
>
> On Sat, Oct 7, 2017 at 6:25 AM, Michael Niedermayer
> wrote:
>
> > On Sat, Oct 07, 2017 at 12:12:15PM +0200, Michael Niedermayer wrote:
> > > > > On Fri, Oct 06, 2017 at 10:03:16AM -0400,
Hi,
On Sat, Oct 7, 2017 at 7:05 PM, Carl Eugen Hoyos wrote:
> Hi!
>
> Attached patch silences two warnings when compiling with gcc-7:
> libavcodec/utvideodec.c:242:107: warning: ‘~’ on a boolean expression
> [-Wbool-operation]
> const int cmask = c->interlaced ? ~(1 + 2
2017-05-05 1:32 GMT+02:00 Carl Eugen Hoyos :
> Hi!
>
> It may be better to disable the warning.
Ping, one of the two patches should be applied,
we currently have one vote for each.
Carl Eugen
___
ffmpeg-devel mailing list
On Sat, Oct 07, 2017 at 12:04:02AM +0200, Michael Niedermayer wrote:
> On Thu, Oct 05, 2017 at 01:37:27PM +0200, Matthias Hunstock wrote:
> > There is still a StartCom certificate in place, which is refused from
> > Chrome and soon other browsers.
> >
> > Any help appreciated to also move that
One possibility attached.
Please comment, Carl Eugen
From 0876a93917c8fe06a3d9b748c39e4f643c2ecd02 Mon Sep 17 00:00:00 2001
From: Carl Eugen Hoyos
Date: Sat, 7 Oct 2017 15:59:22 +0200
Subject: [PATCH] lavfi: Rename local variables "main" as "master".
Silences several
On 10/7/2017 11:02 AM, Carl Eugen Hoyos wrote:
> One possibility attached.
>
> Please comment, Carl Eugen
>
>
> 0001-lavfi-Rename-local-variables-main-as-master.patch
>
>
> From 0876a93917c8fe06a3d9b748c39e4f643c2ecd02 Mon Sep 17 00:00:00 2001
> From: Carl Eugen Hoyos
>
On 10/7/17, James Almer wrote:
> On 10/6/2017 7:09 PM, wm4 wrote:
>> On Fri, 6 Oct 2017 18:02:44 -0300
>> James Almer wrote:
>>
>>> On 10/6/2017 5:44 PM, Paul B Mahol wrote:
On 10/6/17, Michael Niedermayer wrote:
> On Fri,
On 10/7/17, Hendrik Leppkes wrote:
> On Sat, Oct 7, 2017 at 11:24 AM, Nicolas George wrote:
>> Le sextidi 16 vendemiaire, an CCXXVI, Paul B Mahol a ecrit :
>>> There is metadata for each frame added and it can be used right now.
>>
>> Then we can remove that
On Sat, Oct 07, 2017 at 12:12:15PM +0200, Michael Niedermayer wrote:
> On Sat, Oct 07, 2017 at 10:09:45AM +0200, Paul B Mahol wrote:
> > On 10/7/17, James Almer wrote:
> > > On 10/6/2017 7:09 PM, wm4 wrote:
> > >> On Fri, 6 Oct 2017 18:02:44 -0300
> > >> James Almer
On Sat, Oct 07, 2017 at 01:48:16PM +0200, Clément Bœsch wrote:
> > Subject: Re: [FFmpeg-devel] [PATCH] Fix for paletteuse to support
> > transparency
>
> "lavf/paletteuse: add support for transparency"
>
Sorry, "lavfi", not "lavf".
Also, can you add the trac ticket reference for this?
[...]
On Sat, Oct 07, 2017 at 10:09:45AM +0200, Paul B Mahol wrote:
> On 10/7/17, James Almer wrote:
> > On 10/6/2017 7:09 PM, wm4 wrote:
> >> On Fri, 6 Oct 2017 18:02:44 -0300
> >> James Almer wrote:
> >>
> >>> On 10/6/2017 5:44 PM, Paul B Mahol wrote:
> On
> Subject: Re: [FFmpeg-devel] [PATCH] Fix for paletteuse to support transparency
"lavf/paletteuse: add support for transparency"
On Fri, Oct 06, 2017 at 04:59:55PM -0400, Bjorn Roche wrote:
> ---
> libavfilter/vf_paletteuse.c | 175
>
> 1 file
2017-10-07 16:04 GMT+02:00 James Almer :
> On 10/7/2017 11:02 AM, Carl Eugen Hoyos wrote:
>> One possibility attached.
>>
>> Please comment, Carl Eugen
>>
>>
>> 0001-lavfi-Rename-local-variables-main-as-master.patch
>>
>>
>> From 0876a93917c8fe06a3d9b748c39e4f643c2ecd02 Mon Sep
2017-10-07 17:19 GMT+02:00 Michael Niedermayer :
> On Sat, Aug 26, 2017 at 11:53:46AM +0200, Carl Eugen Hoyos wrote:
>> Hi!
>>
>> Attached patch follows RFC 3551, a followup patch adds little-endian
>> G.726 with the old MIME-type.
>>
>> Please comment, Carl Eugen
>
>>
2017-10-07 17:20 GMT+02:00 Michael Niedermayer :
> On Sat, Aug 26, 2017 at 11:55:00AM +0200, Carl Eugen Hoyos wrote:
>> Hi!
>>
>> Attached patch adds little-endian G.726 support to rtpenc, using the
>> MIME-type suggested by RFC 3551.
>>
>> Please comment, Carl Eugen
>
>>
Lately ffmpeg supports gray9/10/12 pixel formats.
This patch adds gray9/10/12 pixel formats to y4m.
It also moves gray16 to 'strict -1' section.
Please review.
Mateusz
From f2b31ef66931e02a355e3140d47b17f0d307dec7 Mon Sep 17 00:00:00 2001
From: Mateusz
Date: Sat, 7
2017-10-02 14:38 GMT+02:00 Carl Eugen Hoyos :
> Hi!
>
> Attached patch fixes the following warning:
> libavformat/protocols.c:100:7: warning: assignment discards ‘const’
> qualifier from pointer target type
Ping, better suggestions very welcome.
Carl Eugen
On 10/6/17, Marton Balint wrote:
>
>
> On Wed, 4 Oct 2017, Marton Balint wrote:
>
>> Otherwise the frame size of the codec is not set in the buffersink.
>>
>> Fixes ticket #6603 and the following simpler case:
>>
>> ffmpeg -c aac -filter_complex "sine=d=0.1,asetnsamples=1025"
06.10.2017 22:10, Marton Balint пише:
On Thu, 5 Oct 2017, Maksym Veremeyenko wrote:
29.09.2017 0:20, Carl Eugen Hoyos пише:
Hi!
I don't have decklink hardware but I assume it never outputs actual
transparency.
Or does it?
it outputs or use internal keyer to put it over passthrow SDI
On Wed, Oct 4, 2017 at 12:48 AM, Marton Balint wrote:
> Otherwise the frame size of the codec is not set in the buffersink.
>
> Fixes ticket #6603 and the following simpler case:
>
> ffmpeg -c aac -filter_complex "sine=d=0.1,asetnsamples=1025" out.aac
>
> Signed-off-by: Marton
Le quintidi 15 vendémiaire, an CCXXVI, Ronald S. Bultje a écrit :
> The same mechanism is present in ssim/psnr filters.
This is true. But how do you think it came to happen?
It happened because somebody wanted some feature for their use and
implemented it (so far, very good), and since it
Le quintidi 15 vendémiaire, an CCXXVI, Sasi Inguva a écrit :
> Signed-off-by: Sasi Inguva
> ---
> libavfilter/avfilter.c | 8
> 1 file changed, 4 insertions(+), 4 deletions(-)
Thanks, pushed.
Regards,
--
Nicolas George
signature.asc
Description: Digital
Le sextidi 16 vendémiaire, an CCXXVI, Paul B Mahol a écrit :
> There is metadata for each frame added and it can be used right now.
Then we can remove that file-writing option. Thanks for the
clarification.
Regards,
--
Nicolas George
signature.asc
Description: Digital signature
On Fri, 6 Oct 2017, James Almer wrote:
On 10/6/2017 8:20 PM, James Almer wrote:
On 10/6/2017 5:20 PM, Marton Balint wrote:
Signed-off-by: Marton Balint
---
Makefile | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/Makefile b/Makefile
index
On 10/7/17, Nicolas George wrote:
> Le quintidi 15 vendemiaire, an CCXXVI, Ronald S. Bultje a ecrit :
>> The same mechanism is present in ssim/psnr filters.
>
> This is true. But how do you think it came to happen?
>
> It happened because somebody wanted some feature for their
Le sextidi 16 vendémiaire, an CCXXVI, Paul B Mahol a écrit :
> No.
Very constructive, thanks.
--
Nicolas George
signature.asc
Description: Digital signature
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
Now works with --disable-stripping.
Signed-off-by: Marton Balint
---
Makefile | 4
configure | 4
2 files changed, 8 insertions(+)
diff --git a/Makefile b/Makefile
index 4a1253a052..642651d4cc 100644
--- a/Makefile
+++ b/Makefile
@@ -97,8 +97,12 @@ include
On 10/7/17, Nicolas George wrote:
> Le sextidi 16 vendemiaire, an CCXXVI, Paul B Mahol a ecrit :
>> There is metadata for each frame added and it can be used right now.
>
> Then we can remove that file-writing option. Thanks for the
> clarification.
No.
On 10/7/17, Nicolas George wrote:
> Le sextidi 16 vendemiaire, an CCXXVI, Paul B Mahol a ecrit :
>> No.
>
> Very constructive, thanks.
No.
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
On Sat, Oct 7, 2017 at 11:24 AM, Nicolas George wrote:
> Le sextidi 16 vendémiaire, an CCXXVI, Paul B Mahol a écrit :
>> There is metadata for each frame added and it can be used right now.
>
> Then we can remove that file-writing option. Thanks for the
> clarification.
>
If
Hi Martin,
On Sat, Oct 7, 2017 at 11:49 AM, Martin Vignali
wrote:
> 2017-10-07 17:30 GMT+02:00 Ronald S. Bultje :
> > On Sat, Oct 7, 2017 at 10:22 AM, Martin Vignali <
> martin.vign...@gmail.com>
> > wrote:
> > > Patch in attach add a new dsp
> > >
On 10/7/17, Ronald S. Bultje wrote:
> Hi,
>
> On Sat, Oct 7, 2017 at 6:25 AM, Michael Niedermayer
> wrote:
>
>> On Sat, Oct 07, 2017 at 12:12:15PM +0200, Michael Niedermayer wrote:
>> > > > On Fri, Oct 06, 2017 at 10:03:16AM -0400, Ronald S. Bultje
Hello,
Patch in attach add a new dsp
for manipulation of qmat
for now, i move this code inside
for (i = 0; i < 64; i++) {
qmat_luma_scaled [i] = ctx->qmat_luma [i] * qscale;
qmat_chroma_scaled[i] = ctx->qmat_chroma[i] * qscale;
}
i add a special case for qscale == 1
and SSE2,
>
> > IMO, the ffmpeg support is mostly interesting to convert hap
> > file to something else or to check what we can encode with
> > the ffmpeg hap encoder.
>
> I don't disagree (on the contrary), I believe we should make it
> as easy as possible for users to work with it:
> Do you believe that
2017-10-07 16:32 GMT+02:00 Martin Vignali :
>>
>> > IMO, the ffmpeg support is mostly interesting to convert hap
>> > file to something else or to check what we can encode with
>> > the ffmpeg hap encoder.
>>
>> I don't disagree (on the contrary), I believe we should make
2017-10-07 16:30 GMT+02:00 Carl Eugen Hoyos :
> 2017-10-07 16:22 GMT+02:00 Martin Vignali :
>
> > Patch in attach add a new dsp
> > for manipulation of qmat
>
> Is there a measurable effect on overall decoding?
>
> No. I have too much variation using
Hi,
On Sat, Oct 7, 2017 at 5:09 AM, Nicolas George wrote:
> Le quintidi 15 vendémiaire, an CCXXVI, Ronald S. Bultje a écrit :
> > The same mechanism is present in ssim/psnr filters.
>
> This is true. But how do you think it came to happen?
>
Calm down guys, I said in the next
2017-10-07 16:22 GMT+02:00 Martin Vignali :
> Patch in attach add a new dsp
> for manipulation of qmat
Is there a measurable effect on overall decoding?
Thank you, Carl Eugen
___
ffmpeg-devel mailing list
2017-10-01 18:23 GMT+02:00 Carl Eugen Hoyos :
> 2017-09-27 18:08 GMT+02:00 Carl Eugen Hoyos :
>
>> The existing amr demuxer does not allow reading streams,
>> it requires the 3GPP-conforming file header.
>> Attached patch allows reading amrnb and amrwb from
2017-10-07 16:52 GMT+02:00 Martin Vignali :
> 2017-10-07 16:30 GMT+02:00 Carl Eugen Hoyos :
>
>> 2017-10-07 16:22 GMT+02:00 Martin Vignali :
>>
>> > Patch in attach add a new dsp
>> > for manipulation of qmat
>>
>> Is there a
On Sat, Aug 26, 2017 at 11:55:00AM +0200, Carl Eugen Hoyos wrote:
> Hi!
>
> Attached patch adds little-endian G.726 support to rtpenc, using the
> MIME-type suggested by RFC 3551.
>
> Please comment, Carl Eugen
> rtpenc.c |2 ++
> sdp.c|8
> 2 files changed, 10
On Sat, Aug 26, 2017 at 11:53:46AM +0200, Carl Eugen Hoyos wrote:
> Hi!
>
> Attached patch follows RFC 3551, a followup patch adds little-endian
> G.726 with the old MIME-type.
>
> Please comment, Carl Eugen
> sdp.c |2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
Hi Martin,
On Sat, Oct 7, 2017 at 10:22 AM, Martin Vignali
wrote:
> Hello,
>
> Patch in attach add a new dsp
> for manipulation of qmat
>
> for now, i move this code inside
>
> for (i = 0; i < 64; i++) {
> qmat_luma_scaled [i] = ctx->qmat_luma [i] * qscale;
>
Hi,
On Sat, Oct 7, 2017 at 6:25 AM, Michael Niedermayer
wrote:
> On Sat, Oct 07, 2017 at 12:12:15PM +0200, Michael Niedermayer wrote:
> > > > On Fri, Oct 06, 2017 at 10:03:16AM -0400, Ronald S. Bultje wrote:
> > > >> I'm open to any alternative method you
2017-10-07 17:30 GMT+02:00 Ronald S. Bultje :
> Hi Martin,
>
> On Sat, Oct 7, 2017 at 10:22 AM, Martin Vignali
> wrote:
>
> > Hello,
> >
> > Patch in attach add a new dsp
> > for manipulation of qmat
> >
> > for now, i move this code inside
> >
> >
On 10/7/17, Mateusz wrote:
> Lately ffmpeg supports gray9/10/12 pixel formats.
>
> This patch adds gray9/10/12 pixel formats to y4m.
>
> It also moves gray16 to 'strict -1' section.
>
> Please review.
>
> Mateusz
>
>
lgtm
___
48 matches
Mail list logo