On Tue, Feb 10, 2015 at 01:27:03PM +0100, wm4 wrote:
Doing this check in avutil_version() is not appropriate. Also, this code
is by default disabled (--assert-level is by default 0). A FATE run with
defaults will never execute the checks.
Move it to the pixelutils test program. Whatever
Hello,
+AV_WB64(y,KE);
+
KE=SP[0][y[0]]^SP[1][y[1]]^SP[2][y[2]]^SP[3][y[3]]^SP[4][y[4]]^SP[5][y[5]]^SP[6][y[6]]^SP[7][y[7]];
+return KE;
have you tried it without the y[] array ?
storing and loading from memory may (or may not) be slower
I have tried without y[] array. And
On Tue, Feb 10, 2015 at 11:53:50AM +, Kevin Wheatley wrote:
Changelog |1 +
libavformat/movenc.c |3 ++-
tests/ref/vsynth/vsynth1-dnxhd-1080i |2 +-
tests/ref/vsynth/vsynth1-dnxhd-1080i-colr |2 +-
On Tue, Feb 10, 2015 at 01:27:02PM +0100, wm4 wrote:
---
Why wasn't this done this way in the first place...
---
libavutil/internal.h | 2 ++
libavutil/pixdesc.h | 2 --
libavutil/utils.c| 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
applied
thanks
[...]
--
Michael
On Tue, Feb 10, 2015 at 11:36:04AM +, Carl Eugen Hoyos wrote:
wm4 nfxjfg at googlemail.com writes:
- * When the pixel format is palettized RGB (AV_PIX_FMT_PAL8),
+ * When the pixel format is palettized ARGB (AV_PIX_FMT_PAL8),
I believe ARGB in this file describes something
that
On Mon, Feb 02, 2015 at 07:43:42AM -0700, Roger Pack wrote:
On 1/31/15, Roger Pack rogerdpa...@gmail.com wrote:
On 1/30/15, Michael Niedermayer michae...@gmx.at wrote:
On Fri, Jan 30, 2015 at 08:55:45AM -0700, Roger Pack wrote:
On 1/30/15, Don Moir donm...@comcast.net wrote:
-
On Mon, Feb 09, 2015 at 06:35:08PM +0100, Clément Bœsch wrote:
[...]
• I added many debug utils (understand: dead code) in palettegen which is
very useful for debugging and error checking. I'd like to keep them if no
one mind. For example, it allows generating pictures such as
On 2/10/15, Reimar Doeffinger reimar.doeffin...@gmx.de wrote:
On 07.02.2015, at 15:51, Paul B Mahol one...@gmail.com wrote:
Signed-off-by: Paul B Mahol one...@gmail.com
---
libavcodec/Makefile | 1 -
libavcodec/allcodecs.c | 1 -
libavcodec/avcodec.h| 1 -
libavcodec/codec_desc.c |
On 2015-02-10 04:19, Mark Reid wrote:
---
configure | 1 +
tests/fate/avformat.mak| 1 +
tests/fate/seek.mak| 2 ++
tests/lavf-regression.sh | 4
tests/ref/lavf/mxf_opatom | 3 +++
tests/ref/seek/lavf-mxf_opatom | 53
On Tue, Feb 10, 2015 at 10:41:46AM +0100, tomas.har...@codemill.se wrote:
On 2015-02-10 04:19, Mark Reid wrote:
---
configure | 1 +
tests/fate/avformat.mak| 1 +
tests/fate/seek.mak| 2 ++
tests/lavf-regression.sh | 4
wm4 nfxjfg at googlemail.com writes:
- * When the pixel format is palettized RGB (AV_PIX_FMT_PAL8),
+ * When the pixel format is palettized ARGB (AV_PIX_FMT_PAL8),
I believe ARGB in this file describes something
that does not depend on the endianess while the
palette (if the documentation
Signed-off-by: Paul B Mahol one...@gmail.com
---
doc/APIchanges | 3 +++
libavcodec/allcodecs.c | 2 ++
libavcodec/avcodec.h| 2 ++
libavcodec/codec_desc.c | 2 ++
libavcodec/version.h| 3 +++
libavcodec/vima.c | 2 ++
6 files changed, 14 insertions(+)
diff --git
On Tue, Feb 10, 2015 at 10:45:46AM +, Kevin Wheatley wrote:
On Tue, Feb 10, 2015 at 10:34 AM, Michael Niedermayer michae...@gmx.at
wrote:
if theres no way to store unknown range then your suggestion sounds
reasonable, can you send a patch?
I'm not aware of a value to specify in the
Also make clear that PAL8 can have alpha.
---
Changed it quite a bit. I just want an official explanation how alpha
works in FFmpeg somewhere on the API. If there are still bits missing,
please tell.
---
libavutil/pixdesc.h | 13 -
libavutil/pixfmt.h | 4 ++--
2 files changed, 14
On Mon, 9 Feb 2015 23:49:00 +0100
Michael Niedermayer michae...@gmx.at wrote:
On Mon, Feb 09, 2015 at 10:33:53PM +0100, wm4 wrote:
Otherwise, you could lose the alpha when handling pixel formats in an
opaque manner (i.e. when you don't special-case PAL8).
The special case for
On Tue, Feb 10, 2015 at 09:08:48AM +, Paul B Mahol wrote:
On 2/10/15, Reimar Doeffinger reimar.doeffin...@gmx.de wrote:
On 07.02.2015, at 15:51, Paul B Mahol one...@gmail.com wrote:
Signed-off-by: Paul B Mahol one...@gmail.com
---
libavcodec/Makefile | 1 -
On Tue, Feb 10, 2015 at 12:20:01PM +0100, wm4 wrote:
On Mon, 9 Feb 2015 23:49:00 +0100
Michael Niedermayer michae...@gmx.at wrote:
On Mon, Feb 09, 2015 at 10:33:53PM +0100, wm4 wrote:
Otherwise, you could lose the alpha when handling pixel formats in an
opaque manner (i.e. when you
On Mon, Feb 09, 2015 at 06:35:08PM +0100, Clément Bœsch wrote:
[...]
• we might still want to consider a per frame palette approach
To elaborate on this point, what I meant was to define a per frame palette
only for the part that change. I originally dismissed that idea for 2
reasons:
• it
From 533523210ae02b80d4450793fd9e3865e716e858 Mon Sep 17 00:00:00 2001
From: Kevin Wheatley kevin.j.wheat...@gmail.com
Date: Tue, 10 Feb 2015 11:37:00 +
Subject: [PATCH] libavformat: DNxHD in .mov, switch unspecified color_range to mpeg
Avid prefers mpeg range [16-235] by default this change
-Original Message-
From: ffmpeg-devel-boun...@ffmpeg.org [mailto:ffmpeg-devel-
boun...@ffmpeg.org] On Behalf Of Dominik 'Rathann' Mierzejewski
Sent: Monday, February 09, 2015 5:22 PM
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH 1/3] Add clew.c clew.h to libavutil
On Tue, 10 Feb 2015 12:47:04 +0100
Michael Niedermayer michae...@gmx.at wrote:
On Tue, Feb 10, 2015 at 12:20:01PM +0100, wm4 wrote:
On Mon, 9 Feb 2015 23:49:00 +0100
Michael Niedermayer michae...@gmx.at wrote:
On Mon, Feb 09, 2015 at 10:33:53PM +0100, wm4 wrote:
Otherwise, you
On Tue, Feb 10, 2015 at 01:08:32PM +0100, wm4 wrote:
On Tue, 10 Feb 2015 12:47:04 +0100
Michael Niedermayer michae...@gmx.at wrote:
On Tue, Feb 10, 2015 at 12:20:01PM +0100, wm4 wrote:
On Mon, 9 Feb 2015 23:49:00 +0100
Michael Niedermayer michae...@gmx.at wrote:
On Mon, Feb 09,
Signed-off-by: Michael Niedermayer michae...@gmx.at
---
ffmpeg.c |6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/ffmpeg.c b/ffmpeg.c
index fd45afb..becd5df 100644
--- a/ffmpeg.c
+++ b/ffmpeg.c
@@ -1528,8 +1528,8 @@ static void print_report(int is_last_report, int64_t
On Tue, Feb 10, 2015 at 04:02:53AM +0100, Reimar Döffinger wrote:
On 08.02.2015, at 10:32, Clément Bœsch u...@pkh.me wrote:
--- a/tests/fate-run.sh
+++ b/tests/fate-run.sh
@@ -38,7 +38,7 @@ target_path(){
# $1=value1, $2=value2, $3=threshold
# prints 0 if absolute difference between
---
libavfilter/unsharp.h | 4 ++
libavfilter/unsharp_opencl.c| 77 ---
libavfilter/unsharp_opencl_kernel.h | 122 ++--
3 files changed, 148 insertions(+), 55 deletions(-)
diff --git a/libavfilter/unsharp.h
On Fri, Jan 30, 2015 at 01:56:56PM +0100, Michael Niedermayer wrote:
From: Paul B Mahol one...@gmail.com
Signed-off-by: Michael Niedermayer michae...@gmx.at
---
LICENSE.md|1 +
configure |1 +
doc/filters.texi |5 ++
On Fri, 6 Feb 2015, Marton Balint wrote:
It is better than using simply video clock, because video clock may be NAN.
Signed-off-by: Marton Balint c...@passwd.hu
---
Hello Michael,
Please merge from my stable branch for the ffplay patch series:
6885009 ffplay: update frame timer based on
On Tue, Feb 10, 2015 at 01:13:40PM -0900, Lou Logan wrote:
On Tue, 10 Feb 2015 14:10:23 +0100, Michael Niedermayer wrote:
Signed-off-by: Michael Niedermayer michae...@gmx.at
---
doc/ffmpeg.texi |4
1 file changed, 4 insertions(+)
diff --git a/doc/ffmpeg.texi
On Tue, Feb 10, 2015 at 09:52:18PM +0100, Marton Balint wrote:
On Fri, 6 Feb 2015, Marton Balint wrote:
It is better than using simply video clock, because video clock may be NAN.
Signed-off-by: Marton Balint c...@passwd.hu
---
Hello Michael,
Please merge from my stable branch for
On Tue, 10 Feb 2015 14:10:23 +0100, Michael Niedermayer wrote:
Signed-off-by: Michael Niedermayer michae...@gmx.at
---
doc/ffmpeg.texi |4
1 file changed, 4 insertions(+)
diff --git a/doc/ffmpeg.texi b/doc/ffmpeg.texi
index 396c623..d36d56d 100644
--- a/doc/ffmpeg.texi
+++
Hello,
I have a patch I'd like to submit. One part is in the
*git://git.ffmpeg.org/rtmpdump
http://git.ffmpeg.org/rtmpdump repository, and the other in the regular
ffmpeg repository (librtmp.c).*
*what is the correct way to coordinate this?*
*Thanks,*
*Cary*
On Tue, 10 Feb 2015 14:38:36 -0900, Lou Logan wrote:
On Tue, 10 Feb 2015 23:44:43 +0100, Michael Niedermayer wrote:
2nd try:
@item -frame_drop_threshold @var{parameter}
Frame drop threshold, which specifies how much behind video frames can be
before
they are being dropped. In
On Tue, 10 Feb 2015 12:08:19 +
Gupta, Maneesh maneesh.gu...@amd.com wrote:
My intention is only to simplify the user experience of compiling OpenCL
enabled ffmpeg. Since this experience seems to be fine on Linux (where all
you need to do is install opencl-headers and ocl-icd), an
Doing this check in avutil_version() is not appropriate. Also, this code
is by default disabled (--assert-level is by default 0). A FATE run with
defaults will never execute the checks.
Move it to the pixelutils test program. Whatever reason there was in
avutil_version() not to run this test by
---
Why wasn't this done this way in the first place...
---
libavutil/internal.h | 2 ++
libavutil/pixdesc.h | 2 --
libavutil/utils.c| 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/libavutil/internal.h b/libavutil/internal.h
index 0a20142..143e2db 100644
---
The checks for the enums all were added in 2011 and 2012. They were
likely for checking that Libav changes do not change the FFmpeg ABI.
Given the amount of changes in the last 3 years, and the fact that
barely any other ABI specifics are tested, keeping these tests makes
not much sense anymore.
On Tue, 10 Feb 2015 23:44:43 +0100, Michael Niedermayer wrote:
2nd try:
@item -frame_drop_threshold @var{parameter}
Frame drop threshold, which specifies how much behind video frames can be
before
they are being dropped. In frame rate units, so 1.0 is one frame. The default
is
-1.1.
37 matches
Mail list logo
