вт, 6 мая 2025 г., 02:27 Michael Niedermayer :
> This will be available in https://github.com/michaelni/libpostproc
> either as a separate library or a ffmpeg source plugin whatever turns
> out more convenient to maintain
>
Congratulations, you broke building cinelerra-gg with ffmpeg.git despi
> -Original Message-
> From: ffmpegagent
> Sent: Donnerstag, 8. Mai 2025 03:37
> To: ffmpeg-devel@ffmpeg.org
> Cc: softworkz
> Subject: [PATCH v12 00/15] Execution Graph Printing
>
> Shortest cover letter for my longest-running FFmpeg patchset:
>
> * Apply
> * Build
> * Add the "-
When setting up the new Patchword builders I noticed some issues when
running FATE tests on Windows. Initially I had them suppressed on the
builders, but this patchset should finally fix it.
Version V2
* Clarified commit message in 3/3 regarding the requirement for a relative
path to the fate
From: softworkz
..when checked out with autocrlf=on, which is Git default
on Windows.
Signed-off-by: softworkz
---
.gitattributes | 38 +-
1 file changed, 37 insertions(+), 1 deletion(-)
diff --git a/.gitattributes b/.gitattributes
index b64bbed2eb..eaf7f7f
From: softworkz
MSYS2 considers the colon (:) as path separator (=separating multiple
paths) and thinks it needs to convert it to a Windows
path separator (;).
Setting the MSYS2_ARG_CONV_EXCL environment variable
keeps MSYS2 from doing this replacement.
NOTE: This makes it possible to run the t
From: softworkz
..to make it work when checked out with autocrlf=on,
which is Git default on Windows.
Signed-off-by: softworkz
---
tests/fate/source-check.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/fate/source-check.sh b/tests/fate/source-check.sh
index 4d7e17
Fixes ticket: https://trac.ffmpeg.org/ticket/11574
Signed-off-by: Appaji
---
fftools/ffplay.c | 13 +++--
1 file changed, 11 insertions(+), 2 deletions(-)
diff --git a/fftools/ffplay.c b/fftools/ffplay.c
index 2a572fc3aa..42f0584b55 100644
--- a/fftools/ffplay.c
+++ b/fftools/ffplay.c
@
We may write up to 43 bits, so 5 bytes is not enough.
Fixes: Assertion n>=0 && n<=32 failed at ./libavcodec/get_bits.h:406
Fixes:
398527871/clusterfuzz-testcase-minimized-ffmpeg_dem_IAMF_fuzzer-6602025714647040
Found-by: continuous fuzzing process
https://github.com/google/oss-fuzz/tree/master/
It's only supported by GCC, and everything inside the __asm__() block is
invisible to the compiler's scheduler.
Signed-off-by: James Almer
---
libavutil/x86/intmath.h | 55 -
1 file changed, 10 insertions(+), 45 deletions(-)
diff --git a/libavutil/x86/int
On Mon, May 12, 2025 at 02:02:41PM +0800, Coia Prant wrote:
> On Windows Arm64
> `uname -m` returned `x86_64` instead of `aarch64`
> Link: https://github.com/msys2/msys2-runtime/issues/171
>
> But `uname -s` contains `ARM64` suffix
> So check suffix on windows arm64 (for clangarm64)
>
> This prob
From: softworkz
Signed-off-by: softworkz
---
doc/developer.texi | 192 +++--
1 file changed, 98 insertions(+), 94 deletions(-)
diff --git a/doc/developer.texi b/doc/developer.texi
index 108558b9e0..42e42350a5 100644
--- a/doc/developer.texi
+++ b/doc/dev
The https://ffmpeg.org/developer.html (doc/developer.texi) page contains a
lot of good information but there's some structural and contentual
duplication that is begging for cleanup:
3 Development Policy
[https://ffmpeg.org/developer.html#Development-Policy-1] 4 Submitting
patches [https://ffmpeg.
From: softworkz
Signed-off-by: softworkz
---
doc/developer.texi | 16 ++--
1 file changed, 6 insertions(+), 10 deletions(-)
diff --git a/doc/developer.texi b/doc/developer.texi
index 5a026fff0e..145b57b249 100644
--- a/doc/developer.texi
+++ b/doc/developer.texi
@@ -923,22 +923,15
From: softworkz
Signed-off-by: softworkz
---
doc/developer.texi | 104 +++--
1 file changed, 53 insertions(+), 51 deletions(-)
diff --git a/doc/developer.texi b/doc/developer.texi
index 42e42350a5..a723d41f39 100644
--- a/doc/developer.texi
+++ b/doc/dev
From: softworkz
Signed-off-by: softworkz
---
doc/developer.texi | 48 --
1 file changed, 25 insertions(+), 23 deletions(-)
diff --git a/doc/developer.texi b/doc/developer.texi
index a723d41f39..5a026fff0e 100644
--- a/doc/developer.texi
+++ b/doc/dev
On Mon, 12 May 2025, Coia Prant wrote:
On Windows Arm64
`uname -m` returned `x86_64` instead of `aarch64`
Link: https://github.com/msys2/msys2-runtime/issues/171
But `uname -s` contains `ARM64` suffix
So check suffix on windows arm64 (for clangarm64)
This problem also in VideoLAN/x264
Link: ht
On Fri, May 09, 2025 at 06:43:26PM -0500, Romain Beauxis wrote:
> ---
> libavcodec/vorbisdec.c | 37 +
> libavformat/oggparsevorbis.c | 174 +
> tests/ref/fate/ogg-vorbis-chained-meta.txt | 3 -
> 3 files changed, 117 insertions(+), 97 d
On 11/05/2025 14:44, Mark Thompson wrote:
> Same setup as the 422-10 profile test, using the same content. FFmpeg
> decoder output is identical to the reference decoder output.
> ---
> On 11/05/2025 14:40, James Almer wrote:
>> Will upload.
>
> Thank you!
And pushed with that in place.
Thanks,
On 11/05/2025 11:09, Mark Thompson wrote:
> ---
> v2:
> * Bring error handling to the same level as before.
> * Split first run/level step to avoid first-AC handling inside the loop.
> * More commentary.
> * Other minor improvements.
>
> Thanks,
No further changes here, so applied.
This also see
On Sat, May 10, 2025 at 12:51:09PM -0300, James Almer wrote:
> We may write up to 43 bits, so 5 bytes is not enough.
>
> Fixes: Assertion n>=0 && n<=32 failed at ./libavcodec/get_bits.h:406
> Fixes:
> 398527871/clusterfuzz-testcase-minimized-ffmpeg_dem_IAMF_fuzzer-6602025714647040
>
> Found-by:
> -原始邮件-
> 发件人: "Shiyou Yin"
> 发送时间:2025-05-13 09:11:34 (星期二)
> 收件人: ffmpeg-devel@ffmpeg.org
> 主题: [FFmpeg-devel] [PATCH] configure: identify loong64 for loongarch.
>
> dpkg-architecture set DEB_HOST_ARCH_CPU as loong64 on loongarch.
> ---
> configure | 2 +-
> 1 file changed, 1 inser
On 2025-05-12 9:11 p.m., Shiyou Yin wrote:
dpkg-architecture set DEB_HOST_ARCH_CPU as loong64 on loongarch.
---
configure | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/configure b/configure
index 2e69b3c56c..5f39050374 100755
--- a/configure
+++ b/configure
@@ -5290,7 +52
k is always 4 here and it seems this is not what was intended
replacing it with 0 works but it may be wrong
This needs review
Fixes: out of array read
Fixes:
409593384/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_SANM_fuzzer-6488251907244032
Found-by: continuous fuzzing process
https://gi
Fixes: Assertion sc->slice_coding_mode == 0 failed at libavcodec/ffv1enc.c:1667
Fixes:
408838118/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_FFV1_fuzzer-6493138204295168
Found-by: continuous fuzzing process
https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
Signed-off-by: Micha
ср, 14 мая 2025 г., 03:55 Andrew Randrianasulu :
>
>
> вт, 6 мая 2025 г., 02:27 Michael Niedermayer :
>
>> This will be available in https://github.com/michaelni/libpostproc
>> either as a separate library or a ffmpeg source plugin whatever turns
>> out more convenient to maintain
>>
>
>
>
> Congr
This is a test email
___
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".
Original Implementation:
-
In the original implementation, the "VER_SD" section processes image data
stored in *data using strided memory access in a vertical fashion This leads to
inefficient memory access patterns and cache thrashing due to non-sequential
data a
it's a good suggestion.
> -原始邮件-
> 发件人: "Brad Smith"
> 发送时间:2025-05-14 09:06:31 (星期三)
> 收件人: "FFmpeg development discussions and patches" ,
> "Shiyou Yin"
> 主题: Re: [FFmpeg-devel] [PATCH] configure: identify loong64 for loongarch.
>
> On 2025-05-12 9:11 p.m., Shiyou Yin wrote:
> > dpk
Bumping this again. Would like to use it for some upcoming live events.
___
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
Is there any patch or any development so that we can send scte 35 trigger .
regards
ashish
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-req
30 matches
Mail list logo
