From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [RFC] Release 6.1
Date: Tue, 3 Oct 2023 21:22:58 +0200
Message-ID: <20231003192258.GR5133@pb2> (raw)
In-Reply-To: <169575207748.6638.4929384189591808216@lain.khirnov.net>
[-- Attachment #1.1: Type: text/plain, Size: 5328 bytes --]
On Tue, Sep 26, 2023 at 08:14:37PM +0200, Anton Khirnov wrote:
> Quoting Michael Niedermayer (2023-09-26 19:16:30)
> > On Tue, Sep 26, 2023 at 05:30:19PM +0200, Anton Khirnov wrote:
> > > Quoting Michael Niedermayer (2023-09-26 17:09:47)
> > > > On Tue, Sep 26, 2023 at 11:13:40AM +0200, Anton Khirnov wrote:
> > > > > Quoting Michael Niedermayer (2023-09-22 11:27:54)
> > > > > > The idea was really just, that i said ill include SDR and i want to
> > > > > > keep this word
> > > > >
> > > > > Well, you should not have spoken for the entire project without
> > > > > consulting the rest of the community first. Nobody here is entitled to
> > > >
> > > > This statement is a little misleading, i think
> > > >
> > > > 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.
> > >
> > > This is disingenuous sophistry, and honestly I find it insulting that
> > > you expect people to swallow it.
> > >
> > > You made the tweet in question long after it was clear that the feature
> > > is controversial. Then you tried to use it as an argument in favor of
> > > pushing SDR to master. In other words, you used the fact that you have
> > > Twitter posting rights to promote your opinion over that of other
> > > developers. If that is not abuse of power then I don't know what is.
> >
> > ok
> > I wrote a SDR input device for free, wanted to give it to the users
> > as i believed it was a cool and usefull feature
> >
> > i tried to argue for it, i tried to promote it.
> > And as the person doing all releases of FFmpeg since a very long time
> > i thought yeah we will be able to resolve the disagreements and get it
> > in 6.1 with everyone geing happy.
> > I was wrong, i announced this before i actually got people to agree yes
> > I still belive if people where not so "excited" on this whole and if it
> > was just a technical question we could get SDR in 6.1 with everyone
> > agreeing.
> > But now heres a man to be burned at the stake, and thats more important.
>
> You keep framing this as some kind of a personal campaign against you.
> It is not. From my perspective, the objections to SDR have been largely
> technical, and most of the "heat" comes from your refusal to accept that
> many active developers are against it.
Technical arguments ?
Yes, several people had technical arguments, I remember Tomas and Remi and some
others. But at least subjectively i felt that the bulk of people where alot more
emotional than technical
But let me list a few observations, from memory
First objection was because processing is done in an external library.
Then it was found out that was wrong and actually processing is done in the new code
so the objection flipped and people demanded it to be moved into an external library.
If you object to pink and want blue and when you find out its actually blue you have
to be happy and become a supporter but what happened was the opposit, the objection
was simply adjusted to object to whatever was the case and demand whatever was not.
Ok so thats at least one developers "Technical objection" down here, maybe more
i dont know if anyone else expressed that same initial objection. but lets move on
In all cases we prefer not to have external dependancies, this is the Technical position of FFmpeg
no, there is no technical argument in this.
Also personal preferrances of people is not a technical argument. Noone explained why a
avdevice module with more external depandancies would be ok but a avdevice module with
fewer external depandancies was not. <-- This last sentance is a technical argument
I could go as far as call this a proof by contradiction.
If people are happy with a avdevice module and FFmpeg prefers fewer external dependancies
then my suggestion of first starting with a plain simple self contained avdevice/avformat
module, would have to be fine too.
We can always move this to an external library once there is a technical reason for that
like for example some other software wants to use it
About the attack/rallying/compaign stuff. Ill keep it very brief as its not useful i think.
Also this is my own personal and subjective view. In fact the whole mail is
There was alot of (negative) emotion from 1-2 people about SDR. This emotion was what spread
slash rallied other developers. That came before any technical arguments.
Now people have picked their flag and march to war.
Everyone will deny it, same as every patriot will fight to the death for the colors of
the flag of the country and religion they where born into.
My claim, sorry to be stubborn, is that had this started a slight bit different there
would be little opposition to SDR. Iam not denying that now there are several people
against it.
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Rewriting code that is poorly written but fully understood is good.
Rewriting code that one doesnt understand is a sign that one is less smart
than the original author, trying to rewrite it will not make it better.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 251 bytes --]
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2023-10-03 19:23 UTC|newest]
Thread overview: 97+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-06 16:04 Lynne
2023-07-06 16:19 ` Jean-Baptiste Kempf
[not found] ` <4e164164-f730-4b5e-9edc-1a37b10684e2@betaapp.fastmail.com-NZg-97N----9>
2023-07-07 6:40 ` Lynne
2023-07-07 6:53 ` Ingo Oppermann
2023-07-07 7:36 ` Steven Liu
2023-09-26 13:37 ` Leo Izen
2023-07-07 15:06 ` Michael Niedermayer
2023-07-07 15:33 ` Lynne
2023-07-07 22:51 ` Michael Niedermayer
2023-07-09 10:14 ` Anton Khirnov
2023-09-22 9:27 ` Michael Niedermayer
2023-09-22 9:32 ` Paul B Mahol
2023-09-22 14:49 ` Michael Niedermayer
2023-09-22 15:27 ` Paul B Mahol
2023-09-26 8:47 ` Jean-Baptiste Kempf
2023-09-22 10:04 ` Nicolas George
2023-09-22 11:42 ` Paul B Mahol
2023-09-26 9:13 ` Anton Khirnov
2023-09-26 15:09 ` Michael Niedermayer
2023-09-26 15:14 ` Kieran Kunhya via ffmpeg-devel
2023-09-26 15:30 ` Anton Khirnov
2023-09-26 16:27 ` Derek Buitenhuis
2023-09-26 17:24 ` Michael Niedermayer
2023-09-26 17:16 ` Michael Niedermayer
2023-09-26 17:25 ` James Almer
2023-09-26 18:03 ` Nicolas George
2023-09-26 18:14 ` Anton Khirnov
2023-09-26 18:24 ` Nicolas George
2023-09-26 18:27 ` Vittorio Giovara
2023-09-26 18:28 ` Nicolas George
[not found] ` <F3D5B4BB-AE60-401F-800E-6246B9F359A4@cosmin.at>
2023-09-26 22:50 ` [FFmpeg-devel] SDR choices Cosmin Stejerean via ffmpeg-devel
2023-10-03 19:22 ` Michael Niedermayer [this message]
2023-10-04 15:19 ` [FFmpeg-devel] [RFC] Release 6.1 Anton Khirnov
2023-10-04 16:54 ` Lynne
2023-10-04 17:53 ` Michael Niedermayer
2023-09-26 21:20 ` Ronald S. Bultje
2023-09-27 13:53 ` Tomas Härdin
2023-09-27 20:18 ` Michael Niedermayer
2023-09-27 20:27 ` Nicolas George
2023-09-28 8:48 ` Ronald S. Bultje
2023-09-28 14:45 ` Rémi Denis-Courmont
2023-09-28 15:33 ` Nicolas George
2023-09-28 15:58 ` Rémi Denis-Courmont
2023-09-28 16:13 ` Nicolas George
2023-09-28 16:34 ` Rémi Denis-Courmont
2023-09-28 16:42 ` Nicolas George
2023-09-28 14:32 ` Rémi Denis-Courmont
2023-09-28 15:28 ` Nicolas George
2023-09-28 16:22 ` Rémi Denis-Courmont
2023-09-28 16:32 ` Nicolas George
2023-09-28 16:35 ` Paul B Mahol
2023-09-28 16:38 ` Rémi Denis-Courmont
2023-09-28 16:41 ` Nicolas George
2023-09-28 16:42 ` Rémi Denis-Courmont
2023-09-28 16:43 ` Nicolas George
2023-09-28 17:27 ` Rémi Denis-Courmont
2023-07-08 1:46 ` Neal Gompa
2023-07-09 10:13 ` Anton Khirnov
2023-10-09 3:37 ` Lynne
2023-10-09 17:41 ` Michael Niedermayer
2023-10-10 15:19 ` Neal Gompa
2023-10-28 16:49 ` Michael Niedermayer
2023-10-28 16:56 ` James Almer
2023-10-28 19:23 ` Lynne
2023-10-29 4:51 ` Michael Niedermayer
2023-10-29 5:57 ` Lynne
2023-11-07 7:36 ` Lynne
2023-11-07 16:47 ` Tristan Matthews
2023-11-08 1:26 ` Steven Liu
2023-11-08 1:29 ` Steven Liu
[not found] ` <NichQkq--3-9@lynne.ee-NichTw8----9>
2023-11-09 8:20 ` Lynne
2023-11-09 9:46 ` epirat07
2023-11-09 9:48 ` Gyan Doshi
2023-11-10 1:47 ` Michael Niedermayer
2023-10-29 9:30 ` Nicolas George
2023-10-29 13:51 ` Jean-Baptiste Kempf
2023-10-29 14:17 ` Nicolas George
2023-10-29 16:27 ` Jean-Baptiste Kempf
2023-10-29 16:40 ` Nicolas George
2023-10-29 16:43 ` Jean-Baptiste Kempf
2023-10-29 16:45 ` Nicolas George
2023-10-29 15:10 ` Thilo Borgmann via ffmpeg-devel
2023-10-29 16:25 ` Jean-Baptiste Kempf
2023-10-29 17:20 ` Thilo Borgmann via ffmpeg-devel
2023-10-29 17:56 ` Jean-Baptiste Kempf
2023-10-29 18:12 ` Nicolas George
2023-10-29 18:22 ` Jean-Baptiste Kempf
2023-10-29 18:31 ` Nicolas George
2023-10-29 19:11 ` Jean-Baptiste Kempf
2023-10-29 19:19 ` Nicolas George
2023-10-29 18:47 ` Thilo Borgmann via ffmpeg-devel
2023-10-29 18:46 ` Thilo Borgmann via ffmpeg-devel
2023-10-29 19:27 ` Jean-Baptiste Kempf
2023-11-01 17:53 ` Thilo Borgmann via ffmpeg-devel
2023-10-29 16:42 ` Jean-Baptiste Kempf
2023-10-29 16:49 ` James Almer
2023-10-29 17:01 ` Jean-Baptiste Kempf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231003192258.GR5133@pb2 \
--to=michael@niedermayer.cc \
--cc=ffmpeg-devel@ffmpeg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git