Re: [FFmpeg-devel] [PATCH v2 1/2] avfilter/vf_blackdetect: add AVX2 SIMD version

On Fri, Jul 18, 2025 at 3:17 PM Kacper Michajlow wrote: > > On Fri, 18 Jul 2025 at 15:33, Kieran Kunhya via ffmpeg-devel > wrote: > > > > On Fri, Jul 18, 2025 at 2:22 PM Kacper Michajlow wrote: > > > > > > On Fri, 18 Jul 2025 at 14:46, Kier

Re: [FFmpeg-devel] [PATCH v2 1/2] avfilter/vf_blackdetect: add AVX2 SIMD version

On Fri, Jul 18, 2025 at 2:22 PM Kacper Michajlow wrote: > > On Fri, 18 Jul 2025 at 14:46, Kieran Kunhya via ffmpeg-devel > wrote: > > > > On Fri, Jul 18, 2025 at 1:41 PM Kacper Michajlow wrote: > > > > > > On Fri, 18 Jul 2025 at 14:14, Kier

Re: [FFmpeg-devel] [PATCH v2 1/2] avfilter/vf_blackdetect: add AVX2 SIMD version

On Fri, Jul 18, 2025 at 1:41 PM Kacper Michajlow wrote: > > On Fri, 18 Jul 2025 at 14:14, Kieran Kunhya via ffmpeg-devel > wrote: > > > > > blackdetect8_c:820.8 ( 1.00x) > > > blackdetect8_avx2:

Re: [FFmpeg-devel] [PATCH v2 1/2] avfilter/vf_blackdetect: add AVX2 SIMD version

> blackdetect8_c:820.8 ( 1.00x) > blackdetect8_avx2: 219.2 ( 3.74x) > blackdetect16_c: 372.8 ( 1.00x) > blackdetect16_avx2:201.4 ( 1.85x) > > Again,

Re: [FFmpeg-devel] [PATCH v2 0/3] Add OpenHarmony hardware codec wrapper

On Wed, Jul 16, 2025 at 3:08 PM Zhao Zhili wrote: > > > > > On Jul 6, 2025, at 16:05, Zhao Zhili > > wrote: > > > > From: Zhao Zhili > > > > v2: > > 1. Add encoder. > > 2. Trial refactor of decoder. > > > > Zhao Zhili (3): > > avutil/hwcontext: Add ohcodec device and pixel format > > avcodec/

Re: [FFmpeg-devel] [PATCH 3/5] avcodec/h264chroma_template: Replace variable by constant in chroma mc

On Sun, 13 Jul 2025, 02:11 Michael Niedermayer, wrote: > Signed-off-by: Michael Niedermayer > --- > libavcodec/h264chroma_template.c | 30 +++--- > 1 file changed, 15 insertions(+), 15 deletions(-) > > diff --git a/libavcodec/h264chroma_template.c > b/libavcodec/h264chro

Re: [FFmpeg-devel] [POLL] [VOTE] code.ffmpeg.org

