James Almer:
> On 11/16/2020 12:25 PM, Hendrik Leppkes wrote:
>> On Mon, Nov 16, 2020 at 4:20 PM James Almer wrote:
>>>
>>> On 11/16/2020 3:01 AM, Anton Khirnov wrote:
Quoting Xiang, Haihao (2020-11-16 06:16:55)
>
> This change breaks the compiling of gst-libav (
> https://gitlab.
On Sun, Nov 8, 2020 at 7:37 PM wrote:
> From: Mark Reid
>
> ---
> libavcodec/exr.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/libavcodec/exr.c b/libavcodec/exr.c
> index cf7824402a..e907c5c464 100644
> --- a/libavcodec/exr.c
> +++ b/libavcodec/exr.c
> @@ -1203,7 +1
On Sun, Nov 8, 2020 at 5:12 PM wrote:
> From: Mark Reid
>
> ---
> libavfilter/vf_lut3d.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/libavfilter/vf_lut3d.c b/libavfilter/vf_lut3d.c
> index 988f6c8b55..172d6df0c8 100644
> --- a/libavfilter/vf_lut3d.c
> +++ b/liba
Nov 16, 2020, 15:56 by ffm...@haasn.xyz:
> In terms of an API user needing this functionality, the way I see it
> working is that presence of the side-data will imply that it still needs
> to be applied, with the side data being removed the moment grain
> actually is applied. So that means that de
On Mon, 2020-11-16 at 21:46 -0300, James Almer wrote:
> On 11/16/2020 12:25 PM, Hendrik Leppkes wrote:
> > On Mon, Nov 16, 2020 at 4:20 PM James Almer wrote:
> > >
> > > On 11/16/2020 3:01 AM, Anton Khirnov wrote:
> > > > Quoting Xiang, Haihao (2020-11-16 06:16:55)
> > > > >
> > > > > This chang
On 11/16/2020 12:25 PM, Hendrik Leppkes wrote:
On Mon, Nov 16, 2020 at 4:20 PM James Almer wrote:
On 11/16/2020 3:01 AM, Anton Khirnov wrote:
Quoting Xiang, Haihao (2020-11-16 06:16:55)
This change breaks the compiling of gst-libav (
https://gitlab.freedesktop.org/gstreamer/gst-libav), I fi
In order to fine-control referencing schemes in VP9 encoding, there
is a need to use VP9E_SET_SVC_REF_FRAME_CONFIG method. This commit
provides a way to use the API through frame metadata.
---
libavcodec/libvpxenc.c | 77 ++
1 file changed, 77 insertions(+)
On 16/11/2020 21:26, Paul B Mahol wrote:
> LGTM
Pushed, thanks.
- Derek
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org w
LGTM
On Mon, Nov 16, 2020 at 10:23 PM Derek Buitenhuis <
derek.buitenh...@gmail.com> wrote:
> From: Andrew Rodland
>
> Fixes e.g. 'ffmpeg -i input.mp4 -vf frei0r=pixeliz0r output.mp4':
>
> [Parsed_frei0r_0 @ 0x5585b8093280] Duplicated pixel format
> Error reinitializing filters!
> Fa
On Mon, Nov 16, 2020 at 07:07:21AM +0100, Anton Khirnov wrote:
> Quoting Michael Niedermayer (2020-11-16 01:05:07)
> > On Sat, Nov 14, 2020 at 11:12:15AM +0100, Anton Khirnov wrote:
> > > Quoting Michael Niedermayer (2020-11-10 00:04:54)
> > > > Fixes: OOM
> > > > Fixes:
> > > > 26934/clusterfuzz-
From: Andrew Rodland
Fixes e.g. 'ffmpeg -i input.mp4 -vf frei0r=pixeliz0r output.mp4':
[Parsed_frei0r_0 @ 0x5585b8093280] Duplicated pixel format
Error reinitializing filters!
Failed to inject frame into filter network: Invalid argument
Error while processing the decoded data for
Gentle ping :)
On Mon, Nov 9, 2020 at 11:00 AM Bohan Li wrote:
> I have added a feature request in the libaom issue tracker for the key &
> value api, although it may take some time for the api to land. Meanwhile I
> still suggest that we apply this patch to ffmpeg since as mentioned this
> opti
From: Mohammad Izadi
HDR10+ is dynamic metadata (A/341 Amendment - SMPTE2094-40) that needs to be
decoded from ITU-T T.35 in HEVC bitstream. The HDR10+ is transferred to side
data packet to be used or passed through.
---
The fate test file can be found here:
https://drive.google.com/file/d/1Ha
On Mon, Nov 16, 2020 at 4:20 PM James Almer wrote:
>
> On 11/16/2020 3:01 AM, Anton Khirnov wrote:
> > Quoting Xiang, Haihao (2020-11-16 06:16:55)
> >>
> >> This change breaks the compiling of gst-libav (
> >> https://gitlab.freedesktop.org/gstreamer/gst-libav), I filed
> >> https://trac.ffmpeg.or
On 11/16/2020 3:01 AM, Anton Khirnov wrote:
Quoting Xiang, Haihao (2020-11-16 06:16:55)
This change breaks the compiling of gst-libav (
https://gitlab.freedesktop.org/gstreamer/gst-libav), I filed
https://trac.ffmpeg.org/ticket/8988 to track this regression.
This is not a regression, it's a b
In terms of an API user needing this functionality, the way I see it
working is that presence of the side-data will imply that it still needs
to be applied, with the side data being removed the moment grain
actually is applied. So that means that decoders applying film grain
must never export this
On 11/16/2020 3:16 AM, Anton Khirnov wrote:
Quoting Lynne (2020-11-14 15:32:35)
Nov 14, 2020, 11:23 by an...@khirnov.net:
Quoting Lynne (2020-11-12 18:42:22)
This introduces a new field to allow decoders to export their film grain
parameters.
Will be used by the next patch.
Patch attached.
applied
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
---
Fixes bug in sse3 path where m1 is not set correctly resulting in off
by one errors. The results are now bit by bit identical.
libswscale/x86/Makefile | 1 +
libswscale/x86/swscale.c| 75
libswscale/x86/yuv2yuvX.asm | 114 ++
19 matches
Mail list logo
