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
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 Thu, Nov 9, 2023 at 5:06 PM Anton Khirnov wrote:
>
> Quoting Michael Niedermayer (2023-11-09 17:21:12)
> > On Thu, Nov 09, 2023 at 01:21:13PM +0100, Anton Khirnov wrote:
> > > As far as I can tell, the voter list in the last vote should be the same
> > > as the GA from 2020, except for the extr
> The list does not match your list, for example Gautam is on your list
> but not on joshs
>
> So my question is still standing, can you explain how your list was created?
> or where its from?
How was the list of your root admins created? Who decided they would be root?
Kieran
___
On Sat, Nov 11, 2023 at 11:45 PM Michael Niedermayer
wrote:
>
> On Fri, Nov 10, 2023 at 12:39:45PM +, Kieran Kunhya via ffmpeg-devel
> wrote:
> > > The list does not match your list, for example Gautam is on your list
> > > but not on joshs
> > >
> &g
On Sun, 19 Nov 2023, 14:05 Derek Buitenhuis,
wrote:
> Hi,
>
> Followup question...
>
> On 11/1/2023 9:25 PM, Derek Buitenhuis wrote:
> > This is certainly interesting considering we just had a giant thread
> about not using
> > or using SPI, with multiple people accused of having corporate intere
On Sun, Nov 19, 2023 at 9:46 PM Michael Niedermayer
wrote:
>
> On Sun, Nov 19, 2023 at 02:26:22PM +, Kieran Kunhya via ffmpeg-devel
> wrote:
> [...]
> > I would not find it acceptable for SPI to pay these costs. I do not feel
> > donors would want their money spent on
Hi Raphael,
I was the author of the tweet and I gave a short talk about this topic at
Demuxed at a video conference last year:
https://m.youtube.com/watch?v=OIyOEuQQsCQ&t=930s
That said this is a community project and it would be best to continue the
discussion on this mailing list unless agreed
Hi Raphael,
Answers in my own personal capacity, not the views of my employer, nor the
views of anyone else in FFmpeg.
On Wed, Apr 3, 2024 at 8:26 PM Satter, Raphael (Reuters) <
raphael.sat...@thomsonreuters.com> wrote:
> Dear Kieran & co.,
>
>
>
> Thank you I’ve had a chance to see the talk. It
Hello,
X (Twitter) has changed the way accounts can post under @ffmpeg.
Please could the person with the main login to @ffmpeg delegate myself
("kierank_") and Derek ("Daemon404") and delegate @ffmpeg access to
both of us.
We have tested this with the @videolan account and it works without a
blue
On Thu, Sep 21, 2023 at 5:21 PM Michael Niedermayer
wrote:
> OTOH If a majority of people are against the SDR code at the time of
> branching 6.1. Then i will make a separate release identical to 6.1 with
> the SDR code and of course also provide security support
How on earth is it acceptable tha
> Iam part of the community, i would think and for 99% of the tweets made
> on the official twitter account i have never been asked or even had a
> chance to comment before they where made. So what you suggest here is
> "the correct way", has never been applied.
Announcing feature are going to be
On Tue, Oct 3, 2023 at 7:50 PM Nicolas George wrote:
> More precisely, I now strongly believe that democracy is a terrible way
> to run a project like FFmpeg.
Why are you part of a community project if you don't believe the
community is capable of running a project?
Why not start your own project
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 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 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 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 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 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, 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, 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 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 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:
> >
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 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
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 Sun, Nov 24, 2024 at 12:23 PM Michael Niedermayer
wrote:
>
> Hi Remi
>
> On Sat, Nov 23, 2024 at 05:16:10PM +0100, Rémi Denis-Courmont wrote:
> >
> >
> > Le 23 novembre 2024 14:12:19 GMT+01:00, Michael Niedermayer
> > a écrit :
> > >Signed-off-by: Michael Niedermayer
> > >---
> > > doc/commu
On Tue, 26 Nov 2024, 23:32 Michael Niedermayer,
wrote:
> Signed-off-by: Michael Niedermayer
> ---
> doc/infra.txt | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/doc/infra.txt b/doc/infra.txt
> index 08dcf04c307..71ad7a7db02 100644
> --- a/doc/infra.txt
> +++ b/do
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
Hi Michael,
Are you able to document the differences between source.ffmpeg.org and
git.ffmpeg.org?
Why does one resolve to telepoint and one to VideoLAN? What is the
purpose of having two CNAMEs?
https://git.ffmpeg.org currently goes to a 403 Forbidden "You don't
have permission to access this re
> - 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
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 be possible to implement
> >> a full pcm
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 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
>
> +In recent years, a significant number of developers contributing to the
> project are employed by companies,
> +unlike in the past. These employees are often compensated for specific
> tasks, and the voting rights,
> +much like the copyrights, can typically be controlled by their employers.
>
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
On Mon, Dec 30, 2024 at 4:58 PM Michael Niedermayer
wrote:
But in an attempt to remove the grand prize and motive behind this.
> I will never give any power related to FFmpeg to people who continue with
> attacks/harrassment/accusations.
> (more clearly, any future democratication will exclude th
On Mon, Dec 30, 2024 at 4:58 PM Michael Niedermayer
wrote:
> But in an attempt to remove the grand prize and motive behind this.
> I will never give any power related to FFmpeg to people who continue with
> attacks/harrassment/accusations.
> (more clearly, any future democratication will exclude t
On Sun, Nov 10, 2024 at 11:53 PM Michael Niedermayer
wrote:
>
> Hi
>
> I have been given recordings of VDD by the Reconnaissance General Bureau.
> (didnt listen to all yet)
>
> IIUC there was a talk where it was suggested (by kieran?) to have some
> assembly langauge course on FFmpeg github. IMO t
>
>
> 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
On Wed, Dec 25, 2024 at 4:27 AM Michael Niedermayer
wrote:
>
> Signed-off-by: Michael Niedermayer
> ---
> doc/community.texi | 6 ++
> 1 file changed, 6 insertions(+)
>
> diff --git a/doc/community.texi b/doc/community.texi
> index 97a49f15ede..0bc8893f0e8 100644
> --- a/doc/community.texi
>
On Wed, Dec 25, 2024 at 1:31 PM Michael Niedermayer
wrote:
>
> Hi Community, Community Commitee, Moderators
>
Your removal of this message as of 1504 GMT 26/12/2024 is completely
unacceptable with one days notice posted on a public holiday in most
countries.
Furthermore, you make regular allegati
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
>
> You can simply verify that vittorio is himself as you meet him next time
> and drink
> beer with him (which you said you did previously).
> Its just a simple "yeah i met him after this and he is still in control
> of his accounts&keys", theres no kyc here, just a statement from you saying
> you
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
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
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
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
> 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
Hello,
My messages are being blocked on the mailing list. How is this fair that
one person can unilaterally decide this?
Here is my message:
Hi Michael,
If the CC has voted to ban someone, why has it not happened?
You can't complain it the CC fails to act when it has voted for something
to hap
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 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
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, 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 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, 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, 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, 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, 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 Thu, 19 Dec 2024, 02:22 Michael Niedermayer,
wrote:
>
> Kieran reports this to the CC
> and jb and ronald vote for a third ban of Nicolas,
> ronald states that he would not have voted for a ban if Nicolas apologized.
>
Hi Michael,
If the CC has voted to ban someone, why has it not happened?
On Fri, Dec 20, 2024 at 5:20 AM Lingyi Kong wrote:
>
> fix for https://trac.ffmpeg.org/ticket/11360
>
> Signed-off-by: Lingyi Kong
> ---
> libavcodec/h264_mb.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/libavcodec/h264_mb.c b/libavcodec/h264_mb.c
> index 4e94136313.
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, 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 +0000, Kieran Kunhya via ffmpeg-devel
> > > wro
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
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 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 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
On Wed, Jan 22, 2025 at 3:33 PM Michael Niedermayer
wrote:
>
> On Mon, Jan 20, 2025 at 06:46:46AM +, Kieran Kunhya via ffmpeg-devel
> wrote:
> > >
> > > > The data arrives on multiple sockets, leading to all sorts
> > > > of opportunities
>
> Ah, I got you now. This would mean that one part of patches will never go
> through the ML and another part will never be seen on "WEB". I hadn't even
> considered that as a possible/acceptable way, but I wouldn't mind.
>
How is this not confusing as hell for new contributors?
Running two sys
On Wed, Jan 22, 2025 at 4:37 PM Michael Niedermayer
wrote:
>
> Hi
>
> On Mon, Jan 20, 2025 at 03:00:17PM +0000, Kieran Kunhya via ffmpeg-devel
> wrote:
> [...]
>
> > Error recovery protocols are complicated -
>
> everything is complicated
>
>
> > this
On Wed, Jan 22, 2025 at 4:53 PM Romain Beauxis wrote:
>
> Le mer. 22 janv. 2025 à 10:29, Kieran Kunhya via ffmpeg-devel
> a écrit :
> >
> > On Wed, Jan 22, 2025 at 3:33 PM Michael Niedermayer
> > wrote:
> > >
> > > On Mon, Jan 20, 2025 at 06:
On Tue, Jan 21, 2025 at 6:59 PM Vittorio Giovara
wrote:
>
> Greetings FFmpeg community
>
> There will be a community meeting during the conference, dates and times
> TBA!
>
> I believe there will be means to connect remotely, and everybody is invited
> to join, especially those that believe that o
On Tue, Jan 21, 2025 at 5:42 PM Michael Niedermayer
wrote:
>
> Hi
>
> As people likely know i belive it is not but i got a 2nd opinion:
Hi Michael,
Can you ask ChatGPT the following:
Is it ok for one person to be in control of a major open source
project when they promised to step down?
Can you
On Tue, 21 Jan 2025, 18:57 James Almer, wrote:
> On 1/21/2025 3:13 PM, Kieran Kunhya via ffmpeg-devel wrote:
> > On Tue, Jan 21, 2025 at 5:42 PM Michael Niedermayer
> > wrote:
> >>
> >> Hi
> >>
> >> As people likely know i belive it
On Wed, Jan 22, 2025 at 4:37 PM Michael Niedermayer
wrote:
>
> Hi
>
> On Mon, Jan 20, 2025 at 03:00:17PM +0000, Kieran Kunhya via ffmpeg-devel
> wrote:
> [...]
>
> > Error recovery protocols are complicated -
>
> everything is complicated
>
>
> > this
> Can you please stop this "my way or no way"
The irony is not lost on me of this sentence (from the person banning
people, censoring people, creating paranoid theories about the GA).
Kieran
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://
On Wed, 22 Jan 2025, 20:36 Michael Niedermayer,
wrote:
> This blocks disallowed extensions from probing
> It also requires all available segments to have matching extensions to the
> format
> mpegts is treated independent of the extension
>
Potentially this is a stupid question but what stops an
On Thu, Jan 16, 2025 at 8:15 PM 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 coul
> The FEC decoder works on the demuxer/transport layer and is
> independent from the content layer.
>
> The FEC decoder parameters can be set by the user according to their
> content settings to determine the delay incurred by buffering and
> packet loss for a CBR content.
A buffer of N packets do
On Thu, 23 Jan 2025, 00:11 Michael Niedermayer,
wrote:
> Hi Kieran
>
> On Wed, Jan 22, 2025 at 10:47:52PM +0000, Kieran Kunhya via ffmpeg-devel
> wrote:
> > On Wed, 22 Jan 2025, 20:36 Michael Niedermayer,
> > wrote:
> >
> > > This blocks disallowed extensi
On Fri, Jan 24, 2025 at 3:59 AM Zhao Zhili
wrote:
>
>
>
> > On Jan 24, 2025, at 02:02, Timo Rothenpieler wrote:
> >
> > On 23.01.2025 15:17, Zhao Zhili wrote:
> >> From: Zhao Zhili
> >> Otherwise all frames can be dropped after seek without the
> >> output_corrupt/showall flags.
> >> ---
> >> l
>
> > The data arrives on multiple sockets, leading to all sorts
> > of opportunities for timing behavior and reordering issues.
>
> how does this matter?
>
There are routers that put traffic on a different port down a different ISP
so you have to compensate for latency delays between the two link
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.beau...@gmail.com> wrote:
> > > >
> > > > Hi,
> > > >
On Tue, Dec 24, 2024 at 9:34 AM Lingyi Kong wrote:
>
> add fate test case
>
> Signed-off-by: Lingyi Kong
For whatever reason PATCHv4 is in neither of my email boxes, one of
which is subscribed to ffmpeg-devel, the other of which is not
subscribed but I still receive the emails. It's a great syst
The mere possibility that the CC could "intervene" about anything has a very
> chilling effect. Few people will touch finances in such an environment.
> Bascially this will make use of money in the future more difficult.
> In the past we just all tried to do the right thing for the project
> but if
On Mon, Jan 20, 2025 at 2:51 PM Nicolas George wrote:
>
> Kieran Kunhya via ffmpeg-devel (12025-01-17):
> > I am the author of the only known functional OSS implementation of FEC.
>
> Seen from here, your rejection of this proposal looks a teeny tiny
> little bit like trying
> If the CC takes a clear action, this whole drama simply stops. Otherwise
> i suspect it will lead to a fork eventually. In the fork case they will leave
> with
> several others. I think thats a much bigger loss
I agree, Anton is gone because of your inflammatory behaviour
(banning, censorship e
On Sun, Jan 26, 2025 at 9:24 PM Michael Niedermayer
wrote:
>
> Hi Kieran
>
> On Sun, Jan 26, 2025 at 07:39:38PM +0000, Kieran Kunhya via ffmpeg-devel
> wrote:
> > > I remember such a IRC session before the libav fork.
> > > It is very similar to this here
> &g
>
> Or is there any reason to not call it what it is (Dish)? There are Sega or
> Nintendo audio decoders and other examples and a cryptic description like
> "DVB 0502" renders it useless for almost everybody.
>
Agreed.
Kieran
>
___
ffmpeg-devel mailing
On Sun, Jan 26, 2025 at 8:40 PM Rémi Denis-Courmont wrote:
>
> With my CC hat on,
>
> Le sunnuntaina 26. tammikuuta 2025, 21.39.38 UTC+2 Kieran Kunhya via ffmpeg-
> devel a écrit :
> > With Anton leaving the project because of you, Paul forking and James
> > lea
On Sun, Jan 26, 2025 at 8:51 PM Kieran Kunhya wrote:
>
> On Sun, Jan 26, 2025 at 8:40 PM Rémi Denis-Courmont wrote:
> >
> > With my CC hat on,
> >
> > Le sunnuntaina 26. tammikuuta 2025, 21.39.38 UTC+2 Kieran Kunhya via ffmpeg-
> > devel a écrit :
> > &
>
> 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
On Sun, 26 Jan 2025, 00:31 Soft Works,
wrote:
> > -Original Message-
> > From: ffmpeg-devel On Behalf Of
> > Marth64
> > Sent: Sunday, January 26, 2025 1:14 AM
> > To: FFmpeg development discussions and patches > de...@ffmpeg.org>
> > Subject: Re: [FFmpeg-devel] [PATCH] libavcodec/mpeg1
> I remember such a IRC session before the libav fork.
> It is very similar to this here
> 4+ people, who simply accuse me of everything (on IRC though)
> this serves no purpose. There is no common ground here
Hi Michael,
With Anton leaving the project because of you, Paul forking and James
leavi
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
> >
On Sun, 19 Jan 2025, 22:22 Michael Niedermayer,
wrote:
> The part i do not agree with and iam not convinced about is that this
> cannot be done in a clean and fully working and heuristics free
> way in the real world.
>
Protocols are not the same as codecs. Just because you have a hammer,
everyt
On Sat, 25 Jan 2025, 21:49 Rémi Denis-Courmont, wrote:
> Le lauantaina 25. tammikuuta 2025, 22.26.44 UTC+2 Michael Niedermayer a
> écrit
> :
> > I had posted one joke on my personal twitter that i deleted a few hours
> > later as people seem to have misunderstood it.
>
> It is completely irreleva
On Sat, 25 Jan 2025, 22:53 Marth64, wrote:
> Hello,
>
> I am to blame here for suggesting DVB_0502 as the name.
> I realize it was not the best choice and apologize for wasting your
> cycles on this.
>
> Looping in Keiran as we had discussed this over IRC briefly a few weeks
> back.
> As I don't
1 - 100 of 237 matches
Mail list logo