On Sun, 13 Jul 2025, 22:47 Michael Niedermayer, wrote: > Hi Ronald > > On Sun, Jul 13, 2025 at 02:04:15PM -0400, Ronald S. Bultje wrote: > > G, preferably hosted by videolan. > > This poll really is about, what we should setup on our server. > > If you want to discuss giving up our autonomy (not

Re: [FFmpeg-devel] [POLL] [VOTE] code.ffmpeg.org

On Sun, 13 Jul 2025, 17:07 Timo Rothenpieler, wrote: > On 7/13/2025 5:57 PM, Michael Niedermayer wrote: > > Hi > > > > On Sun, Jul 13, 2025 at 01:58:44PM +0200, Timo Rothenpieler wrote: > > [...] > > > >> Just want to note that hosting Gitlab is quite a bit more expensive than > >> Forgejo, for w

Re: [FFmpeg-devel] [POLL] [VOTE] code.ffmpeg.org

G but hosted by videolan On Sun, 13 Jul 2025, 12:44 Michael Niedermayer, wrote: > Hi all > > Do people want Forgejo or Gitlab on code.ffmpeg.org for testing? > > F. code.ffmpeg.org should run Forgejo > G. code.ffmpeg.org should run Gitlab > > all GA members can vote, by publically replying here

Re: [FFmpeg-devel] [PATCH 2/3] libavcodec: add NETINT Quadra HW decoders & encoders

--- Begin Message --- On Tue, 8 Jul 2025, 02:00 Desmond Liu, wrote: > * As far as I know, these cards/units are not available to the general > public at all. > > The cards are available to the general public. See > https://netint.com/contact-us and send a message to sa...@netint.com >

Re: [FFmpeg-devel] [PATCH] avformat/rtsp: fix leak of options dict on error

--- Begin Message --- On Tue, 8 Jul 2025, 19:15 Marvin Scholz, wrote: > Fix CID 1655306 > --- > libavformat/rtsp.c | 3 +++ > 1 file changed, 3 insertions(+) > > diff --git a/libavformat/rtsp.c b/libavformat/rtsp.c > index 8d360b375f..0810c56a8b 100644 > --- a/libavformat/rtsp.c > +++ b/libavfor

Re: [FFmpeg-devel] [PATCH 3/5] avcodec/get_bits: Use FF_PTR_ADD() in init_get_bits()

--- Begin Message --- On Thu, 3 Jul 2025, 03:02 Michael Niedermayer, wrote: > Fixes: NULL + 0 > Fixes: > 421817631/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_APV_fuzzer-4957386534354944 > > Found-by: continuous fuzzing process > https://github.com/google/oss-fuzz/tree/master/projects/ffmpe

Re: [FFmpeg-devel] [PATCH] Revert "Add FUNDING.json"

--- Begin Message --- On Tue, 24 Jun 2025, 02:12 Michael Niedermayer, wrote: > Hi Derek > > You said > "The only mails you'll see from me in the future are code or reviews." > > On Mon, Jun 23, 2025 at 09:20:56PM +0100, Derek Buitenhuis wrote: > > This was pushed with outstanding reservations, >

Re: [FFmpeg-devel] [PATCH] Revert "Add FUNDING.json"

--- Begin Message --- On Tue, 24 Jun 2025, 09:28 compn, wrote: > On Tue, 24 Jun 2025 07:48:30 +0100, Kieran Kunhya via ffmpeg-devel > wrote: > > > On Tue, 24 Jun 2025, 07:00 compn, wrote: > > > > > On Mon, 23 Jun 2025 21:20:56 +0100, Derek Buitenhuis wrote: >

Re: [FFmpeg-devel] [PATCH] Revert "Add FUNDING.json"

--- 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

Re: [FFmpeg-devel] [PATCH] Revert "Add FUNDING.json"

--- 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

Re: [FFmpeg-devel] [PATCH] Revert "Add FUNDING.json"

--- 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

Re: [FFmpeg-devel] [PATCH] Revert "Add FUNDING.json"

--- 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

Re: [FFmpeg-devel] [PATCH] Add FUNDING.json

--- 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 >

Re: [FFmpeg-devel] [PATCH v6] gcc: Don't disable '-ftree-vectorize' if gcc version is 13 or newer

--- Begin Message --- On Mon, 16 Jun 2025, 10:29 Reto Kromer via ffmpeg-devel, < ffmpeg-devel@ffmpeg.org> wrote: > > > > -- Forwarded message -- > From: Reto Kromer > To: FFmpeg development discussions and patches > Cc: > Bcc: > Date: Mon, 16 Jun 2025 10:29:35 +0200 > Subject: Re

Re: [FFmpeg-devel] [RFC] Moving edit list handling out of demuxers

--- 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).

Re: [FFmpeg-devel] [PATCH 3/3] tools/ffmpeg-sg: Include show-graph wrapper script in build output

