On Wed, 2025-05-21 at 19:25 +, softworkz . wrote:
> What I mean and what the comment in the ticket is probably
> suggesting,
> is that the HLS demuxer should URL-encode the URL after combining the
> base url with the segment file name before making a request for the
> segment.
Ah, sure. That
On Wed, 2025-05-21 at 18:56 +, softworkz . wrote:
> Why do you think it would require control over the server side?
The original ticket is referring to HLS, and specifically the manifest
of HLS, which means a remotely-hosted M3U playlist.
In principle, the user could download the playlist, co
> I really wonder how Kieran can't be embarrassed trying such maneuvers which
> are so obvious to everybody.
I really wonder how you can't be embarrassed sending what imo is the
worst patchset in the history of the project.
Instead of acknowledging that, it's deflecting and playing the victim
you
On Thu, May 22, 2025 at 12:24 PM Michael Niedermayer
wrote:
> 4. "seeing the scale of memory leaks." try to compare this to
>IAMF "git log --grep IAMF --oneline", IAMF is after a year still receiving
>frequent security fixes. This is just as a comparission
This is completely different, on
On Thu, 22 May 2025, 15:03 softworkz ., wrote:
>
>
> > -Original Message-
> > From: ffmpeg-devel On Behalf Of Kieran
> > Kunhya via ffmpeg-devel
> > Sent: Donnerstag, 22. Mai 2025 14:46
> > To: FFmpeg development discussions and patches
> > C
Hi,
On Monday, May 5th, 2025 at 4:07 PM, Marvin Scholz wrote:
> From: Erik Linge [email protected]
>
>
> Co-authored-by: Marvin Scholz [email protected]
>
> Signed-off-by: Marvin Scholz [email protected]
>
> ---
> libavformat/Makefile | 1 +
> libavformat/rtpdec.c | 8 +
> libavformat/rtpd
On Wed, May 21, 2025 at 2:00 PM Niklas Haas wrote:
>
> From: Niklas Haas
>
> This covers most 8-bit and 16-bit ops, and some 32-bit ops. It also covers all
> floating point operations. While this is not yet 100% coverage, it's good
> enough for the vast majority of formats out there.
>
> Of speci
: ffmpeg-devel On Behalf Of Kyle
> > Swanson
> > > Sent: Mittwoch, 21. Mai 2025 22:11
> > > To: FFmpeg development discussions and patches <
> [email protected]>
> > > Subject: Re: [FFmpeg-devel] Graphprint Patches Overview
> > >
> > >
On Fri, May 23, 2025 at 12:33 PM Michael Niedermayer
wrote:
>
> Hi Kieran
>
> On Fri, May 23, 2025 at 08:51:43AM +0100, Kieran Kunhya via ffmpeg-devel
> wrote:
> [...]
> > I appreciate the way the 2024 organisers ran STF was not exactly stellar
>
> It seems every
On Fri, May 23, 2025 at 3:50 PM Devin Heitmueller
wrote:
>
> Hello Michael,
>
> On Fri, May 23, 2025 at 5:45 AM Michael Niedermayer
> wrote:
> > On Thu, May 22, 2025 at 07:55:40PM -0400, Devin Heitmueller wrote:
> > > On Thu, May 22, 2025 at 7:42 PM Kieran Kunhya
This commit closes trac ticket 10679.
Signed-off-by: Timothy Allen
---
libavformat/hls.c | 9 +
libavformat/url.c | 35 +++
libavformat/url.h | 9 +
3 files changed, 53 insertions(+)
diff --git a/libavformat/hls.c b/libavformat/hls.c
index c7b65
:40PM -0400, Devin Heitmueller wrote:
> > > > On Thu, May 22, 2025 at 7:42 PM Kieran Kunhya via ffmpeg-devel
> > > > wrote:
> > > > > I wanted to put on the record that adding RaptorQ to FFmpeg isn't
> > > > > maintenance of FFmpeg.
> &
Hi,
>
>
> But Lynne is insisting it's not a protocol. The work would just be the low
> level RaptorQ algorithm.
>
> UDP based retransmit/FEC protocols are essentially impossible to develop
> well without an event loop / timers.
>
> You can look at libsrt and librist of examples of how trying
Hello,
I wanted to put on the record that adding RaptorQ to FFmpeg isn't
maintenance of FFmpeg.
It's adding an obscure FEC protocol to FFmpeg, which is not going to be
implemented well without an event loop anyway.
I do not think it's a suitable STF project.
Regards,
Kieran Kunhya
_
On Fri, 23 May 2025, 04:44 Lynne, wrote:
> On 23/05/2025 08:42, Kieran Kunhya via ffmpeg-devel wrote:
> > Hello,
> >
> > I wanted to put on the record that adding RaptorQ to FFmpeg isn't
> > maintenance of FFmpeg.
>
> It isn't -- it's research.
&
On Fri, 23 May 2025, 04:44 Lynne, wrote:
> On 23/05/2025 08:42, Kieran Kunhya via ffmpeg-devel wrote:
> > Hello,
> >
> > I wanted to put on the record that adding RaptorQ to FFmpeg isn't
> > maintenance of FFmpeg.
>
> It isn't -- it's research.
&g
On Fri, 23 May 2025, 10:58 Michael Niedermayer,
wrote:
> On Fri, May 23, 2025 at 11:45:14AM +0200, Michael Niedermayer wrote:
> > Hi
> [...]
> > > I agree with Kieran that this seems to largely be outside the STF
> > > objectives (i.e. sustainability for open source projects).
> >
> > A new imple
On Fri, 23 May 2025, 10:45 Michael Niedermayer,
wrote:
> Hi
>
> On Thu, May 22, 2025 at 07:55:40PM -0400, Devin Heitmueller wrote:
> > On Thu, May 22, 2025 at 7:42 PM Kieran Kunhya via ffmpeg-devel
> > wrote:
> > > I wanted to put on the record that
On Fri, 23 May 2025, 12:33 Michael Niedermayer,
wrote:
> Hi Kieran
>
> On Fri, May 23, 2025 at 08:51:43AM +0100, Kieran Kunhya via ffmpeg-devel
> wrote:
> [...]
> > I appreciate the way the 2024 organisers ran STF was not exactly stellar
>
> It seems every mail you pos
Tested to pass FATE on Linux and Windows.
Checkasm numbers vs the existing SSE2 code on Zen 5 (Strix Halo):
vp9_inv_adst_adst_16x16_sub16_add_10_sse2: 1041.8 ( 1.92x)
vp9_inv_adst_adst_16x16_sub16_add_10_avx512icl: 132.5 (15.06x)
vp9_inv_dct_adst_16x16_sub16_add_10_sse2: 901.0 ( 1
On Fri, 23 May 2025, 21:35 Michael Niedermayer,
wrote:
> Hi Kieran
>
> On Fri, May 23, 2025 at 04:45:53PM +0100, Kieran Kunhya via ffmpeg-devel
> wrote:
> > On Fri, May 23, 2025 at 4:00 PM Kieran Kunhya
> wrote:
> > >
> > > On Fri, May 23, 2025 at
On Thu, 22 May 2025, 07:32 Jiawei, wrote:
> 在 2025/5/22 2:21, Frank Plowman 写道:
> > On 21/05/2025 11:17, Jiawei wrote:
> >> 在 2025/5/21 14:52, Nicolas George 写道:
> >>> Jiawei (HE12025-05-21):
> particularly improving
> performance on x86_64 (AVX), AR
>
> > - The doors will be closed for all future
>
> As i predicted elsewhere privately, I do not belive Paul will return
> unless his fork fails.
> The more successfull his fork is, the less likely it is that he will
> return
>
> Also its like 18 months since paul forked and the way he speaks reall
On Sun, 1 Jun 2025, 20:23 Michael Niedermayer,
wrote:
> Hi James
>
> On Sun, Jun 01, 2025 at 02:27:37PM -0300, James Almer wrote:
> > On 6/1/2025 12:22 PM, Michael Niedermayer wrote:
> > > Hi all
> > >
> > > almpeg is now merged upto 1 months ago. (and since last merge it
> contains
> > > bits of
On Sun, 1 Jun 2025, 16:22 Michael Niedermayer,
wrote:
> Hi all
>
> almpeg is now merged upto 1 months ago. (and since last merge it contains
> bits of AGPL code)
>
> The question now is, how does the community want to proceed from here?
>
> I think there are mainly 2 options
>
> 1. People review
On Sat, 31 May 2025, 10:17 Dmitriy Kovalenko,
wrote:
> This patch integrates so called double bufferring when we are loading
>
Nit: I am not sure this is what most people refer to as "double buffering"
Kieran
>
___
ffmpeg-devel mailing list
ffmpeg-de
>
> }
> +
> +if (strm.avail_out == 0) {
> +chunk *= 8;
>
*8 seems high
+uint8_t *tmp_buf = av_realloc(buf, chunk + 1);
> +if (!tmp_buf) {
> +inflateEnd(&strm);
> +av_free(buf);
> +return AVERROR(E
>
> Let's get to the cast of the final chapter:
>
> - Lynne
> - Nicolas George
> - Kieran Kunyar
>
> The fact all of us (who normally disagree on various technical topics)
agree about the deficiencies of your patch speaks volumes.
Kieran
>
___
ffmpeg-de
--- Begin Message ---
On Thu, 19 Jun 2025, 20:12 Michael Niedermayer,
wrote:
> We have been contacted by Monet du Plessis of the etherium foundation and
> Natascha Buck (Grants at the Better Internet Foundation)
>
> "The Ethereum Foundation is thrilled to inform you that your contribution
> to
>
--- Begin Message ---
Martijn van Beurden wrote:
>So, there is a proposal to close the flac and flac-dev mailing
>lists.
>I'd like to know whether you would be willing to move over to
>GitHub discussions. GitHub would be the first choice because
>most discussions already happen there anyway.
--- Begin Message ---
Oops, sorry for the noise. Reto--- End Message ---
___
ffmpeg-devel mailing list
[email protected]
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
[email protected] wit
--- Begin Message ---
On Mon, 16 Jun 2025, 10:29 Reto Kromer via ffmpeg-devel, <
[email protected]> wrote:
>
>
>
> -- Forwarded message --
> From: Reto Kromer
> To: FFmpeg development discussions and patches
> Cc:
> Bcc:
> Date: Mon, 16
--- Begin Message ---
Friendly ping.
This feature came up during the review of "[PATCH 2/2] avcodec/libaom:
Add tests for HDR10+ metadata support"
https://ffmpeg.org/pipermail/ffmpeg-devel/2025-June/344683.html
On Tue, Jun 10, 2025 at 5:02 PM Maryla Ustarroz-Calonge via
ffmpeg-de
--- Begin Message ---
On Friday, June 13th, 2025 at 4:03 PM, Tristan Matthews
wrote:
> ---
> libavcodec/h264dsp.h | 2 +-
> libavcodec/h264idct.h | 2 +-
> libavcodec/h264idct_template.c | 2 +-
> libavcodec/loongarch/h264dsp_loongarch.h | 2 +-
> libavcodec/loongarch/h264idct.S | 2 +-
> libavcodec/
--- Begin Message ---
On 2025-06-21 00:03 +0200, Kacper Michajlow wrote:
> On Fri, 20 Jun 2025 at 22:26, Hendrik Leppkes
> wrote:
> >
> > On Fri, Jun 20, 2025 at 9:25 PM Timo Rothenpieler
> > wrote:
> > >
> > > On 19.06.2025 22:21, Martin Storsjö wrote:
> > > > On Fri, 13 Jun 2025, Martin Storsj
--- Begin Message ---
On Tue, Jun 24, 2025 at 8:48 AM Kieran Kunhya wrote:
>
>
>
> On Tue, 24 Jun 2025, 07:00 compn, wrote:
>>
>> On Mon, 23 Jun 2025 21:20:56 +0100, Derek Buitenhuis wrote:
>>
>> > This was pushed with outstanding reservations, with no positive
>> > affirmation or review from any
--- Begin Message ---
On Tue, Jun 24, 2025 at 4:53 PM Michael Niedermayer
wrote:
>
> Hi Derek
>
> so many different subjects you raise here, ill try to reply seperately
> to keep it clean and terse
>
> On Tue, Jun 24, 2025 at 06:24:32AM +0100, Derek Buitenhuis wrote:
> > Hi,
> >
> > On Monday, Jun
--- Begin Message ---
On Wed, 25 Jun 2025, 02:09 compn, wrote:
> On Tue, 24 Jun 2025 10:22:26 +0200, Kieran Kunhya via ffmpeg-devel
> wrote:
>
> > On Tue, 24 Jun 2025, 09:28 compn, wrote:
> >
> > > On Tue, 24 Jun 2025 07:48:30 +0100, Kieran Kunhya via ffmpeg-devel
--- Begin Message ---
address sanitizer showed some leaks of drmVersion structs.
`vaapi_device_create` did not call drmFreeVersion in all possible code
paths.
Signed-off-by: Tim Blechmann
---
libavutil/hwcontext_vaapi.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/libavutil/hwcontext_
--- Begin Message ---
On Fri, 13 Jun 2025, 12:56 Tomas Härdin, wrote:
> Hi
>
> In my fiddling with fragmented indexes in mov.c I ran cross
> mov_fix_index(), which has been in the codebase since September 2016.
> The intent of this function is to implement limited support for edit
> lists (elst).
--- Begin Message ---
Sent with Proton Mail secure email.
On Monday, June 16th, 2025 at 6:53 AM, Andreas Rheinhardt
wrote:
> Patch attached.
>
LGTM, and sorry about that, for future reference did you do anything in
particular (instrumentation wise) to catch the stack overflow? I tried m
On Sat, Jun 7, 2025 at 9:06 AM Clément Péron
wrote:
>
> The rtp_set_prft() function incorrectly calculates the timestamp delta
> when RTP timestamps wrap around the 32-bit boundary. The current code:
>
> delta_timestamp = (int64_t)timestamp - (int64_t)s->last_rtcp_timestamp;
>
> treats both ti
--- Begin Message ---
> On Jun 9, 2025, at 05:17, Michael Niedermayer wrote:
>
> Hi
>
> On Sun, Jun 08, 2025 at 04:52:35PM -0700, rcombs via ffmpeg-devel wrote:
>> Date: Sun, 8 Jun 2025 16:52:35 -0700
>> From: rcombs
>> To: [email protected]
>>
--- Begin Message ---
On Mon, 9 Jun 2025, 20:24 ffmpegagent,
wrote:
> The "killer feature" returns!
>
> Different approach - same procedure:
>
> * Add -sg to your FFmpeg command line
> * But now it's not
>* ./ffmpeg -sg x but
>* ./ffmpeg-sg x
>
Why does this need to be part of
Signed-off-by: Jack Lau
---
libavformat/whip.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/libavformat/whip.c b/libavformat/whip.c
index 0671e23635..e7cd57400d 100644
--- a/libavformat/whip.c
+++ b/libavformat/whip.c
@@ -1733,6 +1733,12 @@ static av_cold int whip_init(AVFormatContex
On Thu, Jun 5, 2025 at 3:55 PM Jack Lau via ffmpeg-devel
wrote:
>
> Signed-off-by: Jack Lau
> ---
> libavformat/whip.c | 6 ++
> 1 file changed, 6 insertions(+)
>
> diff --git a/libavformat/whip.c b/libavformat/whip.c
> index 0671e23635..e7cd57400d 100644
> --- a
On Thu, 5 Jun 2025, 00:03 Jack Lau, wrote:
>
>
> > On Jun 5, 2025, at 06:20, Kieran Kunhya via ffmpeg-devel <
> [email protected]> wrote:
> >
> > On Wed, 4 Jun 2025, 12:46 Steven Liu, wrote:
> >
> >> Kieran Kunhya via ffmpeg-
add the missing data structure pkey in the tls_context
properly set this pkey and free it
Signed-off-by: Jack Lau
---
libavformat/tls_openssl.c | 33 -
1 file changed, 20 insertions(+), 13 deletions(-)
diff --git a/libavformat/tls_openssl.c b/libavformat/tls_open
--- Begin Message ---
This muxer has been marked AVFMT_EXPERIMENTAL.
Add a note in muxers.texi that WHIP is an experimental feature
This patch doesn't effect WHIP usage command, as WHIP always
needs to be explicitly specified
The details as follows:
https://ffmpeg.org/pipermail/ffmpeg-devel/2025
--- Begin Message ---
Apologies for the late reply.
Yeah, the other solution to solve this problem is to sprinkle .gotpcrel all
over the x86 assembly whenever it tries to access a variable that's defined
in the C file.
Using `attribute(small)`, as in this patch, is behind a macro that implies
tha
--- Begin Message ---
On Tue, 24 Jun 2025, 07:00 compn, wrote:
> On Mon, 23 Jun 2025 21:20:56 +0100, Derek Buitenhuis wrote:
>
> > This was pushed with outstanding reservations, with no positive
> > affirmation or review from any other devs, and without a push noticed
> > to say it was going to b
--- Begin Message ---
Hi Martin!
On 2025-06-21 13:37 +0300, Martin Storsjö wrote:
> > On 21. Jun 2025, at 12.20, Alexander Strasser via ffmpeg-devel
> > wrote:
> >
> >
> > On 2025-06-21 00:03 +0200, Kacper Michajlow wrote:
> >> On Fri, 20 Jun 202
--- Begin Message ---
replace AV_OPT_FLAG_DECODING_PARAM to ENCODING
mark this ignore_ipv6 flag could ignore any ipv6 ICE candidate,
preventing “No route to host” errors on devices without IPv6 connectivity.
Signed-off-by: Jack Lau
---
libavformat/whip.c | 25 +++--
1 file c
--- Begin Message ---
Signed-off-by: Jack Lau
---
libavformat/whip.c | 21 ++---
1 file changed, 14 insertions(+), 7 deletions(-)
diff --git a/libavformat/whip.c b/libavformat/whip.c
index 84c2092e5e..ef219defb7 100644
--- a/libavformat/whip.c
+++ b/libavformat/whip.c
@@ -1898,13
--- Begin Message ---
Signed-off-by: Jack Lau
---
libavformat/whip.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/libavformat/whip.c b/libavformat/whip.c
index 710f24fc5a..a6827d3478 100644
--- a/libavformat/whip.c
+++ b/libavformat/whip.c
@@ -1885,13 +1885,13
--- Begin Message ---
mark this ignore_ipv6 flag could ignore any ipv6 ICE candidate,
preventing “No route to host” errors on devices without IPv6 connectivity.
Signed-off-by: Jack Lau
---
libavformat/whip.c | 13 +
1 file changed, 13 insertions(+)
diff --git a/libavformat/whip.c b/
--- Begin Message ---
Signed-off-by: Jack Lau
---
libavformat/whip.c | 21 ++---
1 file changed, 14 insertions(+), 7 deletions(-)
diff --git a/libavformat/whip.c b/libavformat/whip.c
index 84c2092e5e..6a33966472 100644
--- a/libavformat/whip.c
+++ b/libavformat/whip.c
@@ -1898,13
--- Begin Message ---
On Thu, Jun 12, 2025 at 6:48 PM Devin Heitmueller
wrote:
>
> On Thu, Jun 12, 2025 at 12:27 PM Maryla Ustarroz-Calonge via
> ffmpeg-devel wrote:
> > -- Forwarded message --
> > From: Maryla Ustarroz-Calonge
> > To: ffmpeg-devel
--- Begin Message ---
api doc: https://docs.openssl.org/1.0.2/man3/BIO_s_mem
In higher versions (openssl 1.0.2 and higher),
the function signature is BIO *BIO_new_mem_buf(const void *buf, int len),
so passing a const string doesn't cause an warnings.
However, in lower versions of OpenSSL,
the func
--- Begin Message ---
Hello to all, I didn't mean to publish this, this was in my drafts and
it somehow was sent without me asking to, I ask you to ignore this as I
didn't mean to send this
My apologizes
On 6/15/25 6:03 PM, Emma Romano wrote:
---
libavcodec/vp3.c | 3 +++
1 file changed, 3
--- Begin Message ---
On Thu, Jun 5, 2025 at 9:27 AM Andreas Rheinhardt
wrote:
>
> Maryla Ustarroz via ffmpeg-devel:
> > On Fri, May 30, 2025 at 2:52 PM Andreas Rheinhardt
> > wrote:
> >>
> >> Maryla Ustarroz-Calonge via ffmpeg-devel:
> >>> The new
--- Begin Message ---
On Wed, Jun 25, 2025 at 9:23 PM James Zern wrote:
>
> On Tue, Jun 10, 2025 at 8:02 AM Maryla Ustarroz-Calonge via
> ffmpeg-devel wrote:
> >
> >
> >
> >
> > -- Forwarded message --
> > From: Maryla Ustarroz-Ca
--- Begin Message ---
Hi Derek!
On 2025-06-23 22:40 +0100, Derek Buitenhuis wrote:
> Libav is no longer extant.
^
Seems I just learned a new English word...
IMHO removal is OK. Should be no longer needed in this specific form.
I see the tool is still mentioned in doc/libav-m
--- Begin Message ---
On Thu, Jun 26, 2025 at 12:00 AM Hendrik Leppkes
wrote:
>
> On Thu, Jun 26, 2025 at 2:58 AM Michael Niedermayer
> wrote:
> >
> > Hi
> >
> > some people use webp apparently, and we have no decoder
> >
>
> libavcodec/webp.c is a decoder.
>
The missing piece is animated webp d
>
>
>
> About 2. (IMHO)
> * The solution is to hire carl or someone else (or find a volunteer)
> to do this work. Changing the tracker will not fix this.
>
> FFlabs should have enough captial to hire carl for this. People should
> ask
> FFlabs to hire him and carl to accept to be hired for t
y, 19 July 2025 at 8:18 PM
To: FFmpeg development discussions and patches
Subject: Re: [FFmpeg-devel] [PATCH] avfilter: add inverse tone mapping
EXTERNAL: Use caution when clicking on links or opening attachments.
On Sat, 19 Jul 2025 at 16:13, Sarthak Indurkhya via ffmpeg-devel <
ffmpeg-devel
>
> >
> > Maybe some spam filter is somehow interfering, and eating some mails?
> >
> > > Going over the whole list is not particularly difficult (the contents
> of
> > > mails and patches may be difficult but the managing of mails/patches
> is not)
> > >
> > > But with forgejo now there are mails
On Fri, 25 Jul 2025, 12:41 Nicolas George, wrote:
> Jacob Lifshay (HE12025-07-24):
> > ok, I prefer to never do that though because it makes reading the
> > patches very annoying. Anyone should be able to read the patches
> > without having to download files and open them in their editor (which
>
On Sat, Jul 12, 2025 at 12:06 AM Michael Niedermayer
wrote:
>
> Hi Maryla
>
> On Thu, Jul 10, 2025 at 06:29:06PM +0200, Maryla Ustarroz via ffmpeg-devel
> wrote:
> [...]
> > Friendly ping.
> > This is a v2 of the patch that includes the shorter -c flag in
> >
On Mon, Jul 28, 2025 at 10:07 PM Stefano Sabatini wrote:
>
> Hi, sorry for the slow reply.
>
> On date Tuesday 2025-06-10 17:02:05 +0200, ffmpeg-devel Mailing List wrote:
> > From: Maryla Ustarroz-Calonge
> > Subject: [PATCH] ffprobe: add -codec: option
> > Date: Tue, 10 Jun 2025 17:02:05 +0200
>
On Thu, Jul 31, 2025 at 12:01 AM Stefano Sabatini wrote:
>
> On date Friday 2025-06-27 10:23:56 +0200, ffmpeg-devel Mailing List wrote:
> > From: Maryla Ustarroz-Calonge
> > Subject: [PATCH v2] ffprobe: add -codec: option
> > Date: Fri, 27 Jun 2025 10:23:56 +0200
> > To: [email protected]
>
On 2025-07-31 00:02 +0200, Nicolas George wrote:
> Niklas Haas (HE12025-07-30):
> > What you pointed out is pointess nitpicking, and I could point you to
> > plenty of other comments by "experienced" FFmpeg developers who have done
> > the same in the past, presumably without having sat through dia
On 2025-07-18 17:42 +0200, Kacper Michajlow wrote:
> On Fri, 11 Jul 2025 at 23:41, Michael Niedermayer
> wrote:
> > On Thu, Jul 10, 2025 at 02:35:10PM +0300, Martin Storsjö wrote:
[...]
> >
> > > I'm unsure if we should allow it everywhere, and just single out loongarch
> > > as a case where it is
On Mon, 4 Aug 2025, 00:31 Jiasheng Jiang,
wrote:
> Add av_free() to free s.temp_dwt_buffer and s.temp_idwt_buffer at the end
> of the function to avoid memory leak.
>
> Fixes: 5d48e4eafa ("Merge commit
> 'a6a750c7ef240b72ce01e9653343a0ddf247d196'")
> Signed-off-by: Jiasheng Jiang
> ---
> libavc
On Mon, 4 Aug 2025, 01:14 [email protected], <
[email protected]> wrote:
> This patch was not written by AI. I used a static analysis tool to detect
> several similar issues, which led to a number of similar-looking
> submissions.
>
> -Jiasheng
>
Sorry about that, thank you fo
>
> The only solution is more manpower.
>
It's really a huge mystery why developers are leaving.
We may never know the answer.
Kieran
>
___
ffmpeg-devel mailing list
[email protected]
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscr
On 2025-08-03 17:04 +0200, Timo Rothenpieler wrote:
> On 8/3/2025 3:26 PM, Michael Niedermayer wrote:
> > On Sun, Aug 03, 2025 at 01:45:17PM +0200, Timo Rothenpieler wrote:
> > > On 8/3/2025 9:41 AM, Michael Niedermayer wrote:
> > > > Hi
> > > >
> > > > can we have a tag that causes "automerge on
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-dev
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,
>
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
On 2025-08-05 22:18 +0200, Nicolas George wrote:
> 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.
I'm a bit undecided
On Wed, Jun 25, 2025 at 5:55 PM Maryla Ustarroz-Calonge
wrote:
>
> From: Maryla
>
> 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
Hi Nicolas!
Am 29. Juli 2025 10:55:15 MESZ schrieb Nicolas George :
>Michael Niedermayer (HE12025-07-29):
>> regression fix for this is here:
>> https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20055
>
>I see no commit message.
>
>I see removing opening braces without removing them.
>
>(see attached sc
Hello,
It seem there is strong evidence that AI wrote TLS code as part of the
WHIP patch. It goes without saying why this is bad. Further discussion
here:
https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20053
This patch was pushed without ML review.
I think this code should be removed before the FFm
[AMD Official Use Only - AMD Internal Distribution Only]
Without this fix, av1 vaapi encoding on navi3x (vcn4) is broken.
Thanks,
Ruijing
-Original Message-
From: ffmpeg-devel On Behalf Of David Rosca
Sent: Thursday, July 24, 2025 6:04 AM
To: [email protected]
Subject: Re: [FFmpeg
Am 29. Juli 2025 22:59:22 MESZ schrieb Nicolas George :
>Alexander Strasser via ffmpeg-devel (HE12025-07-29):
>> You are looking at the overview with latest events for that PR.
>>
>> To see the the individual commits select
>> that view at the top. Or if you want
On Wed, Jul 23, 2025 at 10:59 AM 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 c
On Mon, Aug 4, 2025 at 10:04 PM Hendrik Leppkes wrote:
> On Mon, Aug 4, 2025 at 7:19 PM Jacob Lifshay
> wrote:
> >
> >
> >
> > On August 4, 2025 6:49:20 AM PDT, Alan Kelly via ffmpeg-devel <
> [email protected]> wrote:
> > > The gather i
On Tue, Jul 29, 2025 at 11:40 PM Michael Niedermayer
wrote:
>
> On Tue, Jul 29, 2025 at 10:04:51PM +0100, Frank Plowman wrote:
> > On 28/07/2025 15:20, Michael Niedermayer wrote:
> > > Hi
> > >
> > > regression: issue aaddresses a regression
> > > bug:something is not working
> > >
> > > T
The gather is unmasked but the instruction does a merge into ymm4, which
depends on the value of ymm4 from the previous loop iteration. The
out-of-order scheduler does not know statically that the instruction is
fully unmasked, preventing parallel out-of-order execution of the
gathers.
---
libswsc
On 2025-08-02 20:08 +0200, Nicolas George wrote:
> Alexander Strasser via ffmpeg-devel (HE12025-08-02):
> > I don't understand what the issue with the commit message is?
>
> Two issues:
OK, now I understand what you mean.
It wasn't clear to me from your origin
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:39PM +0200, Michael Niedermayer wrote:
> [...]
> > The solutions are obvious:
> > 1. ignore security and supply chain a
Hi,
Since this is my first FFmpeg patch I’m not sure if I should include anything
extra to make the review easier, like logs, test results, or more explanation.
Please let me know if there’s anything I can add or do differently.
Best regards,
Jan Studený
On May 1, 2025 at 20:13 +0300, Jan Stude
Patch version 6:
- Added support for all `cextern` symbols.
- Added attribute_mcmodel_small attribute to other DECLARE_ASM* macros.
- Used DECLARE_ASM* macros for symbols that are being accessed from
assembly but still marked with non-ASM DECLARE macros.
On Tue, May 6, 2025 at 4:25 PM Pranav Kant
By default, all globals in C/C++ compiled by clang are allocated
in non-large data sections. See [1] for background on code models.
For PIC (Position independent code), this is fine as long as binary is
small but as binary size increases, users maybe want to use medium/large
code models (-mcmodel=m
Placed in a new separate file as the existing combined MMX/SSE/AVX
file is humongous and takes forever to assemble as is.
This adds ~16 KiB of .text. The existing 8bpc asm is ~240 KiB of which
the corresponding AVX2 functions makes up ~42 KiB.
Tested to pass FATE on Linux and Windows.
Checkasm n
On Wed, May 14, 2025 at 8:26 AM Michael Niedermayer
wrote:
>
> Hi
>
> On Wed, May 14, 2025 at 11:41:35AM +0100, Kieran Kunhya via ffmpeg-devel
> wrote:
> > On Wed, May 14, 2025 at 11:21 AM Michael Niedermayer
> > wrote:
> > >
> > > Hi Andrew
> &g
On Wed, May 14, 2025 at 11:21 AM Michael Niedermayer
wrote:
>
> Hi Andrew
>
> On Wed, May 14, 2025 at 05:54:54AM +0300, Andrew Randrianasulu wrote:
> > ср, 14 мая 2025 г., 03:55 Andrew Randrianasulu :
> >
> > >
> > >
> > > вт, 6 мая 2025 г., 02:27 Michael Niedermayer :
> > >
> > >> This will be av
Good day
I wanted to offer a discussion of the referenced patch.
I have found that, when a link in an extended M3U file (as used by HLS)
includes a colon, FFmpeg will fail to load the file.
The bug has already been reported: https://trac.ffmpeg.org/ticket/10679
The error reads:
[hls @ 0x78dea40
This commit closes trac ticket 10679.
Signed-off-by: Timothy Allen
---
libavformat/tests/url.c | 8 +++-
libavformat/url.c | 8 +++-
tests/ref/fate/url | 7 ++-
3 files changed, 20 insertions(+), 3 deletions(-)
diff --git a/libavformat/tests/url.c b/libavformat/tests/url.
2201 - 2300 of 3425 matches
Mail list logo
