On Fri, 17 Jan 2025, 21:32 Romain Beauxis, wrote:
> Le ven. 17 janv. 2025 à 08:32, Kieran Kunhya
> a écrit :
> >
> > On Fri, Jan 17, 2025 at 2:24 PM Kieran Kunhya
> wrote:
> > >
> > > On Fri, Jan 17, 2025 at 2:00 PM Romain Beauxis <
> romain
and a lot of old
third-party products to get right. One change affects another and it's hard
to unit test.
I also asked developers of proprietary implementations and they said theirs
is much more messy but substantially more advanced than mine (doing full
matrix recursion).
Regards,
Kieran
> A simple and clean mpeg FEC implementation will do no harm to FFmpeg,
> instead it will improve FFmpegs capabilities.
For the reasons I have described this is not possible. It's similar to
the way the kernel hides all the idiosyncrasies of real world TCP.
Kieran
ash, infinite loop etc. Nor can it be "elegant".
The reality is it has heuristics to deal with the real world like any
loss tolerant protocol. This is in addition to the other issues this
implementation has.
Regards,
Kieran Kunhya
___
ffmpeg-devel mai
> Don't assume he will not extend the implementation. Ask him instead what
> he plans to do in the long term.
> And this could also be marked as experimental, in which case if
> abandoned or proven unstable for several real world cases, it can be
> removed or disabled.
"the most simple and elegant
On Fri, Jan 17, 2025 at 2:24 PM Kieran Kunhya wrote:
>
> On Fri, Jan 17, 2025 at 2:00 PM Romain Beauxis
> wrote:
> >
> > Hi,
> >
> > Le jeu. 16 janv. 2025 à 16:40, Kieran Kunhya
> > a écrit :
> > >
> > > On Thu, Jan 16, 2025 at 9:35 PM
On Fri, Jan 17, 2025 at 2:00 PM Romain Beauxis wrote:
>
> Hi,
>
> Le jeu. 16 janv. 2025 à 16:40, Kieran Kunhya
> a écrit :
> >
> > On Thu, Jan 16, 2025 at 9:35 PM Romain Beauxis
> > wrote:
> > >
> > > Le jeu. 16 janv. 2025 à 14:48, Kieran Kun
On Thu, Jan 16, 2025 at 9:35 PM Romain Beauxis wrote:
>
> Le jeu. 16 janv. 2025 à 14:48, Kieran Kunhya
> a écrit :
> >
> > On Thu, 16 Jan 2025, 20:15 Romain Beauxis, wrote:
> >>
> >> This patch implements the decoding logic for the FEC error-
> >>
On Thu, 16 Jan 2025, 20:48 Kieran Kunhya, wrote:
> On Thu, 16 Jan 2025, 20:15 Romain Beauxis,
> wrote:
>
>> This patch implements the decoding logic for the FEC error-
>> correction method described in the Pro-MPEG CoP #3-R2 FEC[1]
>>
>> We are still in the p
On Thu, 16 Jan 2025, 20:15 Romain Beauxis, wrote:
> This patch implements the decoding logic for the FEC error-
> correction method described in the Pro-MPEG CoP #3-R2 FEC[1]
>
> We are still in the process of testing this patch with our encoders but
> I wanted to send it now in case it could use
by their employers.
> +
> @bye
> --
>
Hi Michael,
Can you add that you are exempt from this as you are incorruptible?
Regards,
Kieran Kunhya
>
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ff
> In fact the current developers
> already WILL TODAY vote the way their employer wants them to
By that argument you will vote the way FFlabs wants to and therefore
are biased and must resign.
Unless you are somehow incorruptible compared to everyone else?
Regards,
Kieran
where you are in control as usual. Your recent
behaviour of condoning censorship during an election and blocking of
contributors on spurious grounds shows that.
Read Tom's quote again and practice what you preach.
Regards,
Kieran Kunhya
>
___
On Thu, 2 Jan 2025, 06:49 compn, wrote:
> On Thu, 2 Jan 2025 02:23:08 +0000, Kieran Kunhya via ffmpeg-devel wrote:
>
> > On Wed, Jan 1, 2025 at 11:10 PM compn wrote:
> > >
> > > On Tue, 31 Dec 2024 17:28:31 +, Kieran Kunhya via ffmpeg-devel
> > > wrote
On Wed, Jan 1, 2025 at 11:10 PM compn wrote:
>
> On Tue, 31 Dec 2024 17:28:31 +, Kieran Kunhya via ffmpeg-devel
> wrote:
>
> > I personally don't want any control (I am not in GA or CC), I want the
> > people to control FFmpeg.
>
> iirc someone wanted, to
> About a timescale, theres not a single proposal. Short of simply
> resigning and handing FFmpeg out to some random dictator who picks it up.
>
> There is a resposibility here. I cannot and will not simply leave FFmpeg
> to whoever likes to pick it up
Classic tin pot dictator behaviour, setting a
On Tue, 31 Dec 2024, 13:14 Michael Niedermayer,
wrote:
> In case most people want democratication and its actually an important
> thing
> for them. Then sure we will make it happen eventually.
> This is a non trivial problem though but i had a surprising "revelation"
> yesterday how this could be
just a statement from you saying
> you know him and hes still your good friend vittorio
>
Where's your verification? Any observer can see you are behaving
erratically. So why don't you verify yourself?
Some Animals are More Equal than Others.
Regards,
Kieran Kunhya
>
_
peg-devel/2023-September/314864.html?
> I guess there will be votes to remove me from everything.
> But dont fear, i will not abuse anything, i will resign from everything that
> a correct vote asks me to resign from.
Regards,
Kieran Kunhya
___
ffmpe
jury and executioner"?
If there was a Nobel Prize for Mental Gymnastics, this email would win.
Regards,
Kieran Kunhya
___
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".
On Tue, Dec 24, 2024 at 9:59 PM Marth64 wrote:
>
> After support was added for DVB 0502 Closed Caption coding,
What is "DVB 0502"?
Kieran
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubsc
On Sat, 28 Dec 2024, 01:20 James Almer, wrote:
> On 12/27/2024 10:15 PM, Vittorio Giovara wrote:
> > On Fri, Dec 27, 2024 at 8:04 PM James Almer wrote:
> >
> >> On 12/27/2024 9:58 PM, Vittorio Giovara wrote:
> >>> On Tue, Dec 24, 2024 at 11:46 AM Michael Niedermayer <
> >> mich...@niedermayer.cc
ay have seen on IRC I am in the process of writing assembly
lessons (which I have shared on IRC).
Please could I have access to FFmpeg Github so I can publish some assignments.
Regards,
Kieran Kunhya
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
htt
>
>
> On the ffmpeg side, development continued like before, with much less
> strife on the mailing-list. And almost every day, Michael would merge
> the changes in libav into ffmpeg. That was a tremendous work and I do
> not know how Michael managed to keep on top of it for years. We made a
> coll
Regards,
Kieran Kunhya
PS Here is a copy of the censored message:
Micheal, just as to recap the last few months...
- you joined the CC and stalled executive action that would have improved
the community (see the various emails you yourself leaked)
- you played some fun games with STF to get y
nts must not target
> individuals.
> +
Hi Michael,
Does your post on X calling VDD attendees "vultures" fall under this?
Or was that ok because you decided retroactively that it was a "joke"?
Regards,
Kieran Kunhya
___
ffm
It's Christmas day, give it a rest.
Kieran
On Wed, Dec 25, 2024 at 1:31 PM Michael Niedermayer
wrote:
>
> Hi Community, Community Commitee, Moderators
>
> The message: lists.ffmpeg.org pipermail ffmpeg-devel/2024-December/337868.html
> Is unacceptable. We had alot of messages but this one went t
On Sun, 22 Dec 2024, 15:14 Michael Niedermayer,
wrote:
> I think what we need is some friendly smiles, some mutual respect,
> some virtual hugs and mutual tolerance. We can do the opposite, but it
> will make noone happier.
>
translation: everyone must agree with me
This plays out the same way
else {
> deblock_topleft = (sl->mb_x > 0);
> --
> 2.43.0
Hi Lingyi,
Thank you for your patch. Would it be possible to create a FATE test for this?
https://trac.ffmpeg.org/wiki/FATE/AddingATest
Regards,
Kieran Kunhya
___
ffmpeg
On Thu, Dec 19, 2024 at 9:11 PM compn wrote:
>
> On Thu, 19 Dec 2024 20:40:55 +, Kieran Kunhya via ffmpeg-devel
> wrote:
>
> > Please can you confirm you will be resigning your moderator status in light
> > of the election censorship you have undertaken while at t
On Thu, 19 Dec 2024, 20:38 compn, wrote:
> On Thu, 19 Dec 2024 20:35:43 +0000, Kieran Kunhya via ffmpeg-devel
> wrote:
>
> > On Thu, 19 Dec 2024, 20:30 compn, wrote:
> >
> > > On Thu, 19 Dec 2024 20:15:10 +, Kieran Kunhya via ffmpeg-devel
> > > wro
On Thu, 19 Dec 2024, 20:30 compn, wrote:
> On Thu, 19 Dec 2024 20:15:10 +0000, Kieran Kunhya via ffmpeg-devel
> wrote:
>
> > Some Animals are More Equal Than Others.
> >
> > Kieran
>
> and now a CC candidate calling devs animals ?
>
This is one of th
On Thu, Dec 19, 2024 at 7:52 PM Michael Niedermayer
wrote:
>
> Hi compn
>
> On Thu, Dec 19, 2024 at 06:16:03AM -1000, compn wrote:
> > On Thu, 19 Dec 2024 08:58:14 +0000, Kieran Kunhya via ffmpeg-devel
> > wrote:
> >
> > > Hello,
> > >
> &g
On Thu, Dec 19, 2024 at 7:25 PM Michael Niedermayer
wrote:
>
> Hi Kieran
>
> First before replying, id like to say, that i hope we can resolve this and
> in the future work together in a mutually more friendly way.
>
> On Wed, Dec 18, 2024 at 10:18:20PM -0500, Kieran Ku
it not happened?
You can't complain it the CC fails to act when it has voted for something
to happen but is not capable of acting on the vote.
Regards,
Kieran Kunhya
>
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/
ng
to happen but is not capable of acting on the vote.
Regards,
Kieran Kunhya
-- Forwarded message -
From:
Date: Thu, 19 Dec 2024, 08:55
Subject: Your message to ffmpeg-devel awaits moderator approval
To:
Your mail to 'ffmpeg-devel' with the subject
Re: [FFmpeg-d
> 1a. Prior context:
> For a long time FFmpeg booths where organized by various FFmpeg developers
> like Thilo but also others. They where always announced publically, they
> surely had a touch of hobbyists and a "non professional" community
>
> On NAB 2023 theres a booth paid by VideoLabs, with Vi
On Fri, 13 Dec 2024, 16:38 Romain Beauxis, wrote:
> Le ven. 13 déc. 2024 à 16:42, Romain Beauxis
> a écrit :
> >
> > This patch adds parameters to pick specific ports for the two FEC error-
> > correction streams associated with a Pro-MPEG CoP #3-R2 FEC streams.
> >
> > Radio France is currently
On Fri, 13 Dec 2024, 13:41 Niklas Haas, wrote:
> On Fri, 13 Dec 2024 01:37:34 +0000 Kieran Kunhya via ffmpeg-devel <
> ffmpeg-devel@ffmpeg.org> wrote:
> > On Fri, 13 Dec 2024, 00:39 Michael Niedermayer,
> > wrote:
> >
> > > Hi
> > >
> &g
On Fri, 13 Dec 2024, 10:14 Nicolas George, wrote:
> Kieran Kunhya via ffmpeg-devel (12024-12-13):
> > Then the conclusion in your example is wrong.
>
> No it is not. Either you misunderstood what I explained — I am guessing
> you only read it superficially, you did not actuall
On Fri, 13 Dec 2024, 10:00 Nicolas George, wrote:
> Kieran Kunhya via ffmpeg-devel (12024-12-13):
> > Where is the second sample rate stored in wav?
>
> Nowhere, obviously. I am surprised somebody who has been in the project
> for more than 12 years still does not know how it
On Fri, 13 Dec 2024, 09:31 Nicolas George, wrote:
> Kieran Kunhya via ffmpeg-devel (12024-12-13):
> > Does FFmpeg even support a new sample rate per AVFrame?
>
> Generate a 48000 Hz MP3.
> Generate a 32000 Hz MP3.
> Concatenate them.
> Convert the result to wave.
>
On Fri, 13 Dec 2024, 02:46 Michael Niedermayer,
wrote:
> Hi
>
> On Fri, Dec 13, 2024 at 01:40:43AM +0000, Kieran Kunhya via ffmpeg-devel
> wrote:
> > On Thu, 12 Dec 2024, 13:07 Nicolas Gaullier, >
> > wrote:
> >
> > > >De : ffmpeg-devel de la
On Thu, 12 Dec 2024, 13:07 Nicolas Gaullier,
wrote:
> >De : ffmpeg-devel de la part de Anton
> Khirnov
> >Envoyé : jeudi 12 décembre 2024 09:36
> >
> >I am not intimately familiar with these formats and their mutual
> >relationship, so these problems you refer to are not clear to me.
> >What I
On Fri, 13 Dec 2024, 00:39 Michael Niedermayer,
wrote:
> Hi
>
> On Thu, Dec 12, 2024 at 12:54:29PM +, Nicolas Gaullier wrote:
> [...]
> > This is a significant work with some weird things like dealing with a
> truncated sample rate
> > and droping one sample from time to time to keep sync. An
Hello,
This person asked for coverity access:
https://x.com/acentauri92/status/1867186643704099105
I don't know if they should have access.
Kieran
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
T
On Thu, Dec 5, 2024 at 5:04 PM Michael Niedermayer
wrote:
>
> Hi Kieran
>
> On Wed, Dec 04, 2024 at 09:51:23PM +0000, Kieran Kunhya via ffmpeg-devel
> wrote:
> > Hi Michael,
> >
> > Are you able to document the differences between source.ffmpeg.org and
>
On Thu, Dec 5, 2024 at 2:29 PM Nicolas Gaullier
wrote:
>
> >De : Kieran Kunhya
> >Envoyé : mercredi 4 décembre 2024 23:06
> >
> >> - a s337m decoder: it includes a resampler: output and input sample_rate
> >> are the same, sync is always correct. It would b
> - a s337m decoder: it includes a resampler: output and input sample_rate
> are the same, sync is always correct. It would be possible to implement
> a full pcm fallback, but currently only a silence/pcm fallback is
> provided. A 'passthrough' option is also provided and would make it
> possible t
ccess this resource."
Regards,
Kieran Kunhya
PS: This also begs the question what the issue is with VideoLAN
hosting gitlab if they already host (some?) of our Git
On Mon, Dec 2, 2024 at 8:03 PM Michael Niedermayer
wrote:
>
> Hi
>
> On Mon, Dec 02, 2024 at 09:12:55AM -1000, com
On Wed, 27 Nov 2024, 16:56 Michael Niedermayer,
wrote:
> Hi Kieran
>
> On Wed, Nov 27, 2024 at 12:01:03AM +0000, Kieran Kunhya via ffmpeg-devel
> wrote:
> > On Tue, 26 Nov 2024, 23:32 Michael Niedermayer,
> > wrote:
> >
> > > Signed-off-by: Michael Nied
4-11-22", though I accept this could be a coincidence.
https://who.is/whois/avcodec.org
Regards,
Kieran Kunhya
___
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".
On Wed, 20 Nov 2024, 20:36 James Almer, wrote:
> On 11/20/2024 5:03 PM, Michael Niedermayer wrote:
> > On Tue, Nov 19, 2024 at 07:00:47PM -0500, Vittorio Giovara wrote:
> >> On Tue, Nov 19, 2024 at 6:23 PM Michael Niedermayer <
> mich...@niedermayer.cc>
> >> wrote:
> >>
> >>> Signed-off-by: Micha
On Sun, 24 Nov 2024, 19:09 Michael Niedermayer,
wrote:
> And i hear almost everyone at VDD are old man. FFmpeg cannot be run by
> just old man. There is a need for young people and need for new ideas.
Then stop blocking a move to Gitlab based on false concerns of paranoia.
Using a mailing list
On Sun, 24 Nov 2024, 19:09 Michael Niedermayer,
wrote:
> Hi Kieran
>
> I think this is off topic for this thread, but i will reply with adjusted
> Subject and as a new thread
>
> On Sun, Nov 24, 2024 at 02:58:29PM +0000, Kieran Kunhya via ffmpeg-devel
> wrote:
> >
gt; Like other rules, fair enforcement depends on context and community input.
Hi Michael,
Seeing as you are (disrespectfully) using an LLM to answer Mailing
List emails, I thought I would do the same:
Question:
"In the following email, confirm that Michael Niedermayer agrees to
give root acc
On Sun, 17 Nov 2024, 10:03 Anton Khirnov, wrote:
> Quoting Michael Niedermayer (2024-11-17 01:42:20)
> > I think this would work better than TC or nothing process.
> >
> > Signed-off-by: Michael Niedermayer
> > ---
> > doc/developer.texi | 3 +++
> > 1 file changed, 3 insertions(+)
> >
> > diff
On Wed, 13 Nov 2024, 00:10 Michael Niedermayer,
wrote:
> Hi
>
> On Tue, Nov 12, 2024 at 10:38:09PM +0000, Kieran Kunhya via ffmpeg-devel
> wrote:
> > On Tue, 12 Nov 2024, 21:03 Michael Niedermayer,
> > wrote:
> >
> > > On Tue, Nov 12, 2024 at 05:32:40PM +0
On Tue, 12 Nov 2024, 21:03 Michael Niedermayer,
wrote:
> On Tue, Nov 12, 2024 at 05:32:40PM +, Derek Buitenhuis wrote:
> > On 11/12/2024 5:07 PM, James Almer wrote:
> > > I personally don't agree with giving the domain/trademark to the
> general
> > > assembly, as some have argued. It's just
On Tue, 12 Nov 2024, 04:07 compn, wrote:
> haven't seen arpi in a while so remove his root authorized key + remove
> him from maintainers. maybe he'll come back?
>
> anyone know how to contact tim nicholson? his mails are
> bouncing. https://uk.linkedin.com/in/tim-nicholson-7a2a3963
This is all
On Mon, Nov 11, 2024 at 5:31 PM compn wrote:
>
> On Mon, 11 Nov 2024 17:00:42 +
> Derek Buitenhuis wrote:
>
> > This only convinces me further that it this whole setup ins't for for
> > purpose, and is being run by people who have no concept of actual
> > security. This is totally insane.
>
>
On Tue, 22 Oct 2024, 07:25 Michael Niedermayer,
wrote:
> On Mon, Oct 21, 2024 at 07:32:20PM +0200, AndreaMastroberti wrote:
> > ---
> > doc/filters.texi | 14 +++
> > libavfilter/ssim.h| 6 +
> > libavfilter/version.h | 4 +-
> > libavfilter/vf_ssim.c | 277
On Fri, 8 Nov 2024, 06:07 Vittorio Giovara,
wrote:
> On Thu, Nov 7, 2024 at 1:03 PM Michael Niedermayer >
> wrote:
>
> > Hi all
> >
> > On Thu, Nov 07, 2024 at 12:11:49AM +0100, Michael Niedermayer wrote:
> > > Hi all
> > >
> > > Should libpostproc be split out into a seperate source repository
On Thu, Oct 31, 2024 at 6:54 PM Dmitrii Ovchinnikov
wrote:
>
> If there are no comments, I plan to merge this patch at the end of the
> week. I will update the title and description to match the current version
> of the patch.
IMO patches like this playing with sleep() are completely
unacceptable
On Mon, Sep 23, 2024 at 8:56 PM Anton Khirnov wrote:
>
> Quoting Kieran Kunhya via ffmpeg-devel (2024-09-23 21:30:09)
> > > On Mon, Sep 23, 2024 at 4:45 PM Kieran Kunhya via ffmpeg-devel
> > > wrote:
> > >>
> > >> On Mon, Sep 23, 2024 at 3:27 PM
> On Mon, Sep 23, 2024 at 4:45 PM Kieran Kunhya via ffmpeg-devel
> wrote:
>>
>> On Mon, Sep 23, 2024 at 3:27 PM Anton Khirnov wrote:
>> >
>> > Quoting Antoni Bizoń (2024-09-23 10:09:51)
>> > > I understand that the r_frame_rate is the lowest f
On Mon, Sep 23, 2024 at 3:27 PM Anton Khirnov wrote:
>
> Quoting Antoni Bizoń (2024-09-23 10:09:51)
> > I understand that the r_frame_rate is the lowest framerate with which
> > all timestamps can be represented accurately. And I know it is just a
> > guess. But why did the logic behind the calcul
On Mon, Aug 19, 2024 at 7:31 PM Timo Rothenpieler wrote:
>
> On 19.08.2024 16:23, Araz Iusubov wrote:
> > From: Evgeny Pavlov
> >
> > This commit increase precision of Sleep() function on Windows.
> > This fix reduces the sleep time on Windows to improve AMF encoding
> > performance on low resolu
On Fri, Jun 14, 2024 at 1:53 PM Paul B Mahol wrote:
>
>
>
> On Fri, Jun 14, 2024 at 2:41 PM Kieran Kunhya via ffmpeg-devel
> wrote:
>>
>> On Sun, Jun 9, 2024 at 2:39 AM Andreas Rheinhardt
>> wrote:
>> >
>> > The H.264 decoder does not
On Sun, Jun 9, 2024 at 2:39 AM Andreas Rheinhardt
wrote:
>
> The H.264 decoder does not support draw_horiz_band (it does not have
> the AV_CODEC_CAP_DRAW_HORIZ_BAND), making ff_h264_draw_horiz_band()
> legally dead. The function here always calls draw_horiz_band
> in coded order, although the defa
In this project we prefer internal decoders to external libs.
On Fri, 17 May 2024, 18:20 Cosmin Stejerean via ffmpeg-devel, <
ffmpeg-devel@ffmpeg.org> wrote:
>
>
> > On May 14, 2024, at 9:28 AM, Lynne via ffmpeg-devel <
> ffmpeg-devel@ffmpeg.org> wrote:
> >
> > On 14/05/2024 17:09, Christian Bart
On Mon, 13 May 2024, 02:32 Michael Niedermayer,
wrote:
> On Mon, May 06, 2024 at 03:23:07AM +0200, Michael Niedermayer wrote:
> > Fixes: CID1439574 Dereference after null check
> >
> > Sponsored-by: Sovereign Tech Fund
> > Signed-off-by: Michael Niedermayer
> > ---
> > libavcodec/h264_slice.c |
Sent from my mobile device
On Thu, 2 May 2024, 15:54 Ondřej Fiala, wrote:
> On Wed May 1, 2024 at 1:01 AM CEST, Andrew Sayers wrote:
> > On Tue, Apr 30, 2024 at 09:05:05PM +0200, Ondřej Fiala wrote:
> > > [...]
> >
> > IMHO, GitHub have improved that user experience significantly in recent
> yea
On Thu, 11 Apr 2024, 16:42 James Almer, wrote:
> Some interlaced h264 samples may export one caption per field.
>
> Signed-off-by: James Almer
> ---
> libavutil/frame.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/libavutil/frame.c b/libavutil/frame.c
> index 0775e2a
the rest of my thoughts. Microsoft are not the
only company with this attitude.
Regards,
Kieran Kunhya
>
>-
>
> Raphael
>
>
>
> *From:* Kieran Kunhya
> *Sent:* Wednesday, April 3, 2024 12:39 PM
> *To:* FFmpeg development discussions and patches
> *Cc:* Satter,
reed otherwise.
Regards,
Kieran Kunhya
On Wed, 3 Apr 2024, 16:52 Satter, Raphael (Reuters) via ffmpeg-devel, <
ffmpeg-devel@ffmpeg.org> wrote:
> Dear FFMPEG community,
>
> This is Raphael Satter, a journalist with Reuters. I saw your thread on X
> about your experience with Mi
On Sat, 30 Mar 2024 at 17:30, Michael Niedermayer
wrote:
> On Sat, Mar 30, 2024 at 11:51:17AM -0300, James Almer wrote:
> > On 3/30/2024 11:02 AM, Michael Niedermayer wrote:
> > > Iam not 100% sure this is the best place to put this. But we should
> somewhere
> > > describe what differences are e
On Wed, 27 Mar 2024 at 14:03, Michael Niedermayer
wrote:
> On Fri, Feb 09, 2024 at 03:19:58PM +, Anton Khirnov wrote:
> > ffmpeg | branch: master | Anton Khirnov | Thu Feb
> 1 08:57:24 2024 +0100| [ca18bb597223b3df5bbf8a1836d157ba58b62570] |
> committer: Anton Khirnov
> >
> > lavf/demux: sto
On Mon, 25 Mar 2024 at 21:10, Michael Niedermayer
wrote:
> On Mon, Mar 25, 2024 at 09:20:25PM +0100, Lynne wrote:
> > Mar 25, 2024, 14:50 by ffm...@haasn.xyz:
> >
> > > On Mon, 25 Mar 2024 07:20:56 +0100 "Jean-Baptiste Kempf" <
> j...@videolan.org> wrote:
> > >
> > >> Hello,
> > >>
> > >> On Mon,
> You've merged nothing yet and you want push access already?
>
I think this was done in good-faith saying they want to maintain. I
wouldn't antagonise people for no reason.
Kieran
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org
On Thu, 21 Mar 2024 at 13:13, Andreas Rheinhardt <
andreas.rheinha...@outlook.com> wrote:
> Andreas Rheinhardt:
> > When the compiler chooses to inline put_amf_string(pb, ""),
> > the avio_write(pb, "", 0) can be avoided. Happens with
> > Clang-17 with -O1 and higher and GCC 13 with -O2 and higher
On Tue, 19 Mar 2024 at 15:27, James Almer wrote:
> On 3/19/2024 12:20 PM, Kieran Kunhya wrote:
> > On Tue, 19 Mar 2024 at 15:05, James Almer wrote:
> >
> >> On 3/19/2024 11:56 AM, Andreas Rheinhardt wrote:
> >>> James Almer:
> >>>> Signed-
On Tue, 19 Mar 2024 at 15:05, James Almer wrote:
> On 3/19/2024 11:56 AM, Andreas Rheinhardt wrote:
> > James Almer:
> >> Signed-off-by: James Almer
> >> ---
> >> configure| 4 +
> >> libavfilter/Makefile | 1 +
> >> libavfilter/allfilters.c | 1 +
> >> libavfilter
On Thu, 14 Mar 2024, 22:54 Michael Niedermayer,
wrote:
> On Wed, Feb 07, 2024 at 10:55:18PM +0000, Kieran Kunhya wrote:
> > On Wed, 7 Feb 2024 at 22:06, Paul B Mahol wrote:
> >
> > > On Wed, Feb 7, 2024 at 10:13 PM Kieran Kunhya wrote:
> > >
> > > >
On Wed, 13 Mar 2024 at 00:53, Andreas Rheinhardt <
andreas.rheinha...@outlook.com> wrote:
> It is accessed via AV_RN64() in ff_simple_idct_put_int32_10bit().
> Should fix the UBSan failures in the mpeg4-simple-studio-profile
> test here:
>
> https://fate.ffmpeg.org/report.cgi?time=20240312011016&s
>
> Dear LibAV core developer, thank you for this transcript.
>
If you feel like trolling, at least get your facts correct.
Kieran
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, vi
On Sun, 10 Mar 2024, 01:25 Michael Niedermayer,
wrote:
> Hi everyone
>
> Some members of the CC want to indefinitely ban Balling
> from trac. And as our doc/community.texi says:
> "Indefinite bans from the community must be confirmed by the General
> Assembly, in a majority vote."
>
> Thus some C
On Fri, 8 Mar 2024 at 16:50, Nicolas George wrote:
> Kieran Kunhya (12024-03-08):
> > New contributors are not interested in your biased history lessons. They
> > want to write code and have a modern, well run project, not a
> dysfunctional
> > mess.
>
> And we go b
On Fri, 8 Mar 2024 at 16:41, Nicolas George wrote:
> Kieran Kunhya (12024-03-08):
> > Several recent contributors were in nappies during that piece of ancient
> > history. Do you really need to bring it up incessantly and use it as your
> > prism on every issue you disagree
On Fri, 8 Mar 2024 at 15:46, Nicolas George wrote:
> Sean McGovern (12024-03-08):
> > It is really mean-spirited to make such comments about a project that is
> no
> > longer in operation. Can't we look forward instead of behind us?
>
> The project libav might be dead, but the people who made it
On Fri, 8 Mar 2024 at 15:04, Frank Plowman wrote:
> On 08/03/2024 14:04, James Almer wrote:
> > On 3/8/2024 11:02 AM, Kieran Kunhya wrote:
> >> On Fri, 8 Mar 2024 at 14:00, James Almer wrote:
> >>
> >>> On 3/3/2024 4:35 AM, Jean-Baptiste Kempf wrote:
&g
On Fri, 8 Mar 2024 at 14:00, James Almer wrote:
> On 3/3/2024 4:35 AM, Jean-Baptiste Kempf wrote:
> >
> > n Sat, 2 Mar 2024, at 23:55, Michael Niedermayer wrote:
> >> On Tue, Jan 23, 2024 at 08:22:41PM +0100, Michael Niedermayer wrote:
> >>> Hi all
> >>>
> >>> As it was a little difficult for me
On Thu, 7 Mar 2024, 20:16 Sergio Garcia Murillo, <
sergio.garcia.muri...@gmail.com> wrote:
> On Thu, Mar 7, 2024 at 7:02 PM Rémi Denis-Courmont
> wrote:
>
> > Le torstaina 7. maaliskuuta 2024, 19.30.46 EET Sergio Garcia Murillo a
> > écrit :
> > > > The point is we don't want to use the external
On Thu, 7 Mar 2024, 17:16 Sergio Garcia Murillo, <
sergio.garcia.muri...@gmail.com> wrote:
> El jue, 7 mar 2024, 16:30, Kieran Kunhya escribió:
>
> > On Thu, 7 Mar 2024 at 15:07, Sergio Garcia Murillo <
> > sergio.garcia.muri...@gmail.com> wrote:
> >
> >
On Thu, 7 Mar 2024 at 15:07, Sergio Garcia Murillo <
sergio.garcia.muri...@gmail.com> wrote:
>
> Could anyone give me any pointers on what is the best way of doing this?
>
You should use a well known crypto library to implement this in FFmpeg (e.g
libgcrypt, openssl etc).
Kieran
$subj
Old:
vp9_vert_8x8_8bpp_c: 8.1
vp9_vert_8x8_8bpp_mmx: 2.4
New:
vp9_vert_8x8_8bpp_c: 6.8
vp9_vert_8x8_8bpp_sse2: 2.3
0001-libavcodec-vp9dsp-Convert-vp9_vert_8x8_8bpp_mmx-to-s.patch
Description: Binary data
___
ffmpeg-devel mailing list
ffmpeg-deve
On Sat, 2 Mar 2024 at 21:18, Andreas Rheinhardt <
andreas.rheinha...@outlook.com> wrote:
> Kieran Kunhya:
> > $subj
> >
> > Old:
> > pred8x8_horizontal_8_c: 6.8
> > pred8x8_horizontal_8_mmxext: 8.6
> > pred8x8_horizontal_8_ssse3: 4.8
$subj
Old:
pred8x8_horizontal_8_c: 6.8
pred8x8_horizontal_8_mmxext: 8.6
pred8x8_horizontal_8_ssse3: 4.8
New:
pred8x8_horizontal_8_c: 9.2
pred8x8_horizontal_8_sse2: 12.2
pred8x8_horizontal_8_ssse3: 4.9
0001-libavcodec-h264pred-Remove-pred8x8_horizontal_8_mmxe.patch
Description: Binary data
_
The TC is doing this for the good of the project (I hope) and not to push
their own agenda and it's very clear in this case there is no personal
agenda.
Regards,
Kieran Kunhya
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ff
On Sat, 17 Feb 2024 at 13:16, Gyan Doshi wrote:
> > Whilst s302m multiple substreams I haven't seen, Dolby E streams
> internally
> > contain multiple programs, often 5.1 and a 2.0 downmix.
>
> That is downstream of the Dolby-E decoder and user will have to use a
> filter like channelsplit to bif
1 - 100 of 864 matches
Mail list logo
