On 9 September 2015 at 06:53, Ganesh Ajjanagadde wrote:
> On Tue, Sep 8, 2015 at 4:22 PM, Hendrik Leppkes
> wrote:
> > On Tue, Sep 8, 2015 at 9:17 PM, Ganesh Ajjanagadde
> > wrote:
> >> Previous color support relies on existence of tput.
> >> Unfortunately, tput is not available on windows.
> >
Hi,
as discussed in the last IRC meeting, we settle some simple criteria
to define what an active developer is, based on the commit count.
We are aware that such metrics are flawed in many ways, but since we
needed to converge on some simple measurable criteria, we decided to
adopt this one.
We
On Sun, Sep 13, 2015 at 11:33 AM, Stefano Sabatini wrote:
> Hi,
>
> as discussed in the last IRC meeting, we settle some simple criteria
> to define what an active developer is, based on the commit count.
>
> We are aware that such metrics are flawed in many ways, but since we
> needed to converge
Le septidi 27 fructidor, an CCXXIII, Ganesh Ajjanagadde a écrit :
> I assume changing the metric if and when a merge happens from libav is
> going to be handled by the first voting committee.
The idea was to have an initial list without possible objections. It is
expected that some of the first vo
Hi :)
I'm having difficulties implement FFV1 lossless FATE tests in a way that
seems more appropriate.
I'd be grateful for advice how to deal with this:
I'd rather use "framecrc" instead of the "enc_dec" method used in
vodec.mak. Yet, the usage of framecrc in the tests for other lossless
codecs i
Hi.
I just saw that "ffmpeg --help encoder=ffv1 full" only lists the
"slicecrc" parameter option.
I'd like to add the other options to the help as well.
The attached patch adds explanation for "-coder".
I've read up on AVOption Struct Reference [1] and read other source
files, but the usage of s
On Sun, Sep 13, 2015 at 06:11:17PM +0200, Nicolas George wrote:
> Le septidi 27 fructidor, an CCXXIII, Ganesh Ajjanagadde a écrit :
> > I assume changing the metric if and when a merge happens from libav is
> > going to be handled by the first voting committee.
>
> The idea was to have an initial
Hello again :)
I've just noticed that the output of "ffprobe -debug 1" for FFV1 files
has different labels for same parameters in different versions.
For example:
== FFV1.1:
[ffv1 @ 0x3a8ab80] ver:1 keyframe:1 coder:0 ec:0 slices:1 bps:8
== FFV1.3:
[ffv1 @ 0x31584e0] global: ver:3.4, coder:0, c
Hello again :)
I've just noticed that by default, FFV1 chooses version "0".
I thought it would be "1".
When adding "-level 1" it properly shows "ver:1".
(and a proper value for "bps")
== For example:
Source video: https://media.xiph.org/video/derf/y4m/football_422_ntsc.y4m
$ ffmpeg -i input.a
The function is automatically called.
Signed-off-by: Paul B Mahol
---
libavcodec/dxv.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/libavcodec/dxv.c b/libavcodec/dxv.c
index e20e940..e375734 100644
--- a/libavcodec/dxv.c
+++ b/libavcodec/dxv.c
@@ -397,8 +397,6 @@ static int dxv_decode(AV
0001-mpjpeg-probe-should-require-same-constraints-as-pack.patch
Description: Binary data
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
A slightly improved version …
On September 13, 2015 at 4:56:21 PM, Alex Agranovsky (a...@sighthound.com)
wrote:
0001-mpjpeg-probe-should-require-same-constraints-as-pack.patch
Description: Binary data
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmp
On Sunday 13 September 2015 12:30:20 am Michael Niedermayer wrote:
> On Sat, Sep 12, 2015 at 07:52:42PM +0200, Carl Eugen Hoyos wrote:
> > Hi!
> >
> > Attached is a new patch that should be ready to be applied
> > no matter if we drop compatibility or not.
> >
> > Please comment (quickly if possib
On Sat, Sep 12, 2015 at 01:55:03PM +, Paul B Mahol wrote:
> The function is automatically called.
>
> Signed-off-by: Paul B Mahol
> ---
> libavcodec/dxv.c | 2 --
> 1 file changed, 2 deletions(-)
LGTM
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Rewrit
On Sun, Sep 13, 2015 at 09:11:28PM +0200, Peter B. wrote:
> Hello again :)
>
> I've just noticed that the output of "ffprobe -debug 1" for FFV1 files
> has different labels for same parameters in different versions.
>
> For example:
>
> == FFV1.1:
> [ffv1 @ 0x3a8ab80] ver:1 keyframe:1 coder:0 ec
On Sun, Sep 13, 2015 at 09:25:17PM +0200, Peter B. wrote:
> Hello again :)
>
> I've just noticed that by default, FFV1 chooses version "0".
> I thought it would be "1".
>
> When adding "-level 1" it properly shows "ver:1".
> (and a proper value for "bps")
>
>
> == For example:
>
> Source video
Le septidi 27 fructidor, an CCXXIII, Michael Niedermayer a écrit :
> Having a team vote about members of the team can be problematic,
>
> For example if one member votes against another, it wont help
> team spirit and social relations.
If two people do not get along to the point that one would vo
On Sun, Sep 13, 2015 at 11:19:00PM +0200, Carl Eugen Hoyos wrote:
> On Sunday 13 September 2015 12:30:20 am Michael Niedermayer wrote:
> > On Sat, Sep 12, 2015 at 07:52:42PM +0200, Carl Eugen Hoyos wrote:
> > > Hi!
> > >
> > > Attached is a new patch that should be ready to be applied
> > > no mat
On Monday 14 September 2015 12:48:27 am Michael Niedermayer wrote:
> the entries in avcodec_options are wrong
New patch attached.
Thank you, Carl Eugen
diff --git a/doc/APIchanges b/doc/APIchanges
index 958035c..415463a 100644
--- a/doc/APIchanges
+++ b/doc/APIchanges
@@ -15,6 +15,10 @@ libavutil
On Mon, Sep 14, 2015 at 12:36:29AM +0200, Nicolas George wrote:
> Le septidi 27 fructidor, an CCXXIII, Michael Niedermayer a écrit :
> > Having a team vote about members of the team can be problematic,
> >
> > For example if one member votes against another, it wont help
> > team spirit and social
在 2015/9/12 11:18, Philip Langdale 写道:
On Fri, 11 Sep 2015 17:32:06 +0800
Agatha Hu wrote:
From: ahu
---
libavcodec/nvenc.c | 59
+++- 1 file changed,
54 insertions(+), 5 deletions(-)
diff --git a/libavcodec/nvenc.c b/libavcodec/nvenc.c
ind
On Tue, Sep 1, 2015 at 7:33 PM, Paul B Mahol wrote:
> Signed-off-by: Paul B Mahol
> ---
> libavfilter/avf_showcqt.c | 16 ++--
> 1 file changed, 14 insertions(+), 2 deletions(-)
>
LGTM
thanks
___
ffmpeg-devel mailing list
ffmpeg-devel@ff
Hello everyone,
Here is the meeting summary for yesterday meeting (Item No.5 about Outreachy).
I also added possible future agenda. And please let me know if you
have any questions. Also, I will probably start a separate mailing
list for just regarding outreachy related issues, unless I should kee
Hi Yayoi,
Thank you for writing a summary of the IRC Meeting which took place
yesterday regarding the upcoming Outreachy program. Yaaay! ^_^ [ Sadness
levels drop. ]
IMHO, It's fine leaving discussions concerning Outreachy on this mailing
list since it also concerns development of FFmpeg. Please
24 matches
Mail list logo