--- Begin Message --- On Wed, Jun 11, 2025 at 9:58 PM softworkz . wrote: > > > > > -Original Message- > > From: ffmpeg-devel On Behalf Of > > Marton Balint > > Sent: Mittwoch, 11. Juni 2025 21:18 > > To: FFmpeg development discussions and patches > de...@ffmpeg.org> > > Subject: Re: [FFm

Re: [FFmpeg-devel] [PATCH 0/3] tools/ffmpeg-sg: Add show-graph wrapper scripts (aka killer feature)

--- 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

Re: [FFmpeg-devel] [PATCH v2] rtpdec: Fix RTP timestamp wraparound in Producer Reference Time

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

Re: [FFmpeg-devel] [RFC] Subtitle Filtering Ramp-Up

On Sat, Jun 7, 2025 at 5:20 PM softworkz . wrote: > > > It's MythBusters Day! > = > > > Today: Busting the Lies of Nicolas George Can you stop spamming this list with your rants and get a blog or something? Kieran ___ ffmpeg-devel m

Re: [FFmpeg-devel] [PATCH v11 0/3] avutil/log: Add log flag to control printing of memory addresses

> > > #define LIBAVUTIL_VERSION_MAJOR 60 > --#define LIBAVUTIL_VERSION_MINOR 1 > -+#define LIBAVUTIL_VERSION_MINOR 2 > +-#define LIBAVUTIL_VERSION_MINOR 3 > ++#define LIBAVUTIL_VERSION_MINOR 4 >#define LIBAVUTIL_VERSION_MICRO Are you seriously expecting

Re: [FFmpeg-devel] [PATCH] avformat/dhav: Do not evaluate avio_size() multiple times

On Sat, 7 Jun 2025, 00:12 Michael Niedermayer, wrote: > Code like FFMIN(MAX_DURATION_BUFFER_SIZE, avio_size(s->pb)) is not safe > as FFMIN() is a macro and avio_size() is thus evaluated multiple > times > > CC: Justin Ruggles > Signed-off-by: Michael Niedermayer > --- > libavformat/dhav.c | 7

Re: [FFmpeg-devel] [PATCH] avformat/format: make experimental flag works for muxer

On Fri, 6 Jun 2025, 10:51 Michael Niedermayer, wrote: > On Fri, Jun 06, 2025 at 12:06:34AM +0800, Zhao Zhili wrote: > > From: Zhao Zhili > > > > --- > > libavformat/avformat.h | 3 +-- > > libavformat/format.c | 2 ++ > > 2 files changed, 3 insertions(+), 2 deletions(-) > > > > diff --git a/l

Re: [FFmpeg-devel] [PATCH] avformat/whip: set this muxer as experimental

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/libavformat/whip.c > +++ b/l

Re: [FFmpeg-devel] [PATCH v3] avformat/whip: Add WHIP muxer support for subsecond latency streaming

On Thu, 5 Jun 2025, 00:03 Jack Lau, wrote: > > > > On Jun 5, 2025, at 06:20, Kieran Kunhya via ffmpeg-devel < > ffmpeg-devel@ffmpeg.org> wrote: > > > > On Wed, 4 Jun 2025, 12:46 Steven Liu, wrote: > > > >> Kieran Kunhya via ffmpeg-

Re: [FFmpeg-devel] [PATCH v3] avformat/whip: Add WHIP muxer support for subsecond latency streaming

On Wed, 4 Jun 2025, 12:46 Steven Liu, wrote: > Kieran Kunhya via ffmpeg-devel 于2025年6月4日周三 > 19:35写道： > Hi Kieran, > > > > > @Andreas Rheinhardt > > Should we revert this? > > I believe it would be better to leave comments if there are any > concerns abo

Re: [FFmpeg-devel] [RFC] Cherry picks vs merges

> FFlabs depends on FFmpeg so its interrests in terms of FFmpeg complying > to all laws should be aligned here Interesting, so the person that complains about FFlabs having too much corporate control over FFmpeg is now ok to assume FFlabs legal opinion "align[ing]" with FFmpeg. Kieran __

Re: [FFmpeg-devel] [PATCH v3] avformat/whip: Add WHIP muxer support for subsecond latency streaming

@Andreas Rheinhardt Should we revert this? Kieran ___ 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

Re: [FFmpeg-devel] [RFC] Cherry picks vs merges

> > all members of fflabs where aware of it as i asked about the license > situation it in the private > fflabs IRC channel. I asked there because fflabs/jb has a lawyer > Do you understand that the lawyer of FFlabs represents the interests of FFlabs and does not represent the interests of FFmpeg?

Re: [FFmpeg-devel] [RFC] Cherry picks vs merges

> > > - 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

Re: [FFmpeg-devel] [RFC] Cherry picks vs merges

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

Re: [FFmpeg-devel] [RFC] Cherry picks vs merges

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

Re: [FFmpeg-devel] The "bad" Patch

> > 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

Re: [FFmpeg-devel] [PATCH 2/2] swscale: Neon rgb_to_yuv_half process 32 pixels at a time

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

Re: [FFmpeg-devel] [PATCH 2/2] fftools/resman: use inflate loop with increasing buffer size

> > } > + > +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

