Hi all,
Osamu and I are looking at adding FATE tests that checks that the MSE
of a decode image compared to a reference image does not exceed a
conformance threshold (see [1]).
Is there a precedent for adding small shell scripts along the lines of
the following to FATE?
https://gist.github.com/p
Signed-off-by: Peter Ross
---
Author: Paul B Mahol
Date: Wed Jun 26 09:07:29 2024 +0200
libavformat/mm.c | 31 ++
tests/ref/fate/alg-mm | 62 +--
2 files changed, 45 insertions(+), 48 deletions(-)
diff --git a/libavformat/mm.c
On 02/12/2024 11:15, Michael Niedermayer wrote:
Signed-off-by: Michael Niedermayer
---
libavcodec/ffv1enc.c| 8 +++-
libavcodec/ffv1enc.h| 6 ++
libavcodec/ffv1enc_vulkan.c | 8 +++-
3 files changed, 20 insertions(+), 2 deletions(-)
diff --git a/libavcodec/ffv1
Hi
On Sat, Nov 30, 2024 at 04:22:13PM +0900, Lynne via ffmpeg-devel wrote:
> On 30/11/2024 04:33, Michael Niedermayer wrote:
>
> > Signed-off-by: Michael Niedermayer
> > ---
> > libavcodec/ffv1enc.c | 14 +-
> > 1 file changed, 13 insertions(+), 1 deletion(-)
> >
> > diff --git a
Signed-off-by: Michael Niedermayer
---
libavcodec/ffv1enc.c| 8 +++-
libavcodec/ffv1enc.h| 6 ++
libavcodec/ffv1enc_vulkan.c | 8 +++-
3 files changed, 20 insertions(+), 2 deletions(-)
diff --git a/libavcodec/ffv1enc.c b/libavcodec/ffv1enc.c
index c96c71b1096..696823b
Hi Yiğithan
On Wed, Sep 04, 2024 at 09:26:19PM +0200, Michael Niedermayer wrote:
> Hi Yiğithan Yiğit
>
> On Mon, Sep 02, 2024 at 11:52:52PM +0200, Yigithan Yigit wrote:
> > Hi Michael,
> >
> > I am new to community, and I am not sure about qualifications of maintainer
> > but If you prefer I ca
On Mon, Sep 23, 2024 at 11:32:49PM +0200, Michael Niedermayer wrote:
> This does not replicate on my setup, thus this is a blind fix based on
> ossfuzz trace
>
> Fixes: use of uninitialized value
> Fixes:
> 71747/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_HEVC_fuzzer-5427736120721408
>
>
On Mon, Sep 23, 2024 at 11:32:47PM +0200, Michael Niedermayer wrote:
> Fixes: Use of uninitialized value
> Fixes:
> 71551/clusterfuzz-testcase-minimized-ffmpeg_dem_QCP_fuzzer-4647386712965120
>
> Found-by: continuous fuzzing process
> https://github.com/google/oss-fuzz/tree/master/projects/ffmpe
On Mon, Sep 23, 2024 at 11:32:46PM +0200, Michael Niedermayer wrote:
> Fixes: Use of uninitialized memory
> Fixes:
> 71546/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_EATGQ_fuzzer-5607656650244096
>
> Found-by: continuous fuzzing process
> https://github.com/google/oss-fuzz/tree/master/pro
On Mon, Sep 23, 2024 at 11:32:45PM +0200, Michael Niedermayer wrote:
> Signed-off-by: Michael Niedermayer
> ---
> libavcodec/eatgq.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
will apply
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
If you drop
Hi Lynne
On Sat, Sep 28, 2024 at 06:00:11AM +0200, Lynne via ffmpeg-devel wrote:
> On 22/09/2024 23:56, Michael Niedermayer wrote:
> > CC: Lynne
> > Signed-off-by: Michael Niedermayer
> > ---
> > MAINTAINERS | 2 ++
> > 1 file changed, 2 insertions(+)
> >
> > diff --git a/MAINTAINERS b/MAINT
On Sat, Oct 19, 2024 at 03:17:21AM +0200, Michael Niedermayer wrote:
> Fixes: use of uninitialized memory in hScale16To15_c()
> Fixes:
> 373924007/clusterfuzz-testcase-minimized-ffmpeg_SWS_fuzzer-5841199968092160
>
> Found-by: continuous fuzzing process
> https://github.com/google/oss-fuzz/tree/
On Wed, Oct 16, 2024 at 09:49:49PM +0200, Michael Niedermayer wrote:
> Signed-off-by: Michael Niedermayer
> ---
> libavcodec/rangecoder.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
will apply patch 2-6
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FA
On Mon, Nov 18, 2024 at 04:09:10AM +0100, Michael Niedermayer wrote:
> Comply with "For purposes other than determining the amount of data in the
> decoding units
> of the bitstream, decoders shall ignore all data that follow the value 63 for
> nuh_layer_id in a NAL unit"
> Rec. ITU-T H.265 v8 (0
On Mon, Dec 02, 2024 at 12:24:53AM +0100, Michael Niedermayer wrote:
> The rv60_qp_to_idx table only supports qp up to 31 on intra
>
> Fixes: global-buffer-overflow
> Fixes:
> 377543818/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_RV60_fuzzer-5160167345291264
>
> Found-by: continuous fuzzin
Hi Sean
On Thu, Nov 28, 2024 at 02:52:16PM -0500, Sean McGovern wrote:
> The FATE test 'checkasm-sw_yuv2rgb' currently fails on this platform,
> in both little- and big-endian configurations with AltiVec enabled.
>
> Disable it for the time being.
> ---
> libswscale/ppc/yuv2rgb_altivec.c | 8 +++
On Sat, Nov 30, 2024 at 03:24:31PM -0300, James Almer wrote:
> On 11/29/2024 2:17 PM, Michael Niedermayer wrote:
> > ambisonics mode > 1 does not initialize any layer but layer 0
> > is unconditionally dereferenced
> >
> > Fixes: poc-2024-11
> > Fixes: null pointer dereference
> > Found-by: 苏童 <22
On Sat, Sep 28, 2024 at 02:01:33AM +0200, Michael Niedermayer wrote:
> On Wed, Sep 25, 2024 at 03:16:30PM +0200, Ramiro Polla wrote:
> > On Tue, Sep 24, 2024 at 3:35 PM Michael Niedermayer
> > wrote:
> > > On Mon, Sep 23, 2024 at 12:42:22AM +0200, Ramiro Polla wrote:
> > > > Hi,
> > > >
> > > > On
Fixes: index 5 out of bounds for type 'uint8_t [5]'
Fixes:
377748135/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_AAC_LATM_fuzzer-5167109774049280
Found-by: continuous fuzzing process
https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
Signed-off-by: Michael Niedermayer
---
lib
Fixes:
377965565/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_VC1_fuzzer-4504434689769472
Fixes: out of array access
Found-by: continuous fuzzing process
https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
Signed-off-by: Michael Niedermayer
---
libavcodec/vc1dec.c | 1 +
1 file
Fixes: -nan is outside the range of representable values of type 'int'
Fixes:
377072730/clusterfuzz-testcase-minimized-ffmpeg_dem_IAMF_fuzzer-6545416570601472
Found-by: continuous fuzzing process
https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
Signed-off-by: Michael Niedermayer
-
Fixes: Timeout
Fixes:
377574369/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_MSCC_fuzzer-4924697608781824
Found-by: continuous fuzzing process
https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
Signed-off-by: Michael Niedermayer
---
tools/target_dec_fuzzer.c | 1 +
1 file chan
The rv60_qp_to_idx table only supports qp up to 31 on intra
Fixes: global-buffer-overflow
Fixes:
377543818/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_RV60_fuzzer-5160167345291264
Found-by: continuous fuzzing process
https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
Signed-of
Fixes: Timeout (would need 62sec)
Fixes:
376731123/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_VP6_fuzzer-5926437896388608
Found-by: continuous fuzzing process
https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
Signed-off-by: Michael Niedermayer
---
tools/target_dec_fuzzer.c
Hello all,
In mpeg_decode_a53_cc() only the A/53 part 4 CC data ("GA94") is saved
between frames. The other formats incorrectly create a larger buffer
than they use since
https://github.com/FFmpeg/FFmpeg/commit/a705bcd763e344fac191e157ffeddc285388b7fa
because they do not append to the previo
On 01/12/2024 19:44, Alexander Strasser via ffmpeg-devel wrote:
> Introduced in commit 98698ed3c24bfd0b1e6e6db943b5f25f6046cee7
>
> Fixes: CID1635788 CID1635789
> Signed-off-by: Alexander Strasser
> ---
>
> Just picked this up because of Coverity.
> Not sure how to verify/test this change, but i
In commit bce5855afb25d318e090c2e6c16117f065458356 we avoided the
problem by using compression level 0. That fixed the problem, but
introduced a problem with older versioins of original zlib. This
caused differences 2 or more fate tests depending on the zlib version
used. See e.g. zlib commit 8ba39
Sometimes deps (external from FFmpeg) can cause different results
either because of bugs or because of drop in replacements.
This feature of alternate reference files should only be used
where absolutely necessary because other solutions are not
feasible in practice. Maintaining two reference file
This reverts commit e206e72b83a0e512e21694a43af4df2b53f6d045.
---
tests/fate/cover-art.mak | 6 ++--
tests/fate/image.mak | 4 +--
tests/fate/lavf-image.mak | 5 +--
tests/fate/lavf-video.mak | 4 +--
tests/fate/mov.mak
This is a fixed up version of the series I sent before.
This worked for me on Ubuntu 20.04 but probably will break
with older zlib versions as Hendrik pointed out in the
previous thread. Either we must update zlib on affected
FATE clients or add more .alt files to them as well.
We could also go t
On 11/28/2024 5:02 PM, Marton Balint wrote:
On Wed, 27 Nov 2024, Marth64 wrote:
As it stands today, ffprobe has two stream-level fields
(closed_captions and film_grain)
that do not work. Their value is always 0 because ffprobe cannot
access the internal
codec properties in the stream context
Any opinions on v3?
Thank you.
___
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".
> this needs update to fate tests
I am reworking this set and will include the fate test fix
in the same commit for the next version.
Thank you.
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To un
Introduced in commit 98698ed3c24bfd0b1e6e6db943b5f25f6046cee7
Fixes: CID1635788 CID1635789
Signed-off-by: Alexander Strasser
---
Just picked this up because of Coverity.
Not sure how to verify/test this change, but it seems plausible.
Alexander
libavcodec/cbs_h266_syntax_template.c | 2 +-
aarch64 A55:
chrRangeFromJpeg16_1920_c:32684.2
chrRangeFromJpeg16_1920_neon: 8431.2 (3.88x)
chrRangeToJpeg16_1920_c: 24996.8
chrRangeToJpeg16_1920_neon:9395.0 (2.66x)
lumRangeFromJpeg16_1920_c:17305.2
lumRangeFromJpeg16_1920_neon: 4586.5 (3.77x)
lumRangeToJpeg16_1920_c: 2114
chrRangeFromJpeg16_1920_c:3153.9
chrRangeFromJpeg16_1920_sse4: 1770.0 (1.78x)
chrRangeFromJpeg16_1920_avx2: 891.5 (3.54x)
chrRangeToJpeg16_1920_c: 3165.0
chrRangeToJpeg16_1920_sse4: 1953.2 (1.62x)
chrRangeToJpeg16_1920_avx2:973.0 (3.25x)
lumRangeFromJpeg16_1920_c:1298.5
lumRange
aarch64 A55:
chrRangeFromJpeg8_1920_c:28835.2 (1.00x)
chrRangeFromJpeg8_1920_neon: 5313.9 (5.43x) 5308.4 (5.43x)
chrRangeToJpeg8_1920_c: 23074.7 (1.00x)
chrRangeToJpeg8_1920_neon:5551.3 (4.16x) 5549.2 (4.16x)
lumRangeFromJpeg8_1920_c:15389.7 (1.00x)
lumRangeFromJpeg8_1920_neon:
chrRangeFromJpeg8_1920_c:2127.4 (1.00x)
chrRangeFromJpeg8_1920_sse2: 816.0 (2.61x) 813.5 (2.62x)
chrRangeFromJpeg8_1920_avx2: 408.9 (5.20x) 405.4 (5.25x)
chrRangeToJpeg8_1920_c: 3166.9 (1.00x)
chrRangeToJpeg8_1920_sse2:815.0 (3.89x) 815.0 (3.89x)
chrRangeToJpeg8_1920_avx2:404.
aarch64 A55:
chrRangeFromJpeg8_1920_c:28836.2 (1.00x)
chrRangeFromJpeg8_1920_neon: 5312.6 (5.43x) 5313.9 (5.43x)
chrRangeToJpeg8_1920_c: 44196.2 (1.00x)
chrRangeToJpeg8_1920_neon:6034.6 (7.32x) 5551.3 (7.96x)
lumRangeFromJpeg8_1920_c:15388.5 (1.00x)
lumRangeFromJpeg8_1920_neon:
For bit depths <= 14, the result is saturated to 15 bits.
For bit depths > 14, the result is saturated to 19 bits.
x86_64:
chrRangeFromJpeg8_1920_c:2126.5 2127.4 (1.00x)
chrRangeFromJpeg16_1920_c: 2331.4 2325.2 (1.00x)
chrRangeToJpeg8_1920_c: 3163.0 3166.9 (1.00x)
chrRangeToJpe
---
tests/checkasm/sw_range_convert.c | 14 ++
1 file changed, 14 insertions(+)
diff --git a/tests/checkasm/sw_range_convert.c
b/tests/checkasm/sw_range_convert.c
index bf14209987..ba576ff08c 100644
--- a/tests/checkasm/sw_range_convert.c
+++ b/tests/checkasm/sw_range_convert.c
@@ -6
changes from v3:
- removed left-over FFMIN() on input in lumRangeToJpeg16_c();
- restored cast to signed int before right shift that was mistakenly removed in
chrRangeToJpeg16_c();
- restored disabling of aarch64 simd functions after changing to new API;
- add test for negative input values
- fixe
On 11/30/2024 6:13 AM, Zhao Zhili wrote:
From: Zhao Zhili
MSVC messed up standard C features, again.
---
libavutil/mem_internal.h | 4
1 file changed, 4 insertions(+)
diff --git a/libavutil/mem_internal.h b/libavutil/mem_internal.h
index 249ec3a642..2eb4aef5b0 100644
--- a/libavutil/me
Hi,
On Sun, Dec 1, 2024 at 9:24 AM Leo Izen wrote:
>
>
> On 11/30/24 9:23 AM, Niklas Haas wrote:
> > From: Niklas Haas
> >
> > ---
> > libavutil/csp.c | 6 +-
> > 1 file changed, 1 insertion(+), 5 deletions(-)
> >
> > diff --git a/libavutil/csp.c b/libavutil/csp.c
> > index 7ef822c60b..3
Hi Martin!
On 2024-11-07 11:36 +0200, Martin Storsjö wrote:
> If running tests with "make -j fate", the execution will stop
> after the first failing test. To get an overview of the whole
> test suite, one rather would run "make -k -j fate", which then
> again buries the results about what tests a
On 11/30/24 9:23 AM, Niklas Haas wrote:
From: Niklas Haas
---
libavutil/csp.c | 6 +-
1 file changed, 1 insertion(+), 5 deletions(-)
diff --git a/libavutil/csp.c b/libavutil/csp.c
index 7ef822c60b..3dd7bc2562 100644
--- a/libavutil/csp.c
+++ b/libavutil/csp.c
@@ -290,11 +290,7 @@ sta
The PNGv3 Specification Draft [1] has changed the capitalization
of mDCV and cLLI chunks (formerly mDCv and cLLi). This patch updates
FFmpeg to work with the new chunk names while retaining decode-side
compatibility with files created using the old names.
[1]: https://w3c.github.io/png/
Signed-of
On Sun, Dec 01, 2024 at 02:39:19AM +0100, Michael Niedermayer wrote:
> Hi Ramiro
>
> On Sat, Nov 30, 2024 at 04:23:36PM +0100, Ramiro Polla wrote:
> > For bit depths <= 14, the result is saturated to 15 bits.
> > For bit depths > 14, the result is saturated to 19 bits.
> >
> > x86_64:
> > chrRang
On Sun, 01 Dec 2024 02:56:31 +0100 Michael Niedermayer
wrote:
> Hi
>
> On Sat, Nov 30, 2024 at 03:27:53PM +0100, Niklas Haas wrote:
> > On Sat, 30 Nov 2024 15:23:50 +0100 Niklas Haas wrote:
> > > From: Niklas Haas
> > >
> > > The existing av_csp_trc_func_from_id() mostly implements the OETF, ex
49 matches
Mail list logo
