On 2022-05-27 08:46 pm, Kieran Kunhya wrote:
On Fri, 27 May 2022 at 09:30, Gyan Doshi wrote:
Support for 'libx262' was added in e56f14659f by merging
Libav e1319aa1c1.
The Libav commit author believed that "x262 is a subfeature of x264"
but this is not the case. Kieran Kuhnya added support
On Wed, 25 May 2022, Martin Storsjö wrote:
This fixes handling of cases like ".ifc \foo, bar // comment", where
there was trailing whitespace after the condition (before the comment
which already was stripped out at this point).
---
Will apply after a couple days.
This fixes the "lavc/aarch64:
On Thu, 26 May 2022, Martin Storsjö wrote:
The dlopen wrapper contains code to make loading libraries safer,
to avoid loading a potentially malicious DLL with the same name.
Signed-off-by: Martin Storsjö
---
v2: Use dlsym too, for consistency.
---
libavcodec/mfenc.c | 7 ---
1 file changed,
On Fri, 27 May 2022, Swinney, Jonathan wrote:
Thanks! If I don't see it merged in a few days, I will submit it again
with the final touch up.
Pushed now, thanks!
// Martin
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mai
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Andreas Rheinhardt
> Sent: Saturday, April 30, 2022 10:02 PM
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] FATE Errors
>
> James Almer:
> >
> >
> > On 4/30/2022 4:06 PM, Andreas Rheinhardt wrote:
> >> Soft Works:
>
On Tue, May 17, 2022 at 12:45 PM James Zern wrote:
>
> On Tue, Apr 19, 2022 at 11:20 AM Bohan Li
> wrote:
> >
> > When target levels are set, this patch checks whether they are
> > satisfied by libaom. If not, a warning is shown. Otherwise the output
> > levels are also logged.
> >
> > This patch
log2() remains, this can either be replaced by a integer implementation or the
table
hardcoded if needed
Signed-off-by: Michael Niedermayer
---
libavcodec/ffv1enc.c| 25 -
tests/ref/vsynth/vsynth1-ffv1-2pass | 4 ++--
tests/ref/vsynth/vsynth2-ffv
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Mark Thompson
> Sent: Tuesday, May 3, 2022 10:23 PM
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] [PATCH 1/3] avutils/hwcontext: add
> derive-device function which searches for existing devices in both
> directions
>
On Fri, 27 May 2022 at 09:30, Gyan Doshi wrote:
> Support for 'libx262' was added in e56f14659f by merging
> Libav e1319aa1c1.
>
> The Libav commit author believed that "x262 is a subfeature of x264"
> but this is not the case. Kieran Kuhnya added support for MPEG-2
> encoding in *his fork* of x2
> -Original Message-
> From: softworkz
> Sent: Thursday, May 26, 2022 10:09 AM
> To: ffmpeg-devel@ffmpeg.org
> Cc: softworkz ; softworkz
>
> Subject: [PATCH 1/6] avutil/frame: Add av_frame_copy_side_data() and
> av_frame_remove_all_side_data()
>
> From: softworkz
>
> Signed-off-by:
Hello everybody. I have compiled ffmpeg libraries via msvc toolchain
under win64 os, but I came across on some lack of support pdb files. I need
to use /Zi command with compiler and generate full debug information via
linker's commands /DEBUG:FULL and /PDB:$(NAME), where $(NAME) is the name
of curr
On 5/27/2022 5:12 AM, Tomas Härdin wrote:
ons 2022-05-25 klockan 14:15 -0300 skrev James Almer:
Normally, both the source and dest frame would have only the old API
fields
set, only the new API fields set, or both set. But in some cases,
like when
calling av_frame_ref() using a non reference c
Hwaccel doesn't use any of the block strength, pcm, slice address, etc.
arrays which can be >100k each for 4k video. Patch to avoid initial
allocation and zeroing at the start of every frame. On a Pi4 the memsets
can use 10% CPU on 4k 60Hz decode, this fixes that.
Signed-off-by: John Cox
---
lib
Support for 'libx262' was added in e56f14659f by merging
Libav e1319aa1c1.
The Libav commit author believed that "x262 is a subfeature of x264"
but this is not the case. Kieran Kuhnya added support for MPEG-2
encoding in *his fork* of x264.
See https://github.com/kierank/x262/commit/6851000e27
So
ons 2022-05-25 klockan 14:15 -0300 skrev James Almer:
> Normally, both the source and dest frame would have only the old API
> fields
> set, only the new API fields set, or both set. But in some cases,
> like when
> calling av_frame_ref() using a non reference counted source frame
> where only
> th
15 matches
Mail list logo