Re: [FFmpeg-devel] (no subject)

> > - adding vzeroupper: ~12% > This seems quite suspicious. Can you explain what you are doing here? Kieran > ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or

Re: [FFmpeg-devel] [PATCH v2 1/4] avcodec/h2645_vui: Ensure color primaries/trc/space isn't reserved value

On Mon, May 26, 2025 at 8:13 PM Zhao Zhili wrote: > > > > > On May 22, 2025, at 13:06, Zhao Zhili > > wrote: > > > > From: Zhao Zhili > > > > Fix error reported by swscaler: > > Unsupported input (Operation not supported): fmt:yuv420p csp:unknown > > prim:reserved trc:bt709 -> fmt:yuv420p csp:

Re: [FFmpeg-devel] [ANNOUNCEMENT] almpeg

Hi Michael, Here is how this should be handled. "Hi Paul, I'm sorry for aggressively trying to force SDR into the FFmpeg project over a period of several weeks in spite of objections from you and the community causing you to leave. FFmpeg is now a better community* and we would love it if you co

Re: [FFmpeg-devel] [PATCH] MAINTAINERS: Add entry for samples-request

Hi Michael, On Wed, 14 May 2025, 23:35 Michael Niedermayer, wrote: > On Sun, May 11, 2025 at 10:13:36PM +0200, Michael Niedermayer wrote: > > This is based on discussion with the GA and its simply the people > > who have done or tried to do some uploads recently. > > > > Everyone who has a shel

Re: [FFmpeg-devel] Previous trac server hosting Was: STF RaptorQ

