On Sun, Jul 20, 2025 at 1:17 AM Frank Plowman wrote:
> Prior to this patch, kth_order_egk_decode could read arbitrarily
> large values which then overflowed and caused various issues.
> Patch fixes this by making kth_order_egk_decode falliable,
> requiring the caller to specify an upper bound and
> On Jul 25, 2025, at 12:18, Gyan Doshi wrote:
>
>
>
> On 2025-07-25 03:29 am, Jack Lau wrote:
>> Signed-off-by: Jack Lau
>> ---
>> Changelog | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/Changelog b/Changelog
>> index 228029ea00..27531ad0ab 100644
>> --- a/Changelog
>> +++
On Thu, 24 Jul 2025 20:58:19 -0700, Jacob Lifshay wrote:
> On Thu, Jul 24, 2025 at 8:40 PM compn wrote:
> > people can always just manually attach patches to emails sent to
> > ffmpeg-devel list. no need for git send mail.
>
> ok, I prefer to never do that though because it makes reading the
>
On 2025-07-25 03:29 am, Jack Lau wrote:
Signed-off-by: Jack Lau
---
Changelog | 1 +
1 file changed, 1 insertion(+)
diff --git a/Changelog b/Changelog
index 228029ea00..27531ad0ab 100644
--- a/Changelog
+++ b/Changelog
@@ -25,6 +25,7 @@ version :
- APV in MP4/ISOBMFF muxing and demuxing
On Wed, 23 Jul 2025 11:59:23 +0200, Michael Niedermayer wrote:
> Hello Kieran
>
> On Wed, Jul 23, 2025 at 10:39:01AM +0100, Kieran Kunhya via ffmpeg-devel
> wrote:
> > > About 2. (IMHO)
> > > * The solution is to hire carl or someone else (or find a volunteer)
> > > to do this work. Changing t
On Thu, Jul 24, 2025 at 8:40 PM compn wrote:
> people can always just manually attach patches to emails sent to
> ffmpeg-devel list. no need for git send mail.
ok, I prefer to never do that though because it makes reading the
patches very annoying. Anyone should be able to read the patches
withou
On Tue, 22 Jul 2025 02:15:22 -0700, Jacob Lifshay wrote:
> On Tue, Jul 22, 2025 at 1:44 AM Kacper Michajlow wrote:
> > On Tue, 22 Jul 2025 at 05:54, Lynne wrote:
> > > +Additionally, new users have frequently encountered difficulties
> > > with mailing list development.
> > > +From fi
Fixes use-of-uninitialized-value.
Signed-off-by: James Almer
---
libavfilter/af_channelmap.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/libavfilter/af_channelmap.c b/libavfilter/af_channelmap.c
index a883934fa6..b864317312 100644
--- a/libavfilter/af_channelmap.c
+++ b/libavfilter/af_ch
Signed-off-by: Jack Lau
---
Changelog | 1 +
1 file changed, 1 insertion(+)
diff --git a/Changelog b/Changelog
index 228029ea00..27531ad0ab 100644
--- a/Changelog
+++ b/Changelog
@@ -25,6 +25,7 @@ version :
- APV in MP4/ISOBMFF muxing and demuxing
- OpenHarmony hardware decoder/encoder
- Colo
On Thu, 24 Jul 2025 16:59:24 +0200 Nicolas George wrote:
> Right now, I an not demanding negotiation, I am just requiring
> protection:
>
> if (frame->is_premultiplied && !out->supports_premultiplied) {
> av_log(ctx, AV_LOG_ERROR, "Your data is about to be
> corrupted bec
tor 2025-07-24 klockan 00:51 +0200 skrev Marton Balint:
>
>
> On Wed, 23 Jul 2025, Tomas Härdin wrote:
>
> > ons 2025-07-23 klockan 13:45 +0200 skrev Michael Niedermayer:
> > > Fixes: read of uninitialized memory
> > > Fixes: 391916474/clusterfuzz-testcase-minimized-
> > > ffmpeg_dem_MXF_fuzzer-
ons 2025-07-23 klockan 00:32 +0800 skrev Zhao Zhili:
> From: Zhao Zhili
>
> Fix assert failure.
> Fix #11666.
>
> Signed-off-by: Zhao Zhili
> ---
> libavformat/mxfenc.c | 48
Looks fine
/Tomas
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
ht
On 7/24/2025 7:58 PM, Kyle Swanson wrote:
Hi,
On Thu, Jul 24, 2025 at 10:46 AM Timo Rothenpieler
wrote:
The mails will never contain patches, they're just notifications.
They do contain a link to the patches and the PR number to fetch it via
CLI though.
If you append ".patch" or ".diff" to t
Hi,
On Thu, Jul 24, 2025 at 10:46 AM Timo Rothenpieler
wrote:
> The mails will never contain patches, they're just notifications.
> They do contain a link to the patches and the PR number to fetch it via
> CLI though.
If you append ".patch" or ".diff" to the url in the mail, you can get
the patc
On 7/24/2025 7:30 PM, Michael Niedermayer wrote:
Hi all
how can i simply follow all changes, patches and discussions ?
prior to teh forgejo test, i simply go over all new mail in my ffmpeg-devel
folder.
In that folder,
I can leave things as new that i want to look at later
I can mark
On 7/24/2025 6:48 PM, Nicolas George wrote:
Timo Rothenpieler (HE12025-07-24):
I don't see any need for this, no.
If the patch does not reach our inbox, it will not be reviewed.
That's what it does, just not as format-patch, but simply as a link.
A link is not enough. When we open our mail
Hi all
how can i simply follow all changes, patches and discussions ?
prior to teh forgejo test, i simply go over all new mail in my ffmpeg-devel
folder.
In that folder,
I can leave things as new that i want to look at later
I can mark things as old that i have not read but dont plan to d
Timo Rothenpieler (HE12025-07-24):
> I don't see any need for this, no.
If the patch does not reach our inbox, it will not be reviewed.
> That's what it does, just not as format-patch, but simply as a link.
A link is not enough. When we open our mail, we need to be able to see
the proposed chang
Fixes: use of uninitialized memory
Fixes:
427532813/clusterfuzz-testcase-minimized-ffmpeg_dem_MXG_fuzzer-5661938917113856
Found-by: continuous fuzzing process
https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
Signed-off-by: Michael Niedermayer
---
libavformat/mxg.c | 2 ++
1 file
Fixes: use of uninitialized memory
Fixes:
422217206/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_DXV_fuzzer-4786889444098048
Found-by: continuous fuzzing process
https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
Signed-off-by: Michael Niedermayer
---
libavcodec/dxvenc.c | 3 +
Fixes: use of uninitialized memory
Fixes:
421954767/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_SHORTEN_fuzzer-515682786246656
Found-by: continuous fuzzing process
https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
Signed-off-by: Michael Niedermayer
---
libavcodec/shorten.c |
On 23/07/2025 22:28, Jack Lau wrote:
Signed-off-by: Jack Lau
---
Changelog | 1 +
1 file changed, 1 insertion(+)
diff --git a/Changelog b/Changelog
index 228029ea00..1c6c27919f 100644
--- a/Changelog
+++ b/Changelog
@@ -2,6 +2,7 @@ Entries are sorted chronologically from oldest to youngest
On 7/24/2025 5:09 PM, Nicolas George wrote:
Timo Rothenpieler (HE12025-07-24):
If the "was synchronized" notifications could be disabled, it'd be much more
reasonable I feel.
But that does not seem to be an option, it's all or nothing.
I am not sure what you mean here.
If a patch is submitted
Timo Rothenpieler (HE12025-07-24):
> If the "was synchronized" notifications could be disabled, it'd be much more
> reasonable I feel.
> But that does not seem to be an option, it's all or nothing.
I am not sure what you mean here.
If a patch is submitted to the monolithic thing, the patch must b
Lynne (HE12025-07-24):
> That's way too spammy. Those wishing to stay on the ML should respect the
> decision of the vote and make an account.
What decision of the vote?
The way I recall it, the vote that just happened was about which one of
these two monstrous monolithic appliances we were to te
Niklas Haas (HE12025-07-24):
> That is no worse than the status quo, so I fail to see how this patch is
> a regression in this regard.
Until now, premultiplied frames were an anecdotal experimental feature
with barely any documentation: only people who knew what they were doing
were supposed to us
On 24/07/2025 03:55, Lynne wrote:
On 24/07/2025 07:06, Timo Rothenpieler wrote:
On 7/23/2025 9:24 PM, Nicolas George wrote:
Hi. I just saw somebody mention this on trac:
https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20025
But I have no trace of it in my inbox. If this is now an accepted way of
Changes since v2:
* Applied a few minor cosmetic fixes
* Fixed assignment logic in libjxl_parser.c
* Dropped unrelated commit that was causing FATE regressions
---
View it on FFmpeg Forgejo ( https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20031 )
or reply to this email directly.
___
On Wed, 23 Jul 2025 18:11:23 +0200 Kacper Michajlow wrote:
> On Wed, 23 Jul 2025 at 15:57, Niklas Haas wrote:
> >
> > From: Niklas Haas
> >
> > ---
> > libavfilter/vf_showinfo.c | 8
> > 1 file changed, 8 insertions(+)
> >
> > diff --git a/libavfilter/vf_showinfo.c b/libavfilter/vf_sho
On Wed, 23 Jul 2025 15:47:14 +0200 Niklas Haas wrote:
> From: Niklas Haas
>
> This filter was, for some reason, always ignoring the incoming chroma
> location in favor of the user-specified value, even when that value was set
> to the default (unspecified).
>
> This has been the status quo for qu
On Wed, 23 Jul 2025 18:19:03 +0200 Kacper Michajlow wrote:
> On Wed, 23 Jul 2025 at 15:57, Niklas Haas wrote:
> >
> > From: Niklas Haas
> >
> > This header bit ("alpha_associated") was incorrectly ignored.
> > ---
> > libavcodec/jpegxl_parse.c | 7 +--
> > libavcodec/jpegxl_parse.h | 1 +
On Wed, 23 Jul 2025 19:02:06 +0200 Nicolas George wrote:
> Niklas Haas (HE12025-07-23):
> > [PATCH v2 05/18] avcodec/encode: enforce alpha mode compatibility at encode
> > time
>
> That handles it for encoders, I suppose. But I do not see anything
> protecting you from stacking images with differ
On Thu, Jun 5, 2025 at 2:17 PM David Rosca wrote:
>
> On Mon, Apr 14, 2025 at 4:00 PM David Rosca wrote:
> >
> > We always use two slots, even when only one L0 reference is supported
> > by the driver. However we still need to set the correct value for the
> > ref_order_hint of the second slot.
>
On Wed, Jun 25, 2025 at 8:48 AM David Rosca wrote:
>
> ---
> libavcodec/hw_base_encode.c | 5 +
> 1 file changed, 5 insertions(+)
>
> diff --git a/libavcodec/hw_base_encode.c b/libavcodec/hw_base_encode.c
> index 33a30c8d10..927aeb4bad 100644
> --- a/libavcodec/hw_base_encode.c
> +++ b/libavc
*JackLau* force-pushed the *whip* from *d0d5c8ddde* (
https://code.ffmpeg.org/FFmpeg/FFmpeg/commit/d0d5c8dddef1c958596cb920559f3b27fb5ff4ed
) to *3d7807e03f* (
https://code.ffmpeg.org/FFmpeg/FFmpeg/commit/3d7807e03f17fb6222d15c452978f445720549cc
).
---
View it on FFmpeg Forgejo (
https://code
This patchset mainly add NACK, RTX, DTLS active support, fix some issues and
optimize the ICE and DTLS code
This version fix issue:
* fix https://ffmpeg.org/pipermail/ffmpeg-devel/2025-July/346906.html
* fix build error when openssl is 1.1.0, log:
libavformat/tls_openssl.c: In function ‘tls_writ
Fix #9195 ( https://code.ffmpeg.org/FFmpeg/FFmpeg/issues/9195 )
Signed-off-by: Zhao Zhili zhiliz...@tencent.com
---
View it on FFmpeg Forgejo ( https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20029 )
or reply to this email directly.
___
ffmpeg-devel mailin
Checkasm Benchmark Results
yuv2nv12cX_2_512_accurate_c: 3496.2 ( 1.00x)
yuv2nv12cX_2_512_accurate_neon:409.5 ( 8.54x)
yuv2nv12cX_2_512_approximate_c: 3495.1 ( 1.00x)
yuv2nv12cX_2_512_approximate_neon:
38 matches
Mail list logo
