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

2025-02-14 Thread Kieran Kunhya via ffmpeg-devel
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] Fw: GSoC 2025: Please review your Project Ideas lists

2025-02-14 Thread Kieran Kunhya via ffmpeg-devel
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

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

2025-02-08 Thread Kieran Kunhya via ffmpeg-devel
$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] GSoC 2025

2025-02-11 Thread Kieran Kunhya via ffmpeg-devel
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] [RFC] GSoC 2025 SDR Cleanup

2025-02-11 Thread Kieran Kunhya via ffmpeg-devel
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] [RFC] GSoC 2025 SDR Cleanup

2025-02-11 Thread Kieran Kunhya via ffmpeg-devel
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

2025-02-11 Thread Kieran Kunhya via ffmpeg-devel
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: > &g

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

2025-03-25 Thread Kieran Kunhya via ffmpeg-devel
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] Access to the ARM server

2025-03-25 Thread Kieran Kunhya via ffmpeg-devel
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] [PATCH] swscale/x86/rgb2rgb: optimize AVX2 version of uyvytoyuv422

2025-04-05 Thread Kieran Kunhya via ffmpeg-devel
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

2025-03-30 Thread Kieran Kunhya via ffmpeg-devel
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] APV codec with OpenAPV support

2025-04-22 Thread Kieran Kunhya via ffmpeg-devel
h implementations and > integrate them in parallel in FFmpeg. > > > > What's your opinion about that? > > > > Regards, > > Dariusz > Hi Dariusz, The general "policy" is that external libraries are not used if we al

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

2025-04-21 Thread Kieran Kunhya via ffmpeg-devel
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] [RFC] STF 2025

2025-04-22 Thread Kieran Kunhya via ffmpeg-devel
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] FFmpeg Community Committee – Updates & Next Steps

2025-03-04 Thread Kieran Kunhya via ffmpeg-devel
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] CC statement on alleged insults against the GSoC student et al

2025-03-04 Thread Kieran Kunhya via ffmpeg-devel
> > 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

2025-03-04 Thread Kieran Kunhya via ffmpeg-devel
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

2025-03-04 Thread Kieran Kunhya via ffmpeg-devel
> > 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] [RFC] Experiment: enable github pull requests

2025-02-12 Thread Kieran Kunhya via ffmpeg-devel
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] I've written a filter in Rust

2025-02-21 Thread Kieran Kunhya via ffmpeg-devel
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

2025-02-21 Thread Kieran Kunhya via ffmpeg-devel
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

2025-02-21 Thread Kieran Kunhya via ffmpeg-devel
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] [PATCH] tools: Add binaries to .gitignore

2025-02-23 Thread Kieran Kunhya via ffmpeg-devel
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] [BASIC QUESTION] Profiling tool for ffmpeg

2025-02-24 Thread Kieran Kunhya via ffmpeg-devel
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] FFmpeg Community Committee – Updates & Next Steps

2025-02-26 Thread Kieran Kunhya via ffmpeg-devel
nd let the volunteers of the CC do their job. Hi Vittorio, A quick reminder that questioning the unelected people who run our infrastructure in a wholly secretive fashion is unacceptable but questioning the elected CC is perfectly fine. I thought you knew the rules here by

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

2025-05-07 Thread Kieran Kunhya via ffmpeg-devel
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] [PATCH 1/2] Remove libpostproc

2025-05-14 Thread Kieran Kunhya via ffmpeg-devel
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

2025-05-14 Thread Kieran Kunhya via ffmpeg-devel
t all plugins > (in fact i intend to include libpostproc in the next relaase) I do not think we should have a plugin API. As we have seen from other open source multimedia projects like GStreamer, the only use case will be to incorporate binary blobs. FFmpeg will then get the support burden fr

Re: [FFmpeg-devel] Graphprint Patches Overview

2025-05-21 Thread Kieran Kunhya via ffmpeg-devel
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] [ANNOUNCEMENT] almpeg

