PR #20129 opened by Daniel Stadelmann (dstadelmann-iis)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20129
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20129.patch
Adds a wrapper around the Fraunhofer IIS MPEG-H 3D Audio mpeghdec [1]
decoder shared library.
[1] https://github.com/Fr
On 2025-08-06 00:37 +0200, Michael Niedermayer wrote:
>
> On Mon, Aug 04, 2025 at 10:15:53PM +0200, Alexander Strasser via ffmpeg-devel
> wrote:
[...]
> >
> > If I understand the original point you wanted to discuss correctly,
> > than this is not a question of rebase or merge but one of letting
Le 4 août 2025 22:06:07 GMT+07:00, Leon Grutters a
écrit :
>Is it that much harder to submit a patch on the ML? All you do is sign up for
>the ML, run one git command and then attach it to an email and click send.
I don't know how much is that much. It is harder, at least the *first* time,
t
Hi,
There is an ongoing FATE failure on RISC-V. I can try to address it by the end
of *next* week but not right now.
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above
Hi,
FWIW I don't really care personally but judging by the original author and
their affiliation, the intent was most probably to enable this for RISC-V /
RVA23.
On that platform it is *probably* safe to enable vectorisation on all GCC
versions but I have not tested it. In fact, I don't have a
From: renjg <17607086...@163.com>
Functions and arrays in pixdesc will cause the code size to be larger (about
30KB or more).
For some products that only care about audio,you can use the audio_only switch
to
reduce the size of pixdesc symbols.
You can enable optimization by using the command lin
Add check for the return value of av_calloc() to avoid potential NULL pointer
dereference.
Fixes: 7dc81d33c2 ("lavfi/af_channelmap: remove an arbitrary limit on channel
count")
Signed-off-by: Jiasheng Jiang
---
libavfilter/af_channelmap.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/
PR #20127 opened by michaelni
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20127
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20127.patch
Signed-off-by: Michael Niedermayer
>From 934c1cadb4617d54649fd29062d5d491b33ae6f8 Mon Sep 17 00:00:00 2001
From: Michael Niedermayer
Date: Wed
PR #20126 opened by Kacper Michajłow (kasper93)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20126
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20126.patch
heif_items are reused and to avoid leaking memory or using stale name,
clear it first.
Signed-off-by: Kacper Michajłow
From
Hi Alexander
On Mon, Aug 04, 2025 at 10:15:53PM +0200, Alexander Strasser via ffmpeg-devel
wrote:
> Hi Michael,
> hi all!
>
> I think it's a good time to bring stuff like this up for discussion.
>
> On 2025-08-03 21:02 +0200, Michael Niedermayer wrote:
> >
> > On Sun, Aug 03, 2025 at 05:31:39P
On 2025-08-05 05:06 +0200, Kacper Michajlow wrote:
> On Mon, 4 Aug 2025 at 23:38, Marton Balint wrote:
> >
> > On Mon, 4 Aug 2025, Alexander Strasser via ffmpeg-devel wrote:
[...]
> > >
> > > If I understand the original point you wanted to discuss correctly,
> > > than this is not a question of r
Don't silently skip errors when AV_EF_EXPLODE is specified. This can
lead to out-of-bound reads with ff_put_h264_chroma_mc4_ssse3() when
small padding is used with the checked bitstream reader.
Signed-off-by: Dale Curtis
h264_stricter_v1.patch
Description: Binary data
__
Jiasheng Jiang (HE12025-08-05):
> Moreover, replace with proper error handling to avoid potential memory leak.
There is no potential memory leak with exit().
And it does not have to be a lesson in good C practices.
Regards,
--
Nicolas George
___
ff
Move av_malloc() after the check for subsampling to avoid memory leak if
subsampling < 0 and av_malloc() succeeds.
Fixes: a41a2efc85 ("lavc/videotoolbox: add VP9 hardware acceleration")
Signed-off-by: Jiasheng Jiang
---
libavcodec/videotoolbox_vp9.c | 6 +++---
1 file changed, 3 insertions(+),
Add check for the return valud of av_packet_alloc() to avoid potential NULL
pointer dereference.
Moreover, replace with proper error handling to avoid potential memory leak.
Fixes: 9a38184a14 ("examples/decode_audio: allocate the packet dynamically")
Fixes: f5df897c4b ("examples/avcodec: split au
PR #20124 opened by Kacper Michajłow (kasper93)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20124
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20124.patch
From 9e0c4693414bc97587d234b60c76a2470ee45e0d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Kacper=20Michaj=C5=82ow?=
Date: Mon, 4
PR #20123 opened by Kacper Michajłow (kasper93)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20123
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20123.patch
Signed-off-by: Kacper Michajłow
From 8930558b83f69ced7b22813bf9271a06955e7dd5 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Kacper
PR #20122 opened by James Almer (jamrial)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20122
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20122.patch
Fixes issue #20121
>From accb9128272882d713bfd1e8b87aa46ba5b8197c Mon Sep 17 00:00:00 2001
From: James Almer
Date: Tue, 5 Aug 2025
On 2025/08/05 01:02, kimapr via ffmpeg-devel wrote:
> Hi! it would be nice if my bug fix
>
>avformat/libopenmpt: fix seeking weirdness
>
> was backported to 6.1.3 and 7.0.3 (dunno about 5.1.7 as i haven't checked
> if libopenmpt even exists there). not sure how that would work from my side
I
On Tue, 5 Aug 2025 at 15:10, Nicolas George wrote:
>
> Leon Grutters (HE12025-08-04):
> > Is it that much harder to submit a patch on the ML? All you do is sign up
> > for the ML, run one git command and then attach it to an email and click
> > send.
>
> No, it is not harder at all, but it has the
PR #20120 opened by Martin Storsjö (mstorsjo)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20120
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20120.patch
This changes configure to stop disabling -ftree-vectorize on
GCC versions 13 and newer, on major architectures.
Background:
- Ori
Leon Grutters (HE12025-08-04):
> Is it that much harder to submit a patch on the ML? All you do is sign up
> for the ML, run one git command and then attach it to an email and click
> send.
No, it is not harder at all, but it has the reputation to be, which has
the same result.
Nowadays, any idio
Nicolas George (HE12025-08-04):
> That was me.
Whoever disabled the account: I went to just delete it, and now I
cannot, so the joke is on you, you have to do it yourself.
> Thank you for ensuring it went to the mailing-list.
It seems to work randomly.
Regards,
--
Nicolas George
___
On Fri, 18 Jul 2025, Kacper Michajlow wrote:
On Fri, 11 Jul 2025 at 23:41, Michael Niedermayer
wrote:
Hi Martin
On Thu, Jul 10, 2025 at 02:35:10PM +0300, Martin Storsjö wrote:
> On Thu, 10 Jul 2025, Jiawei wrote:
>
> > Hi Martin,
> >
> > Is there any progress for this patch, should I resend
On Tue, 15 Jul 2025, Jiawei wrote:
FYI,
Reported Loongarch build fault with '-ftree-vectorize',
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=121064
and has been fixed with a gcc patch, it will be apply it gcc 16 release
version.
Thanks for reporting and getting that fixed! I see it's also
Hi everyone
If someone wants the FFv1 frame threading race fix backported:
its these 2 commits:
8d5efc218245c3f0559f48837b3e63e2932525e0 and
bcf08c11710cab5db8eb3d0774e1a93e322fb821
If these are not backported, our choice is to leave the bug or to disable
frame threading in favor of slice thread
On Mon, Aug 4, 2025 at 1:08 AM Michael Niedermayer
wrote:
>
> Hi Maryla
>
> On Wed, Jun 25, 2025 at 05:55:45PM +0200, Maryla Ustarroz-Calonge via
> ffmpeg-devel wrote:
> > Date: Wed, 25 Jun 2025 17:55:45 +0200
> > From: Maryla Ustarroz-Calonge
> > To: ffmpeg-devel@ffmpeg.org
> > Subject: [PATCH
In general, a provider code corresponds to a company/organization, and
the name should be that of the company, not of a given feature.
The feature is signalled in the "provider oriented code".
The exception is HDR Vivid, where the code 0x0004 indicates the HDR Vivid
feature itself rather than CUVA
ITU-T T.35 provider codes are attributed by national bodies and it's
possible to have collisions across countries. This is why the country code
must always be checked as well.
Use if statements rather than nested switches which would be unreadable.
Signed-off-by: Maryla Ustarroz-Calonge
---
lib
This is in preparation to change the switch statement to if/else.
Signed-off-by: Maryla Ustarroz-Calonge
---
libavcodec/libdav1d.c | 165 ++
1 file changed, 88 insertions(+), 77 deletions(-)
diff --git a/libavcodec/libdav1d.c b/libavcodec/libdav1d.c
index
Yes. Sorry I missed that one.
On Tue, Aug 5, 2025 at 11:31 AM Nicolas George wrote:
>
> Robert Nagy (HE12025-08-05):
> > On a side note. Shouldn't ffprobe also report the detect alpha mode if
> > the decoder/container supports it?
>
> You mean like
>
> [PATCH v2 02/18] fftools/ffprobe: add suppor
Robert Nagy (HE12025-08-05):
> On a side note. Shouldn't ffprobe also report the detect alpha mode if
> the decoder/container supports it?
You mean like
[PATCH v2 02/18] fftools/ffprobe: add support for AVFrame.alpha_mode
?
> On Tue, Aug 5, 2025 at 11:16 AM Nicolas George wrote:
Please rememb
On a side note. Shouldn't ffprobe also report the detect alpha mode if
the decoder/container supports it?
On Tue, Aug 5, 2025 at 11:16 AM Nicolas George wrote:
>
> Nicolas George (HE12025-08-05):
> > > I will repeat myself briefly here that such a flag should be an opt-out,
> > > not
> > > an op
Nicolas George (HE12025-08-05):
> > I will repeat myself briefly here that such a flag should be an opt-out, not
> > an opt-in. Supporting premultiplied alpha should be the default assumption
> > unless provable otherwise.
>
> Absolutely not.
>
> Do you dereference a pointer when you can prove it
Niklas Haas (HE12025-08-05):
> I will repeat myself briefly here that such a flag should be an opt-out, not
> an opt-in. Supporting premultiplied alpha should be the default assumption
> unless provable otherwise.
Absolutely not.
Do you dereference a pointer when you can prove it cannot be NULL o
Just wanted to clarify that this feature is not just academic but
something that is quite important for broadcasters where we often
receive/send content of mixed alpha type.
Users often don't know the difference between the alpha type and send
material in whatever mode their editing software happe
On Sun, 03 Aug 2025 20:15:09 +0200 Nicolas George wrote:
> Nicolas George (HE12025-08-03):
> > I will send the series here in a few hours.
>
> Here is a series of patch. I am absolutely not sure I found all the
> filters that could be flagged, but the rest can be done as the need
> arises.
>
> Not
This fixes two old TODO's in ipv6 multicast handling.
A helper function to iterate over all interfaces added to
help join the multicast group on interface if approperite.
The default value is IN6ADDR_ANY (::) and it then joins all interfaces
that are up and have multicast support. Local address ca
PR #20118 opened by Lynne
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20118
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20118.patch
This commit adds support for Vulkan labelling.
>From 8ad2415d9b56572d2c7fa321eb1febf73eb713fc Mon Sep 17 00:00:00 2001
From: Lynne
Date: Tue, 5 Aug
39 matches
Mail list logo
