On 02.03.2018 23:14, wm4 wrote:
On Fri, 2 Mar 2018 22:48:07 +0100
Michael Niedermayer wrote:
On Fri, Mar 02, 2018 at 09:07:06AM +0100, Tobias Rapp wrote:
On 01.03.2018 22:08, Michael Niedermayer wrote:
On Wed, Feb 28, 2018 at 09:47:15AM +0100, Tobias Rapp wrote:
On 27.02.2018 19:03, Michael
On 26.02.2018 17:09, Tobias Rapp wrote:
Signed-off-by: Tobias Rapp
---
fftools/ffmpeg.c | 44
1 file changed, 20 insertions(+), 24 deletions(-)
[...]
Rebased on v1 of the patch and pushed. Thanks for review.
Regards,
Tobias
___
Hello,
I have not received any comment yet on my patchset v3 ("add mono mode" new
feature + 4 fixes including a ticket), does it look good to you, could it be
committed ?
http://ffmpeg.org/pipermail/ffmpeg-devel/2018-February/225494.html
http://ffmpeg.org/pipermail/ffmpeg-devel/2018-February/225
From: Ravindra
---
doc/muxers.texi | 2 ++
libavformat/dashenc.c | 4
2 files changed, 6 insertions(+)
diff --git a/doc/muxers.texi b/doc/muxers.texi
index 3a63da7..cb75c26 100644
--- a/doc/muxers.texi
+++ b/doc/muxers.texi
@@ -264,6 +264,8 @@ of the adaptation sets and a,b,c,d and e
From: Ravindra
---
doc/muxers.texi | 3 +++
libavformat/hlsenc.c | 5 -
2 files changed, 7 insertions(+), 1 deletion(-)
diff --git a/doc/muxers.texi b/doc/muxers.texi
index c156ec0..3a63da7 100644
--- a/doc/muxers.texi
+++ b/doc/muxers.texi
@@ -964,6 +964,9 @@ publishing it repeatedly
Hello,
Thanks for the review. I've made changes according to your guidance.
It would be great to know if the community will go on with our intention
of adding reinterlace as a alternative for tinterlace.
That being said, here is the new patch.
Regards,
-Vasile Toncu
From 7419be6fa213383ed
On 3/5/18, Vasile Toncu wrote:
> Hello,
>
> Thanks for the review. I've made changes according to your guidance.
>
> It would be great to know if the community will go on with our intention
> of adding reinterlace as a alternative for tinterlace.
>
> That being said, here is the new patch.
As alr
2018-03-05 12:37 GMT+01:00, Paul B Mahol :
> On 3/5/18, Vasile Toncu wrote:
>> Hello,
>>
>> Thanks for the review. I've made changes according to your guidance.
>>
>> It would be great to know if the community will go on with our intention
>> of adding reinterlace as a alternative for tinterlace.
On 3/5/18, Carl Eugen Hoyos wrote:
> 2018-03-05 12:37 GMT+01:00, Paul B Mahol :
>> On 3/5/18, Vasile Toncu wrote:
>>> Hello,
>>>
>>> Thanks for the review. I've made changes according to your guidance.
>>>
>>> It would be great to know if the community will go on with our intention
>>> of adding
libx264 encoder uses AVFrame.pict_type (if provided by user) to use this
frame as key frame.
For openh264 encoder this functionality is missing, pict_type simply being
ignored.
Attached patch fixes it.
Valery
From f95943165c91dac13a644365f775aff3dd9edb11 Mon Sep 17 00:00:00 2001
From: vkot
Date
Kieran Kunhya (2018-03-05):
> Ladies and Gentleman I present you exhibit A, Michael
Wait, what? "exhibit"? When did this thread become a trial?
Regards,
--
Nicolas George
signature.asc
Description: Digital signature
___
ffmpeg-devel mailing list
f
> -Ursprüngliche Nachricht-
> Von: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] Im Auftrag
> von Sven Dueking
> Gesendet: Dienstag, 27. Februar 2018 08:27
> An: 'FFmpeg development discussions and patches'
> Betreff: Re: [FFmpeg-devel] [PATCH] avformat/opensrt: add Haivision
> Op
On Sat, Mar 03, 2018 at 08:19:43PM +, Rostislav Pehlivanov wrote:
> The commit which added those was pushed prematurely before anyone could object
> to illogical suffixes like just m for milliseconds.
What you call illogical is following the same convention as pretty much
all numeric parameter
Hello,
The reinterlace behaves just like the tinterlace and in terms of fps is
basically the same.
The ASM Opts are used with reinterlace only in case of CONFIG_GPL enabled.
There are two new modes, MODE_MERGE_BFF and MODE_MERGE_TFF for which I
have documentation.
Also reinterlace process
On Mon, Mar 05, 2018 at 08:37:10AM +0800, Jun Zhao wrote:
>
>
> On 2018/3/4 6:16, Michael Niedermayer wrote:
> > On Sat, Mar 03, 2018 at 07:10:48PM -0300, James Almer wrote:
> >> On 3/3/2018 6:41 PM, Michael Niedermayer wrote:
> >>> On Fri, Mar 02, 2018 at 08:16:11AM +0800, Jun Zhao wrote:
>
On Tue, Feb 27, 2018, at 6:24 AM, Timo Rothenpieler wrote:
>
> Patch applied.
Could you mention the new repo, and perhaps some simple instructions, on
HWAccelIntro? I've seen a few confused users. I would but I'm not a HW user and
I don't want to add anything incorrect.
_
Here is a patch proposition for https://trac.ffmpeg.org/ticket/7053
Pierre Chatelier
From 7cbc1bd47fb97e3498d92eda9c84144de2c06d01 Mon Sep 17 00:00:00 2001
From: Pierre Chatelier
Date: Mon, 5 Mar 2018 13:57:00 +0100
Subject: [PATCH 1/1] added YUV422-12, -14, -16 bit depth, mono-8, -10, -12,
-16
Am 05.03.2018 um 20:46 schrieb Lou Logan:
On Tue, Feb 27, 2018, at 6:24 AM, Timo Rothenpieler wrote:
Patch applied.
Could you mention the new repo, and perhaps some simple instructions, on
HWAccelIntro? I've seen a few confused users. I would but I'm not a HW user and
I don't want to add an
Hi all.
I am student and my name is Oleg. I work on qualification task for GSoC 2018.
I should implement float-point support to als encoder.
A have some questions:
1)In documentation was written
"The floating-point sequence is modeled by the sum of an integer sequence
multiplied by a constant (A
On Mon, Mar 5, 2018, at 11:07 AM, Timo Rothenpieler wrote:
>
> I tried to do that multiple times already, but trac won't let me login,
> it just eventually runs into a Gateway Timeout if I try.
Weird. I can't duplicate that issue. Is anyone else experiencing this?
If you give me the info I can a
On Mon, Feb 12, 2018 at 9:35 AM, Jacob Trimble wrote:
> On Tue, Jan 30, 2018 at 11:27 AM, Jacob Trimble wrote:
>> On Wed, Jan 24, 2018 at 5:46 PM, Michael Niedermayer
>> wrote:
>>> On Wed, Jan 24, 2018 at 11:43:26AM -0800, Jacob Trimble wrote:
On Mon, Jan 22, 2018 at 7:38 PM, Michael Nieder
On 5 March 2018 at 13:04, Pierre Chatelier wrote:
> Here is a patch proposition for https://trac.ffmpeg.org/ticket/7053
>
> Pierre Chatelier
>
> ___
> ffmpeg-devel mailing list
> ffmpeg-devel@ffmpeg.org
> http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Am 04.03.2018 um 20:15 schrieb Compn:
On Sat, 3 Mar 2018 22:39:45 +0100, Timo Rothenpieler
wrote:
Right now, if someone configures ffmpeg with for example --enable-nvenc they
will
get an error message complaining about missing cuda.
This is very confusing and already has lead people into ins
Am 05.03.2018 um 21:17 schrieb Lou Logan:
On Mon, Mar 5, 2018, at 11:07 AM, Timo Rothenpieler wrote:
I tried to do that multiple times already, but trac won't let me login,
it just eventually runs into a Gateway Timeout if I try.
Weird. I can't duplicate that issue. Is anyone else experiencin
On 3 March 2018 at 16:20, Aurelien Jacobs wrote:
> On Thu, Mar 01, 2018 at 10:46:07PM +, Rostislav Pehlivanov wrote:
> > On 1 March 2018 at 20:45, Aurelien Jacobs wrote
> >
> > >
> > > So what I propose is to rename sbc_delay to sbc_latency (for example),
> > > and to add a opus_latecy using
On 24 February 2018 at 12:05, Aurelien Jacobs wrote:
> On Thu, Feb 22, 2018 at 05:21:57PM +, Rostislav Pehlivanov wrote:
> > On 21 February 2018 at 22:37, Aurelien Jacobs wrote:
> > [...]
> > > +;***
> > > +;void ff_sbc_analyze_
On 5 March 2018 at 16:47, Aurelien Jacobs wrote:
> On Sat, Mar 03, 2018 at 08:19:43PM +, Rostislav Pehlivanov wrote:
> > The commit which added those was pushed prematurely before anyone could
> object
> > to illogical suffixes like just m for milliseconds.
>
> What you call illogical is foll
From 5d28b92d9d164b104e9a47b8183cd7ddedfde366 Mon Sep 17 00:00:00 2001
From: Matt Wolenetz
Date: Mon, 5 Mar 2018 12:36:28 -0800
Subject: [PATCH] lavf/oggparseflac: Free flac extradata before reallocating.
Otherwise ff_alloc_extradata() just leaks any existing allocated
memory.
BUG=789835
Chang
On 3/5/2018 6:54 PM, Matthew Wolenetz wrote:
>
> 0001-lavf-oggparseflac-Free-flac-extradata-before-realloc.patch
>
>
> From 5d28b92d9d164b104e9a47b8183cd7ddedfde366 Mon Sep 17 00:00:00 2001
> From: Matt Wolenetz
> Date: Mon, 5 Mar 2018 12:36:28 -0800
> Subject: [PATCH] lavf/oggparseflac: Free f
On Sun, Feb 11, 2018 at 8:31 PM, Jan Ekström wrote:
> On Sun, Feb 11, 2018 at 7:52 PM, Michael Niedermayer
> wrote:
>>
>> should be ok unless its intended to also restore the MSB
>>
>
> The value seemed to be 10bit and if the pointer is at the position
> right after the picture_start_code, then `
On Sun, Feb 11, 2018 at 4:37 PM, Jan Ekström wrote:
> From: Masaki Tanaka
>
> ---
> libavcodec/mpegvideo_parser.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/libavcodec/mpegvideo_parser.c b/libavcodec/mpegvideo_parser.c
> index 4f554b684e..ecf7c28e72 100644
> --- a/l
This patch seems to be doing the wrong thing and breaking seek tests for us.
As far as I understand , seeking for most containers is based on "decoding
timestamp". Unless AV_SEEK_TO_PTS flag is specified in container, which is
not for most containers and MOV. So if PTS and DTS are like such,
Pts
Accepting 'u' suffix for a time specification is neither intuitive nor
consistent (now that we don't accept m). Also there was a bug in the code
accepting an extra 's' even after 'ms'.
Signed-off-by: Marton Balint
---
libavutil/parseutils.c | 7 +++
1 file changed, 3 insertions(+), 4 deletio
On 01/03/18 05:20, Zhong Li wrote:
> Look_ahead can provide quality improvements, but would better disable it by
> default due to some reasons:
> 1. It is only available for some codecs (e.g. HEVC is not supported) on Intel
>Haswell and plus platforms. Thus means it will be failed on some plat
From 7471c1d223b860c13793abfd93174d1557f77d6f Mon Sep 17 00:00:00 2001
From: Matt Wolenetz
Date: Mon, 5 Mar 2018 15:59:18 -0800
Subject: [PATCH] lavc/vorbisdec: Allow avcodec_open2 to call .close
If there is a decoder initialization failure detected in avcodec_open2
after .init is called, allow
Perhaps true, but there are a ton of paths to ff_alloc_extradata that are
not included in Chromium. Such a wider, general, fix seems more appropriate
to land upstream first with more testing.
For now, this is a particular known case that's occurring in Chromium that
needs fixing.
On Mon, Mar 5, 20
On Fri, 2018-03-02 at 09:23 +0800, Jun Zhao wrote:
>
> On 2018/3/2 6:43, Mark Thompson wrote:
> > On 01/03/18 08:07, Jerome Borsboom wrote:
> > > v1.1->v1.2: Changed ifdefs around vc1_get_INTCOMPFIELD, vc1_get_LUMSCALE2,
> > > and vc1_get_LUMSHIFT2 to av_unused.
> > >
> > > avcodec/vaapi: add fie
Cosmetic refactor
Signed-off-by: James Almer
---
libavformat/utils.c | 26 +++---
1 file changed, 11 insertions(+), 15 deletions(-)
diff --git a/libavformat/utils.c b/libavformat/utils.c
index 31340a484b..3ca1ca2441 100644
--- a/libavformat/utils.c
+++ b/libavformat/utils.c
This prevents leaks in the rare cases the function is called when extradata
already exists.
Signed-off-by: James Almer
---
libavformat/utils.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/libavformat/utils.c b/libavformat/utils.c
index 72531d4185..31340a484b 100644
--- a/libavformat/utils
> -Original Message-
> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf Of Mark
> Thompson
> Sent: Tuesday, February 13, 2018 11:54 AM
> To: FFmpeg development discussions and patches
> Subject: Re: [FFmpeg-devel] [PATCH] lavc/vaapi_encode: Don't pass
> VAConfigAttri
40 matches
Mail list logo