2025-05-25 Thread Kieran Kunhya via ffmpeg-devel
it if you could come back. Regards, Michael Niedermayer " * Narrator: It is not a better community Regards, Kieran Kunhya On Sun, May 25, 2025 at 8:23 PM Michael Niedermayer wrote: > > Hi all > > Id like to announce that ive setup a repository to merge pauls work of > the las

Re: [FFmpeg-devel] (no subject)

2025-05-27 Thread Kieran Kunhya via ffmpeg-devel
> > - 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

2025-05-26 Thread Kieran Kunhya via ffmpeg-devel
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] FFmpeg Community Committee – Updates & Next Steps

2025-05-24 Thread Kieran Kunhya via ffmpeg-devel
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] Previous trac server hosting Was: STF RaptorQ

2025-05-24 Thread Kieran Kunhya via ffmpeg-devel
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] [PATCH] MAINTAINERS: Add entry for samples-request

2025-05-24 Thread Kieran Kunhya via ffmpeg-devel
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] Vittorio's mailinglist ban, git access removal and message deletion (was: Worsening messages)

2025-05-14 Thread Kieran Kunhya via ffmpeg-devel
t; > "I am not trying to be anyone's saviour, I'm trying to think about the > future and not be sad" - Elon Musk > > ___ > ffmpeg-devel mailing list > ffmpeg-devel@ffmpeg.org > https://ffmpeg.org/mai

Re: [FFmpeg-devel] Graphprint Patches Overview

2025-05-22 Thread Kieran Kunhya via ffmpeg-devel
> 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

2025-05-22 Thread Kieran Kunhya via ffmpeg-devel
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

2025-05-22 Thread Kieran Kunhya via ffmpeg-devel
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] [PATCH v2 14/17] swscale/x86: add SIMD backend

2025-05-21 Thread Kieran Kunhya via ffmpeg-devel
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

2025-05-22 Thread Kieran Kunhya via ffmpeg-devel
: 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] STF RaptorQ

2025-05-23 Thread Kieran Kunhya via ffmpeg-devel
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

2025-05-23 Thread Kieran Kunhya via ffmpeg-devel
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

2025-05-23 Thread Kieran Kunhya via ffmpeg-devel
On Fri, May 23, 2025 at 4:00 PM Kieran Kunhya wrote: > > 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

[FFmpeg-devel] STF RaptorQ

2025-05-22 Thread Kieran Kunhya via ffmpeg-devel
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

Re: [FFmpeg-devel] STF RaptorQ

2025-05-22 Thread Kieran Kunhya via ffmpeg-devel
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. &

Re: [FFmpeg-devel] STF RaptorQ

2025-05-23 Thread Kieran Kunhya via ffmpeg-devel
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

2025-05-23 Thread Kieran Kunhya via ffmpeg-devel
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

2025-05-23 Thread Kieran Kunhya via ffmpeg-devel
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

2025-05-23 Thread Kieran Kunhya via ffmpeg-devel
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

2025-05-23 Thread Kieran Kunhya via ffmpeg-devel
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] gcc: Remove auto-vectorization limitation.

2025-05-23 Thread Kieran Kunhya via ffmpeg-devel
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] [PATCH 2/2] fftools/resman: use inflate loop with increasing buffer size

2025-05-30 Thread Kieran Kunhya via ffmpeg-devel
> > } > + > +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] The "bad" Patch

2025-05-31 Thread Kieran Kunhya via ffmpeg-devel
> > 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] [RFC] Cherry picks vs merges

2025-06-01 Thread Kieran Kunhya via ffmpeg-devel
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] [PATCH 2/2] swscale: Neon rgb_to_yuv_half process 32 pixels at a time

2025-05-31 Thread Kieran Kunhya via ffmpeg-devel
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] [RFC] Cherry picks vs merges

2025-06-01 Thread Kieran Kunhya via ffmpeg-devel
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

2025-06-02 Thread Kieran Kunhya via ffmpeg-devel
> > > - 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

<    5   6   7   8   9   10