$subj
0001-libavfilter-vf_hqdn3d-Remove-emms.patch
Description: Binary data
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
Thilo Borgmann via ffmpeg-devel 于2023年11月1日周三 08:04写道：
>
> > it would just show up once lets say on a specific day 1 year after the code
> > is added. we would remove it on that day ourselfs.
> > It would just be a simple one time shown message that says
> > "Decoded by ffmpeg.org / Please
Am 31.10.23 um 18:48 schrieb Michael Niedermayer:
On Tue, Oct 31, 2023 at 06:37:58PM +0100, Hendrik Leppkes wrote:
On Tue, Oct 31, 2023 at 6:31 PM Michael Niedermayer
wrote:
On Tue, Oct 31, 2023 at 07:19:41PM +0200, Rémi Denis-Courmont wrote:
Le tiistaina 31. lokakuuta 2023, 18.58.57 EET
On Tue, Oct 24, 2023 at 05:54:37AM -0400, Leo Izen wrote:
> On 10/23/23 12:04, Michael Niedermayer wrote:
> > On Mon, Oct 23, 2023 at 02:10:35AM -0400, Leo Izen wrote:
> > > On 10/22/23 17:51, Michael Niedermayer wrote:
> > > > This makes the code more testable as uninitialized fields are 0
> > >
On Sun, Oct 22, 2023 at 02:35:15AM +0200, Michael Niedermayer wrote:
> Fixes: Assertion failure in mov_read_iloc( in mov_read_iloc())
> Fixes:
> 62866/clusterfuzz-testcase-minimized-ffmpeg_dem_MOV_fuzzer-5282997370486784
>
> Found-by: continuous fuzzing process
>
On Fri, Oct 27, 2023 at 03:02:27PM +0200, Dawid Kozinski/Multimedia (PLT)
/SRPOL/Staff Engineer/Samsung Electronics wrote:
>
>
>
>
> > -Original Message-
> > From: ffmpeg-devel On Behalf Of
> > Michael Niedermayer
> > Sent: piątek, 13 października 2023 01:28
> > To: FFmpeg
On Tue, Oct 31, 2023 at 9:13 PM Paul B Mahol wrote:
>
>
> On Tue, Oct 31, 2023 at 11:55 AM Nicolas George wrote:
>
>> Paul B Mahol (12023-10-27):
>> > Both patches are required to fix out of memory scenario with this use
>> case:
>>
>> I checked. The OOM still happens with these two patches =>
On Tue, Oct 31, 2023 at 11:55 AM Nicolas George wrote:
> Paul B Mahol (12023-10-27):
> > Both patches are required to fix out of memory scenario with this use
> case:
>
> I checked. The OOM still happens with these two patches => they do not
> fix the issue => rejected.
>
Huh? I fixed this, and
v2: refactored after review
Signed-off-by: Evgeny Pavlov
Co-authored-by: Dmitrii Ovchinnikov
---
libavcodec/amfenc.c | 2 ++
libavcodec/amfenc_av1.c | 22 ++
2 files changed, 24 insertions(+)
diff --git a/libavcodec/amfenc.c b/libavcodec/amfenc.c
index
From: nyanmisaka
v2: fixes for indentation
---
libavcodec/amfenc.c | 83 +
1 file changed, 83 insertions(+)
diff --git a/libavcodec/amfenc.c b/libavcodec/amfenc.c
index 0bd15dd812..068bb53002 100644
--- a/libavcodec/amfenc.c
+++ b/libavcodec/amfenc.c
From: Michael Fabian 'Xaymar' Dirks
added 10 bit support for amf hevc.
before:
command - ffmpeg.exe -hide_banner -y -hwaccel d3d11va -hwaccel_output_format
d3d11 -i test_10bit_file.mkv -an -c:v h264_amf res.dx11_hw_h264.mkv
output - Format of input frames context (p010le) is not supported by
v2: refactored after review
Signed-off-by: Evgeny Pavlov
Co-authored-by: Dmitrii Ovchinnikov
---
libavcodec/amfenc.c | 2 ++
libavcodec/amfenc_av1.c | 22 ++
2 files changed, 24 insertions(+)
diff --git a/libavcodec/amfenc.c b/libavcodec/amfenc.c
index
From: nyanmisaka
v2: fixes for indentation
---
libavcodec/amfenc.c | 83 +
1 file changed, 83 insertions(+)
diff --git a/libavcodec/amfenc.c b/libavcodec/amfenc.c
index 0bd15dd812..068bb53002 100644
--- a/libavcodec/amfenc.c
+++ b/libavcodec/amfenc.c
From: Michael Fabian 'Xaymar' Dirks
added 10 bit support for amf hevc.
before:
command - ffmpeg.exe -hide_banner -y -hwaccel d3d11va -hwaccel_output_format
d3d11 -i test_10bit_file.mkv -an -c:v h264_amf res.dx11_hw_h264.mkv
output - Format of input frames context (p010le) is not supported by
On Tue, Oct 31, 2023 at 06:37:58PM +0100, Hendrik Leppkes wrote:
> On Tue, Oct 31, 2023 at 6:31 PM Michael Niedermayer
> wrote:
> >
> > On Tue, Oct 31, 2023 at 07:19:41PM +0200, Rémi Denis-Courmont wrote:
> > > Le tiistaina 31. lokakuuta 2023, 18.58.57 EET Michael Niedermayer a écrit
> > > :
> >
This is a trivial patch that fixes the bug. If there are no objections, I
would like to merge it in 2-3 days
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or
On Tue, Oct 31, 2023 at 6:31 PM Michael Niedermayer
wrote:
>
> On Tue, Oct 31, 2023 at 07:19:41PM +0200, Rémi Denis-Courmont wrote:
> > Le tiistaina 31. lokakuuta 2023, 18.58.57 EET Michael Niedermayer a écrit :
> > > > That's not a credible solution for a library. All reverse dependency
> > > >
On Tue, Oct 31, 2023 at 07:19:41PM +0200, Rémi Denis-Courmont wrote:
> Le tiistaina 31. lokakuuta 2023, 18.58.57 EET Michael Niedermayer a écrit :
> > > That's not a credible solution for a library. All reverse dependency
> > > developers would disable that before they ship affected FFmpeg
Le tiistaina 31. lokakuuta 2023, 18.58.57 EET Michael Niedermayer a écrit :
> > That's not a credible solution for a library. All reverse dependency
> > developers would disable that before they ship affected FFmpeg versions,
> > or worse, just stop updating their vendored FFmpeg.
>
> If its
On Sun, Oct 29, 2023 at 09:36:13PM +0200, Rémi Denis-Courmont wrote:
> Le sunnuntaina 29. lokakuuta 2023, 18.12.58 EET Michael Niedermayer a écrit :
> > On Sun, Oct 29, 2023 at 04:35:35PM +0200, Rémi Denis-Courmont wrote:
> > > Hi,
> > >
> > > Le 28 octobre 2023 21:01:57 GMT+03:00, Michael
> From: ffmpeg-devel On Behalf Of Romain
> Beauxis
> Sent: 2023年10月30日 9:06
> To: ffmpeg-devel@ffmpeg.org
> Cc: Romain Beauxis
> Subject: [FFmpeg-devel] [PATCH] Extract av_hls_codec_attr
>
> The logic for extracting HLS codec attribute strings is very useful and
> can be re-used in many
From: Niklas Haas
Alpha planes must always be full range, so complain loudly if fed
limited range grayscale input.
---
libavfilter/vf_alphamerge.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/libavfilter/vf_alphamerge.c b/libavfilter/vf_alphamerge.c
index 4bbc06da36..a5f5baf77e
From: Niklas Haas
No need to write a custom string parser when we can just use an integer
option with preset values. The various bits of fallback logic are wholly
redundant with equivalent logic already inside sws_getCoefficients.
Note: I disallowed setting 'out_color_matrix=auto', because this
From: Niklas Haas
When using vf_scale to force a specific output color space, also tag
this on the AVFrame. (Mirroring existing logic for output range)
---
libavfilter/vf_scale.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/libavfilter/vf_scale.c b/libavfilter/vf_scale.c
index
From: Niklas Haas
PGMYUV seems to be always limited range. This was a format originally
invented by FFmpeg at a time when YUVJ distinguished limited from full
range YUV, and this codec never appeared to output YUVJ in any
circumstance, so hard-coding limited range preserves the status quo.
The
From: Niklas Haas
Alpha planes are explicitly full range, even for limited range YUVA
formats. Mark them as such.
---
libavfilter/vf_extractplanes.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/libavfilter/vf_extractplanes.c b/libavfilter/vf_extractplanes.c
index 7b7149ab24..ca406ff323
From: Niklas Haas
This was a complete hack seemingly designed to work around a different
bug, which was fixed in the previous commit. As such, there is no more
reason not to do this, as it simply breaks changing color range in
sws_setColorspaceDetails for no reason.
---
libswscale/utils.c | 4
From: Niklas Haas
More commonly, this fixes the case of sws_setColorspaceDetails after
sws_getContext, since the latter implies sws_init_context.
The problem here is that sws_init_context sets up the range conversion
and fast path tables based on the values of srcRange/dstRange at init
time.
From: Niklas Haas
The documentation states that invalid entries default to SWS_CS_DEFAULT.
A value of 0 is not a valid SWS_CS_*, yet the code incorrectly
hard-codes it to BT.709 coefficients instead of SWS_CS_DEFAULT.
---
libswscale/yuv2rgb.c | 2 +-
1 file changed, 1 insertion(+), 1
On Sun, Oct 29, 2023 at 08:05:50PM -0500, Romain Beauxis wrote:
> The logic for extracting HLS codec attribute strings is very useful and
> can be re-used in many different situations when working with HLS
> streams using libavcodec/libavformat.
>
> This patch extracts the function's code and
On Sat, 28 Oct 2023 16:41:13 +0200 Niklas Haas wrote:
> From: Niklas Haas
>
> This code, as written, skips sws_init_context if scale->in_range was not
> set, even if scale->in_frame_range is set to something. So this would
> hit the 'no sws context' fast path in scale_frame and skip color range
On Thu, 26 Oct 2023, Logan.Lyu wrote:
And I missed submitting a commit that was earlier than these four commits,
which caused the corrupted whitespace problem. Now I have recreated these
patches.
In addition, I rebased it to ensure that these patches can be successfully
applied on the
On Tue, 31 Oct 2023 00:42:47 +0100 Michael Niedermayer
wrote:
> On Sat, Oct 28, 2023 at 04:41:14PM +0200, Niklas Haas wrote:
> > From: Niklas Haas
> >
> > YUV->YUV conversions should preserve input range, if the output range is
> > unspecified. Ensures full-range YUV input comes out as
Paul B Mahol (12023-10-27):
> Both patches are required to fix out of memory scenario with this use case:
I checked. The OOM still happens with these two patches => they do not
fix the issue => rejected.
> This was a test. That you failed.
Are you sure you are mature enough to go on the
On Tue, 24 Oct 2023, Martin Storsjö wrote:
Clang versions before 17 (Xcode versions up to and including 15.0)
had a very annoying bug in its behaviour of the ".arch" directive
in assembly. If the directive only contained a level, such as
".arch armv8.2-a", it did validate the name of the level,
On Tue, 24 Oct 2023, Sean McGovern wrote:
On Tue, Oct 24, 2023, 08:23 Martin Storsjö wrote:
Skip doing the whole getauxval(AT_HWCAP) if HWCAP_CPUID isn't
defined.
---
libavutil/aarch64/cpu.c | 6 +-
1 file changed, 1 insertion(+), 5 deletions(-)
diff --git a/libavutil/aarch64/cpu.c
> 在 2023年10月31日，下午4:40，Zhao Zhili 写道：
>
>
>>
>> On Oct 31, 2023, at 13:16, Lynne wrote:
>>
>> Oct 30, 2023, 18:35 by quinkbl...@foxmail.com:
>>
>>>
On 2023/10/31 01:05, Lynne wrote:
>>>
Oct 30, 2023, 17:05 by quinkbl...@foxmail.com:
> From: Zhao Zhili
>
>
On Mon, Oct 30, 2023 at 02:11:27PM +0100, Andreas Rheinhardt wrote:
> Section 7.4.4 of the MPEG-2 specifications requires that the
> last bit of the last coefficient be toggled so that the sum
> of all coefficients is odd; both our decoder and encoder
> did this only if the bitexact flag has been
> On Oct 31, 2023, at 13:16, Lynne wrote:
>
> Oct 30, 2023, 18:35 by quinkbl...@foxmail.com:
>
>>
>> On 2023/10/31 01:05, Lynne wrote:
>>
>>> Oct 30, 2023, 17:05 by quinkbl...@foxmail.com:
>>>
From: Zhao Zhili
Add vulkan renderer via libplacebo.
Simple usage:
39 matches
Mail list logo
