Signed-off-by: Vittorio Giovara
---
Refreshing an old patch from last November...
After this, vf_colorspace supports *all* the primaries recognized
by libavutil.
Vittorio
doc/filters.texi| 3 +++
libavfilter/vf_colorspace.c | 2 ++
2 files changed, 5
On Wed, Jun 7, 2017 at 7:36 PM, Kieran O Leary wrote:
> Hi,
>
> Should the vf colorspace documentation be updated with this new addition?
Oh right, I forgot sorry.
Do you want to do the honors since I forgot also about gbr?
--
Vittorio
On 2017/6/7 11:17, Jun Zhao wrote:
>
>
> On 2017/6/7 9:22, Michael Niedermayer wrote:
>> On Mon, Jun 05, 2017 at 08:43:35AM +0800, Jun Zhao wrote:
>>> V2: Add Add set_ue_golomb_long() to support 32bits UE golomb and update the
>>> unit test.
>>
>>> golomb.h | 20 +++-
V3: Clean the code logic base on Michael's review.
V2: Add Add set_ue_golomb_long() to support 32bits UE golomb and update the
unit test.
From 4de3e0c30af7bc1901562000eda018a6d6849292 Mon Sep 17 00:00:00 2001
From: Jun Zhao
Date: Fri, 2 Jun 2017 15:05:49 +0800
Subject: [PATCH
Hi,
Should the vf colorspace documentation be updated with this new addition?
Best,
Kieran
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
On Wed, Jun 07, 2017 at 03:25:51PM +0200, Nedeljko Babic wrote:
> Manojkumar is taking over MIPS maintenance.
>
> Signed-off-by: Nedeljko Babic
> ---
> MAINTAINERS | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
applied
thanks
[...]
--
Michael GnuPG
Hi,
On Wed, Jun 7, 2017 at 5:50 PM, Vittorio Giovara wrote:
> +ENUM("smpte248", AVCOL_PRI_SMPTE428, "prm"),
428 or 248?
Ronald
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
On Mon, Jun 05, 2017 at 08:43:56PM +0200, Daniel Kucera wrote:
> Signed-off-by: Daniel Kucera
> ---
> libavformat/avio.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
breaks fate-indeo3-2
--- ./tests/ref/fate/indeo3-2 2017-06-07 00:13:40.271727575 +0200
+++
---
I don't have a sample for this, but I used the values found in mpv
(and I find the source very reliable about this).
Vittorio
libavfilter/vf_colorspace.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/libavfilter/vf_colorspace.c b/libavfilter/vf_colorspace.c
index
On Tue, Jun 6, 2017 at 4:48 PM John P Poet wrote:
> On Tue, Jun 6, 2017 at 4:40 PM Kieran Kunhya wrote:
>
>> >
>> > The cc_count is only 5 bits, which mean that only 31 3-byte "closed
>> caption
>> > constructs" will fit in a "block".Testing this with
On Tue, Jun 06, 2017 at 09:39:25AM -0700, Aman Gupta wrote:
> On Mon, Jun 5, 2017 at 1:22 PM, Aman Gupta wrote:
>
> > From: Aman Gupta
> >
> > Android TV and FireOS hardware supports mpeg2 hardware decoding via
> > MediaCodec.
> >
>
> I tested this patch on an
On Sat, Jun 3, 2017 at 3:24 PM, Gyan wrote:
> The support forum at
>
> http://ffmpeg.gusari.org/index.php
>
> which is linked to at
>
> http://www.ffmpeg.org/contact.html#Forums
>
> now sports a banner announcing its likely closure. The banner redirects
> visitors to Stack
On Wed, 7 Jun 2017, wm4 wrote:
On Wed, 31 May 2017 18:26:01 +0200
wm4 wrote:
Fixes detection of some TV sample as 24.5 FPS. With the patch applied,
it's detected as 25 FPS.
This is enabled for mpegts only.
---
libavformat/internal.h | 5 +
libavformat/mpegts.c
Hello,
I am removing myself from MAINTAINERS list as MIPS maintainer.
Manojkumar Bhosale agreed to maintain MIPS related code, so I am adding him to
the list.
Thanks,
Nedeljko
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
Manojkumar is taking over MIPS maintenance.
Signed-off-by: Nedeljko Babic
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 32408e6..60aae12 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -514,7 +514,7
On Wed, 31 May 2017 18:26:01 +0200
wm4 wrote:
> Fixes detection of some TV sample as 24.5 FPS. With the patch applied,
> it's detected as 25 FPS.
>
> This is enabled for mpegts only.
> ---
> libavformat/internal.h | 5 +
> libavformat/mpegts.c | 2 ++
>
I also have to wonder if it would be advantageous to add the cast on
the right side as well. That way the var_values variables will have
the proper truncated values on future evaluations. Open to comments on
that.
On Wed, Jun 7, 2017 at 3:45 AM, Kevin Mark wrote:
> -
The input width and height is known at parse time so there's no
reason ow/oh should not be usable when using 0 as the width or
height expression.
Previously in "scale=0:ow" ow would be set to "0" which works,
conveniently, as "scale=0:0" is perfectly valid input but this breaks
down when you do
Unfortunately I have to withdraw this patch. I'll be submitting an
updated one shortly. The below lines allow through values that are 0
when casted/truncated to an integer but are not zero as doubles (like
-0.1).
On Wed, Jun 7, 2017 at 2:11 AM, Kevin Mark wrote:
> -eval_w
The input width and height is known at parse time so there's no
reason ow/oh should not be usable when using 0 as the width or
height expression.
Previously in "scale=0:ow" ow would be set to "0" which works,
conveniently, as "scale=0:0" is perfectly valid input but this breaks
down when you do
20 matches
Mail list logo