Hi Ngassa,
On Sun, Sep 13, 2015 at 10:33 PM, Ngassa Finjap wrote:
> 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. ]
I am glad to hear that.
>
> IMHO, It's fine leaving di
I missed a very very important point from the summary I wrote.
Action Item:
Raynald: He will write a news entry about last Outreachy project.
Also, thanking Samsung to fund
at least two interns in the past rounds. THANK YOU SAMSUNG!
I am terribly sorry for missing this!! I was super nervous
Hi all,
What is ffmpeg's policy on "necro-bumping" old patches? Or more
precisely, what is the policy of requesting a patch to be merged where
all objections raised have been addressed via discussion/updated
patches, and which have not been merged in over 2 weeks due to unknown
reasons?
In partic
On Mon, Sep 14, 2015 at 5:26 PM, Lou Logan wrote:
> Signed-off-by: Lou Logan
> ---
> README.md | 6 ++
> 1 file changed, 6 insertions(+)
>
> diff --git a/README.md b/README.md
> index 58e1eff..962cef3 100644
> --- a/README.md
> +++ b/README.md
> @@ -40,3 +40,9 @@ Coding examples are availabl
On Mon, Sep 7, 2015 at 10:10 AM, Ganesh Ajjanagadde
wrote:
> Signed-off-by: Ganesh Ajjanagadde
> ---
> libavfilter/vf_vidstabdetect.c | 60
> +-
> 1 file changed, 30 insertions(+), 30 deletions(-)
>
> diff --git a/libavfilter/vf_vidstabdetect.c b/libavfil
On 9/14/2015 7:49 PM, Carl Eugen Hoyos wrote:
> But nobody wants to send a patch with an updated commit message afaict.
How is that important? If you're talking about stating somewhere that
we're dropping ABI compatibility then the correct place is changelog,
RELEASE_NOTES and/or APIChanges, not a
On Mon, Sep 14, 2015 at 7:46 PM, Timothy Gu wrote:
> ---
> configure | 6 +-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/configure b/configure
> index da18e70..3dfbb91 100755
> --- a/configure
> +++ b/configure
> @@ -425,7 +425,10 @@ if test -t 1 && which tput >/dev/null
---
configure | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/configure b/configure
index da18e70..3dfbb91 100755
--- a/configure
+++ b/configure
@@ -425,7 +425,10 @@ if test -t 1 && which tput >/dev/null; then
error_color=$(tput setaf 1)
reset_color=$(tp
On Tue, Sep 15, 2015 at 12:49:31AM +0200, Carl Eugen Hoyos wrote:
> On Monday 14 September 2015 04:31:56 pm Michael Niedermayer wrote:
> > On Mon, Sep 14, 2015 at 01:16:34AM +0200, Carl Eugen Hoyos wrote:
> > > On Monday 14 September 2015 12:48:27 am Michael Niedermayer wrote:
> > > > the entries i
On 09/13/2015 11:48 PM, Michael Niedermayer wrote:
>> - What is "keyframe"?
> a random access point
I'm not sure what your answer means.
I understand that "A keyframe" is a random access point. The flag in
ffprobe's output seems to always be "1".
I thought it might be the same as "intra" in FFV1.3
I wanted to check what happens if someone uses an invalid parameter
combination:
"-c:v ffv1 -level 1 -slices 2"
I expected an error message about invalid slice number, but the code
selected FFV1.2:
"[ffv1 @ 0x391b060] Version 2 needed for requested features but version
2 is experimental and not e
On 09/14/2015 12:25 AM, Michael Niedermayer wrote:
> the encoder chooses the lowest version that supports the requested
> features well to maximize compatibility
Thanks for the explanation.
Sounds reasonable.
If I read [1] correcly, FFV1.0 does not store "bits_per_raw_sample".
I'd be interested i
On Monday 14 September 2015 04:31:56 pm Michael Niedermayer wrote:
> On Mon, Sep 14, 2015 at 01:16:34AM +0200, Carl Eugen Hoyos wrote:
> > On Monday 14 September 2015 12:48:27 am Michael Niedermayer wrote:
> > > the entries in avcodec_options are wrong
> >
> > New patch attached.
>
> [...]
>
> > di
On Mon, Sep 14, 2015 at 01:26:34PM -0800, Lou Logan wrote:
> Signed-off-by: Lou Logan
> ---
> README.md | 6 ++
> 1 file changed, 6 insertions(+)
LGTM
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
No human being will ever know the Truth, for even if
On Thu, Sep 10, 2015 at 11:12:14AM -0500, Rodger Combs wrote:
> Specifically:
> - Skip writing drawings as text
> - Parse \h correctly
> - Handle comments and unknown tags correctly
> ---
do you have a testcase for these ?
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC7870
On 9/5/2015 8:13 PM, Henrik Gramner wrote:
> ---
> libavcodec/v210enc.c | 15 +---
> libavcodec/v210enc.h | 2 +
> tests/checkasm/Makefile | 1 +
> tests/checkasm/checkasm.c | 3 ++
> tests/checkasm/checkasm.h | 1 +
> tests/checkasm/v210enc.c | 94
> +
On Thu, Sep 10, 2015 at 11:12:15AM -0500, Rodger Combs wrote:
> ---
> libavutil/avstring.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
applied
thanks
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Good people do not need laws to tell them to a
Signed-off-by: Lou Logan
---
README.md | 6 ++
1 file changed, 6 insertions(+)
diff --git a/README.md b/README.md
index 58e1eff..962cef3 100644
--- a/README.md
+++ b/README.md
@@ -40,3 +40,9 @@ Coding examples are available in the **doc/examples**
directory.
FFmpeg codebase is mainly LGP
This fixes cases where the shifted number is 64, but we shifted non-
zero numbers away in the shift. The change makes behaviour consistent
with libvpx.
---
libavcodec/vp9.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libavcodec/vp9.c b/libavcodec/vp9.c
index a357a5f..f1183e
This commit adds an error trace when jitter buffer
is full. It helps to understand leading decoding issues.
Signed-off-by: Eloi BAIL
---
libavformat/rtpdec.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/libavformat/rtpdec.c b/libavformat/rtpdec.c
index fee9547..225b77e 100644
--- a/lib
This commit print as AV_LOG_INFO the jitter buffer
size. It might be the default value or the value set by application.
Signed-off-by: Eloi BAIL
---
libavformat/rtpdec.c | 4
1 file changed, 4 insertions(+)
diff --git a/libavformat/rtpdec.c b/libavformat/rtpdec.c
index 225b77e..de01403 100
This patchset adds information about jitter buffer used in rtpdec.
The first patch prints as error when jitter buffer is full.
The second patch prints as information jitter buffer size set by default in
ffmpeg headers or by application.
Both traces are helpful to know the origin of decoding issues
L'octidi 28 fructidor, an CCXXIII, Ganesh Ajjanagadde a écrit :
> Looks mostly good to me. One thing I think that should be clarified is
> the meaning of "linear combination" - I assume you meant a non-trivial
> (exclude all zeros) linear combination over the nonnegative integers?
Thanks. You are
On Mon, Sep 14, 2015 at 11:53 AM, Nicolas George wrote:
> L'octidi 28 fructidor, an CCXXIII, Nicolas George a écrit :
>> I have been thinking of a practical proposal myself, I will word it and post
>> it shortly.
>
> Here it is. Please comment.
Looks mostly good to me. One thing I think that shou
L'octidi 28 fructidor, an CCXXIII, Nicolas George a écrit :
> I have been thinking of a practical proposal myself, I will word it and post
> it shortly.
Here it is. Please comment.
> I strongly think that we will able to reach unanimous consensus about the
> members of the second stage list, and
On Mon, Sep 14, 2015 at 05:34:27PM +0200, Michael Niedermayer wrote:
> On Mon, Sep 14, 2015 at 05:27:01PM +0200, Michael Niedermayer wrote:
> > On Sat, Sep 12, 2015 at 07:07:53PM -0400, Alex Agranovsky wrote:
> > > Attached.
> > >
> > > --
> > > Alex Agranovsky
> > > Sighthound, Inc
> > > www.sig
On Mon, Sep 14, 2015 at 05:27:01PM +0200, Michael Niedermayer wrote:
> On Sat, Sep 12, 2015 at 07:07:53PM -0400, Alex Agranovsky wrote:
> > Attached.
> >
> > --
> > Alex Agranovsky
> > Sighthound, Inc
> > www.sighthound.com
> >
> > On September 12, 2015 at 5:41:56 PM, Michael Niedermay
On Sat, Sep 12, 2015 at 07:07:53PM -0400, Alex Agranovsky wrote:
> Attached.
>
> --
> Alex Agranovsky
> Sighthound, Inc
> www.sighthound.com
>
> On September 12, 2015 at 5:41:56 PM, Michael Niedermayer (michae...@gmx.at)
> wrote:
>
> On Sat, Sep 12, 2015 at 05:10:06PM -0400, Alex A
On Mon, Sep 14, 2015 at 05:00:54PM +0200, Michael Niedermayer wrote:
> On Sun, Sep 13, 2015 at 05:09:50PM -0400, Alex Agranovsky wrote:
> > A slightly improved version …
> >
> >
> > On September 13, 2015 at 4:56:21 PM, Alex Agranovsky (a...@sighthound.com)
> > wrote:
> >
> >
>
> > mpjpegdec.
On Sun, Sep 13, 2015 at 05:09:50PM -0400, Alex Agranovsky wrote:
> A slightly improved version …
>
>
> On September 13, 2015 at 4:56:21 PM, Alex Agranovsky (a...@sighthound.com)
> wrote:
>
>
> mpjpegdec.c | 32 +---
> 1 file changed, 13 insertions(+), 19 deletio
On Mon, Sep 14, 2015 at 01:16:34AM +0200, Carl Eugen Hoyos wrote:
> On Monday 14 September 2015 12:48:27 am Michael Niedermayer wrote:
> > the entries in avcodec_options are wrong
>
> New patch attached.
[...]
> diff --git a/libavcodec/options_table.h b/libavcodec/options_table.h
> index d6a5c69
On Fri, Sep 11, 2015 at 03:16:16PM +0200, Nedeljko Babic wrote:
> Code in aaccoder_mips.c was not synced with changes in aaccoder.c for
> some time.
>
> That was cause for some fate-aac tests failing.
>
> This patch fixes the problems.
>
> Optimizations disabled in 933309a are enabled again.
>
Yes you're right, another typo.
Fix by attached patch (Based on Timo's branch, others seem fine to me).
Agatha Hu
Applied and merged, thanks.
Timo
signature.asc
Description: OpenPGP digital signature
___
ffmpeg-devel mailing list
ffmpeg-devel
2015-09-14 18:54 GMT+08:00 Nicolas George :
> L'octidi 28 fructidor, an CCXXIII, Zhang Rui a écrit :
>> I'd like to know if this API-change could happen, since it will break
>> many things.
>
> It depends on the decision about ABI compatibility, that itself depends on
> the decision about the decis
Hi,
On Tue, Sep 1, 2015 at 8:33 AM, Paul B Mahol wrote:
> Signed-off-by: Paul B Mahol
> ---
> libavfilter/avf_showcqt.c | 16 ++--
> 1 file changed, 14 insertions(+), 2 deletions(-)
>
> diff --git a/libavfilter/avf_showcqt.c b/libavfilter/avf_showcqt.c
> index 85f9ea9..a70c4b0 1006
On Mon, Sep 14, 2015 at 04:23:58PM +0700, Muhammad Faiz wrote:
>
> From c1b58d43c8940efcdea3e30d91d8fde0a0ab6551 Mon Sep 17 00:00:00 2001
> From: Muhammad Faiz
> Date: Sun, 13 Sep 2015 21:52:17 +0700
> Subject: [PATCH] avfilter/avf_showcqt: change fft left-right separation
applied with slightly
L'octidi 28 fructidor, an CCXXIII, Zhang Rui a écrit :
> I'd like to know if this API-change could happen, since it will break
> many things.
It depends on the decision about ABI compatibility, that itself depends on
the decision about the decision process.
Assuming we will stop ABI compatibility
2015-09-14 17:48 GMT+08:00 Zhang Rui :
> URLs longer than 1024 could be truncated by AVFormatContext.
> The field filename[1024] should be replaced with allocated string in future.
I'd like to know if this API-change could happen, since it will break
many things.
And there is one direct usage of
URLs longer than 1024 could be truncated by AVFormatContext.
The field filename[1024] should be replaced with allocated string in future.
---
ffmpeg.c | 8 +++
ffmpeg_opt.c | 8 +++
ffplay.c | 20 +-
ffpr
From c1b58d43c8940efcdea3e30d91d8fde0a0ab6551 Mon Sep 17 00:00:00 2001
From: Muhammad Faiz
Date: Sun, 13 Sep 2015 21:52:17 +0700
Subject: [PATCH] avfilter/avf_showcqt: change fft left-right separation
---
libavfilter/avf_showcqt.c | 56 ++-
1 file cha
On 13.09.2015 19:13, Peter B. wrote:
libavcodec/ffv1enc.c |1 +
1 file changed, 1 insertion(+)
diff --git a/libavcodec/ffv1enc.c b/libavcodec/ffv1enc.c
index 265ced1..d210692 100644
--- a/libavcodec/ffv1enc.c
+++ b/libavcodec/ffv1enc.c
@@ -1345,6 +1345,7 @@ static av_cold int encode_close(A
L'octidi 28 fructidor, an CCXXIII, Michael Niedermayer a écrit :
> saying "no" to a candidate here does not require prior problems or
> hate between the people but it will lead to that afterwards at least
> to some extend. very little in some, quite a bit in others.
> people have different points o
42 matches
Mail list logo