On Sat, 24 May 2025, 17:39 Michael Niedermayer, wrote: > Hi > > On Fri, May 23, 2025 at 01:13:05PM +0100, Kieran Kunhya via ffmpeg-devel > wrote: > [...] > > > As an example i could have instead replied with a tone matching yours: > > > (below is a (true) exa

Re: [FFmpeg-devel] FFmpeg Community Committee – Updates & Next Steps

On Tue, 4 Mar 2025, 19:01 Kieran Kunhya, wrote: > > > On Tue, 4 Mar 2025, 11:17 Michael Niedermayer, > wrote: > >> Hi Kieran >> >> On Tue, Mar 04, 2025 at 08:13:11AM -0600, Kieran Kunhya via ffmpeg-devel >> wrote: >> [...] >> > Hi Michael,

Re: [FFmpeg-devel] gcc: Remove auto-vectorization limitation.

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

Re: [FFmpeg-devel] STF RaptorQ

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

Re: [FFmpeg-devel] STF RaptorQ

: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. > &

Re: [FFmpeg-devel] STF RaptorQ

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

Re: [FFmpeg-devel] STF RaptorQ

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

Re: [FFmpeg-devel] STF RaptorQ

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

Re: [FFmpeg-devel] STF RaptorQ

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

Re: [FFmpeg-devel] STF RaptorQ

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

Re: [FFmpeg-devel] STF RaptorQ

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

Re: [FFmpeg-devel] STF RaptorQ

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. &

[FFmpeg-devel] STF RaptorQ

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 _

Re: [FFmpeg-devel] Graphprint Patches Overview

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

Re: [FFmpeg-devel] Graphprint Patches Overview

> 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

Re: [FFmpeg-devel] Graphprint Patches Overview

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

Re: [FFmpeg-devel] Graphprint Patches Overview

: ffmpeg-devel On Behalf Of Kyle > > Swanson > > > Sent: Mittwoch, 21. Mai 2025 22:11 > > > To: FFmpeg development discussions and patches < > ffmpeg-devel@ffmpeg.org> > > > Subject: Re: [FFmpeg-devel] Graphprint Patches Overview > > > > > >

Re: [FFmpeg-devel] [PATCH v2 14/17] swscale/x86: add SIMD backend

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

Re: [FFmpeg-devel] Graphprint Patches Overview

On Wed, 21 May 2025, 01:45 softworkz ., wrote: > Hello, > > thanks again to all for the patches. I figured it might be a bit difficult > to > keep track of what has already been submitted and fixed and is still > pending, and I'm sorry that there has been some duplicate effort to fix the > same t

Re: [FFmpeg-devel] Vittorio's mailinglist ban, git access removal and message deletion (was: Worsening messages)

On Tue, 31 Dec 2024, 06:44 Michael Niedermayer, wrote: > Hi Ronald, Vittorio > > On Mon, Dec 30, 2024 at 11:05:59PM -0500, Ronald S. Bultje wrote: > > Hi Michael, > > > > On Mon, Dec 30, 2024 at 2:13 PM Michael Niedermayer < > mich...@niedermayer.cc> > > wrote: > > > > > Hi CC-2024 > > > > > > On

Re: [FFmpeg-devel] [PATCH 1/2] Remove libpostproc

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

Re: [FFmpeg-devel] [PATCH 1/2] Remove libpostproc

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

Re: [FFmpeg-devel] [PATCH 0/4] [Please Ignore] ci_test

On Wed, May 7, 2025 at 4:24 AM ffmpegagent wrote: > > This is for testing Patchwork CI builds, not for merging. > > softworkz (4): > ci_test: Fail configure > ci_test: Fail build > ci_test: Fail fate > ci_test: All good > > > > base-commit: 2b6303762fc0850b3bd841ebd234c336271f657c > Publis

Re: [FFmpeg-devel] [RFC] STF 2025

On Fri, 15 Nov 2024, 18:12 Thilo Borgmann via ffmpeg-devel, < ffmpeg-devel@ffmpeg.org> wrote: > Hi, > > Am 17.05.24 um 15:49 schrieb Michael Niedermayer: > > Hi all > > > > Before this is forgotten again, better start some dicsussion too early > than too late > > > > I propose that if we have the

Re: [FFmpeg-devel] APV codec with OpenAPV support

On Tue, 22 Apr 2025, 09:44 , wrote: > Hi, > > > > I'm Dariusz from Samsung Electronics, you can know me from last VDD in > Korea, I was presenting APV. > > > > I'm glad that Mark created native APV decoder. As you might know we're also > working on APV implementation for FFmpeg. > > Our approach

Re: [FFmpeg-devel] [PATCH] postproc/postprocess_template: Fix reading uninitialized pixels in dering_C()

On Tue, 22 Apr 2025, 00:44 Michael Niedermayer, wrote: > Sponsored-by: Sovereign Tech Fund > Signed-off-by: Michael Niedermayer > I thought we decided postproc work in STF wasn't going to happen? Note that the STF wiki doesn't mention anything about bugfixes to libpostproc. Kieran >

Re: [FFmpeg-devel] [PATCH] swscale/x86/rgb2rgb: optimize AVX2 version of uyvytoyuv422

On Mon, 3 Mar 2025, 16:38 Shreesh Adiga, <16567adigashre...@gmail.com> wrote: > On Thu, Feb 20, 2025 at 6:51 PM Shreesh Adiga > <16567adigashre...@gmail.com> wrote: > > > > Currently the AVX2 version of uyvytoyuv422 in the SIMD loop does the > following: > > 4 vinsertq to have interleaving of the

Re: [FFmpeg-devel] [PATCH] avcodec/nvenc: Use CBR filler data consistently across codecs

On Sun, Mar 30, 2025 at 12:04 AM Cameron Gutman wrote: > > Previously, AV1 used filler data with CBR by default while H.264 > and HEVC did not. Make this consistent by using filler data in > CBR mode across all codecs. > > Since there are valid reasons to use CBR with or without filler, > also add

Re: [FFmpeg-devel] Access to the ARM server

would like to report it. Kieran On Tue, Mar 25, 2025 at 8:55 AM Nicolas George wrote: > > Kieran Kunhya via ffmpeg-devel (HE12025-03-25): > > The server belongs to @Jean-Baptiste Kempf > > Are you saying that the tweet that says “giving ***us*** a 160-core ARM > server” (em

Re: [FFmpeg-devel] Access to the ARM server

On Tue, 25 Mar 2025, 08:47 Zhao Zhili, wrote: > Hi, > > From Twitter > > Unlike the majority of hardware/cloud companies, Ampere have supported > the FFmpeg project by giving us a 160-core ARM server for development. > > Is the Ampere ARM server still available? Is it only for FATE or other > par

Re: [FFmpeg-devel] CC statement on alleged insults against the GSoC student et al

> > Kierans reply later refered back to this: > > OMG a GSoC contributor is complaining about how hard the contribution > That's a selective quotation of an incomplete sentence. Kieran > ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffm

Re: [FFmpeg-devel] FFmpeg Community Committee – Updates & Next Steps

On Tue, 4 Mar 2025, 11:17 Michael Niedermayer, wrote: > Hi Kieran > > On Tue, Mar 04, 2025 at 08:13:11AM -0600, Kieran Kunhya via ffmpeg-devel > wrote: > [...] > > Hi Michael, > > > > Was all the STF discussion around the first application done in public? > &

Re: [FFmpeg-devel] CC statement on alleged insults against the GSoC student et al

> > Nevertheless, the CC does issue a warning regarding unnecessarily > offensive recent comments by Kieran on other topics, as well as for > initially failing to provide background and context regarding Paul’s > action on IRC. > Hi CC, What comments are these? This is very vague as to what I've

Re: [FFmpeg-devel] FFmpeg Community Committee – Updates & Next Steps

On Mon, 3 Mar 2025, 20:35 Michael Niedermayer, wrote: > Hi jb > > On Thu, Feb 27, 2025 at 12:11:39AM +0100, Jean-Baptiste Kempf wrote: > > On Wed, 26 Feb 2025, at 02:51, Michael Niedermayer wrote: > > > 1. I agree we need discussions, transparency and maybe IRC or some > other > > >audio/vide

Re: [FFmpeg-devel] FFmpeg Community Committee – Updates & Next Steps

> While people who spent a significant time of their life working on FFmpeg > may be great developers, their skillset might not be matching the one > needed to handle a community. > > Cmon we've been over these points, let's not rehash the same drama over and > over, and let the volunteers of the C

Re: [FFmpeg-devel] [BASIC QUESTION] Profiling tool for ffmpeg

On Mon, 24 Feb 2025, 06:43 Cesar Matheus, wrote: > Hi, I'm a CS student working on an optimisation of the ebur128 filter. > First I'm looking for the nicest way to get information on code performance. > I saw that the configuration flag "--enable-linux-perf" enables > Linux Performance Mo

Re: [FFmpeg-devel] [PATCH] tools: Add binaries to .gitignore

On Sun, 23 Feb 2025, 04:11 Frank Plowman, wrote: > On 09/02/2025 10:58, Frank Plowman wrote: > > Signed-off-by: Frank Plowman > > --- > > tools/.gitignore | 10 ++ > > 1 file changed, 10 insertions(+) > > > > diff --git a/tools/.gitignore b/tools/.gitignore > > index 7c45896923..f017fa2

Re: [FFmpeg-devel] I've written a filter in Rust

On Fri, 21 Feb 2025, 15:02 Soft Works, wrote: > > > > -Original Message- > > From: ffmpeg-devel On Behalf Of > > Kieran Kunhya via ffmpeg-devel > > Sent: Freitag, 21. Februar 2025 15:53 > > To: FFmpeg development discussions and patches >

Re: [FFmpeg-devel] I've written a filter in Rust

On Fri, 21 Feb 2025, 14:30 Soft Works, wrote: > > > > -Original Message- > > From: ffmpeg-devel On Behalf Of > > Michael Niedermayer > > Sent: Freitag, 21. Februar 2025 14:22 > > To: FFmpeg development discussions and patches > de...@ffmpeg.org> > > Subject: Re: [FFmpeg-devel] I've writ

Re: [FFmpeg-devel] I've written a filter in Rust

On Fri, 21 Feb 2025, 13:18 Lynne, wrote: > On 20/02/2025 14:06, Leandro Santiago wrote: > Regardless of the language, I disagree with using crates in the context > of FFmpeg, and any use of cargo. > I have no opinion on rust in FFmpeg but I broadly agree crates and cargo are not suited for FFmpe

Re: [FFmpeg-devel] Fw: GSoC 2025: Please review your Project Ideas lists

On Fri, 14 Feb 2025, 21:29 Steven Liu, wrote: > > > Kieran Kunhya via ffmpeg-devel 于2025年2月15日 > 周六04:21写道： > >> On Fri, Feb 14, 2025 at 7:28 PM Michael Niedermayer >> wrote: >> > >> > Hi everyone >> > >> > Please help improve the

Re: [FFmpeg-devel] Fw: GSoC 2025: Please review your Project Ideas lists

On Fri, Feb 14, 2025 at 7:28 PM Michael Niedermayer wrote: > > Hi everyone > > Please help improve the gsoc 2025 page > > 2 ideas are missing backup mentors, if you are able please > add yourself to them as backup mentor > > Also please add more ideas! > And help review the page and ideas to ensur

Re: [FFmpeg-devel] [RFC] Experiment: enable github pull requests

On Wed, 12 Feb 2025, 23:29 Timo Rothenpieler, wrote: > On 12.02.2025 23:16, Soft Works wrote: > > > > > >> -Original Message- > >> From: ffmpeg-devel On Behalf Of Timo > >> Rothenpieler > >> Sent: Mittwoch, 12. Februar 2025 23:05 > >> To: ffmpeg-devel@ffmpeg.org > >> Subject: Re: [FFmpeg

Re: [FFmpeg-devel] [RFC] GSoC 2025 SDR Cleanup

On Wed, 12 Feb 2025, 02:11 Michael Niedermayer, wrote: > On Wed, Feb 12, 2025 at 01:23:09AM +0000, Kieran Kunhya via ffmpeg-devel > wrote: > > Is this a joke? > > no > > It follows up on Jean Baptistes request here: > https://lists.ffmpeg.org/pipermail/ffmpeg-de

Re: [FFmpeg-devel] GSoC 2025

Adding @Cc This is a blatant attempt to push an unrelated pet project into FFmpeg under the Gsoc banner with no notice. It's also unfair to students applying as there was serious community pushback against this last time. Kieran On Wed, 12 Feb 2025, 01:16 Kieran Kunhya, wrote: > > > On Wed, 1

Re: [FFmpeg-devel] [RFC] GSoC 2025 SDR Cleanup

On Wed, 12 Feb 2025, 01:21 Michael Niedermayer, wrote: > Hi all > > Ive added SDR to our GSoC 2025 page as there was just a single project > on that page and the page needs to be more complete yesterday > > If people are against this say this NOW do not wait until we have accepted > a student and

Re: [FFmpeg-devel] GSoC 2025

On Wed, 12 Feb 2025, 00:20 Michael Niedermayer, wrote: > Hi everyone > > On Wed, Feb 12, 2025 at 06:30:11AM +0800, Steven Liu wrote: > > Michael Niedermayer 于2025年1月28日 周二10:21写道： > > > > > Hi > > > > > > Everyone interested in mentoring a project in 2025, please add your > > > idea(s) to [1]. >

Re: [FFmpeg-devel] [PATCH] checkasm/v210enc.c: Use checkasm_check_type

On Mon, Feb 10, 2025 at 12:40 PM Martin Storsjö wrote: > > On Sat, 8 Feb 2025, Kieran Kunhya via ffmpeg-devel wrote: > > > $subj > > > -if (memcmp(y0, y1, BUF_SIZE * sizeof(type)) > > \ > > -|| memcmp

[FFmpeg-devel] [PATCH] checkasm/v210enc.c: Use checkasm_check_type

$subj 0001-checkasm-v210enc.c-Use-checkasm_check_type.patch Description: Binary data ___ 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...@

Re: [FFmpeg-devel] Democratization work in progress draft v2

Hi Michael, On Sat, 1 Feb 2025, 22:27 Michael Niedermayer, wrote: > > Lets be carefull here with the words. But the awnser is "yes" > Many developers have been paid to write commits. employees, contractors, > students > As an FFlabs employee (which I believe is the biggest GA cohort) and shareh

Re: [FFmpeg-devel] Democratization

On Sat, 1 Feb 2025, 15:03 Michael Niedermayer, wrote: > Hi > > On Sat, Feb 01, 2025 at 02:48:51PM +0000, Kieran Kunhya via ffmpeg-devel > wrote: > > On Sat, 1 Feb 2025, 14:46 Michael Niedermayer, > > wrote: > > > > > Hi > > > > > > On

Re: [FFmpeg-devel] Democratization

On Sat, 1 Feb 2025, 14:46 Michael Niedermayer, wrote: > Hi > > On Wed, Jan 29, 2025 at 10:21:37PM +0100, Niklas Haas wrote: > > On Wed, 29 Jan 2025 21:51:27 +0100 Nicolas George > wrote: > > > Niklas Haas (12025-01-29): > [...] > > > > *Some members* of > > > what you call community have express

Re: [FFmpeg-devel] Democratization

On Wed, Jan 29, 2025 at 6:27 PM Marth64 wrote: > > Here is an idea, > Can we try to lay out the friction points in a table or bullet format > where we can separate the issue from emotion and direct name calling? > > For example, > " * Community has issue ABC but we can't move forward because senio

Re: [FFmpeg-devel] GSoC 2025

On Wed, Jan 29, 2025 at 7:01 PM Michael Niedermayer wrote: > > Hi Yigithan > > Its good that you bring these issues up. > Discussing about them is a step towards solving them > > see my coments inline below > > On Wed, Jan 29, 2025 at 06:51:40PM +0300, Yigithan Yigit wrote: > > Hi Michael, > > > >

Re: [FFmpeg-devel] [PATCH v2 00/11] fix broken CC detection and ffprobe fields (cover letter)

On Mon, Jan 27, 2025 at 7:03 PM Soft Works wrote: > > > From: ffmpeg-devel On Behalf Of > > Kieran Kunhya via ffmpeg-devel > > Sent: Monday, January 27, 2025 10:40 AM > > > While this is a very valid concern for some kinds of frame side > > data, it > >

Re: [FFmpeg-devel] [PATCH v2 00/11] fix broken CC detection and ffprobe fields (cover letter)

> > While this is a very valid concern for some kinds of frame side data, it > does not apply to CC data. It's either in every frame or none. If a > provider generally broadcasts CC, then it's always present in every frame, > even during programs for which no CC is available - it's always there. Li

  1   2   3   >