From: Paul B Mahol <onemda@gmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] What is FFmpeg and what should it be Date: Tue, 8 Aug 2023 17:37:22 +0200 Message-ID: <CAPYw7P7-+KhCyvCJDPqY1baoqEo8zDL6UwNuKDtQH5MXSZfCGA@mail.gmail.com> (raw) In-Reply-To: <20230808152249.GY7802@pb2> On Tue, Aug 8, 2023 at 5:23 PM Michael Niedermayer <michael@niedermayer.cc> wrote: > Hi > > On Mon, Aug 07, 2023 at 06:39:10PM +0300, Rémi Denis-Courmont wrote: > > Le sunnuntaina 6. elokuuta 2023, 22.53.23 EEST Michael Niedermayer a > écrit : > > > > > > Did you ask people to do that? > > > > > > > > > > yes, multiple times. > > > > > Also normally patch objections come with a path forward, that was > not > > > > > the case here. > > > > > > > > Not necessarily, sometimes preventing a bad idea from happening is a > > > > positive thing in itself, and no path forward is needed. > > > > > > That is missing that people suggest a path forward but > > > with too few details to easily walk that path. > > > > Uh, I hate to state the patently obvious, but if "no path forward is > needed", > > then there should logically be _no_ "details to walk [a] path". > Conversely, if > > avradio does not belong in FFmpeg, as Kieran, Tomas and others have been > > arguing, then there is no path forward to be given on FFmpeg-devel. > > > > > > And besides I don't think it's even fair to state that "too few details" > were > > given. People did suggest making this a new separate project properly > isolated > > from FFmpeg internals, and/or joining efforts with existing OSS SDR > projects > > rather than FFmpeg. Some specific projects have even been cited. > > > > As far as FFmpeg(-devel) is concerned, I can't think how it could/should > > reasonably get any more specific than that. > > The saying goes, one cannot win an Argument on the Internet. > So, iam not trying to, but > > IIRC, a while ago you said iam obliged to work on FFmpeg. Thats > simply not the case. > > Its not an obligation but rather my choice that i like to work on > something the end user will enjoy. And the end user, in fact > more than 500 end users liked SDR in FFmpeg. > My original plan was to spend 1-2 weeks working on SDR, now > probably about 2 months passed with me spending a bit working on > SDR here and there. > > I also am not obliged to do what other developers want me to do. But i have > been in this community for a very long time and have my highest respect > from the Developers in this community, even if at times we disagreed > they are all great people, and some are my friends. > And working toward a consensus everyone is happy with is > something i want whenever there is a disagreement. > On IRC what people said, and what JB said here, is that people are ok > with a SDR module in FFmpeg under some conditions. > It is these conditions that i do not fully understand, and that i > tried to understand better. > > You and vittorio here seem to suggest that instead there are no > possible conditions and no path forward. Thus a fork would have to happen. > Now iam quite confident, that, thats not what people ask for. > We had a fork and i dont think we want to have a new one. > > Again, i want a consensus everyone is happy with so I keep asking > what people suggest exactly. > For start, and good will, I'm willing to accept a signal of good will from you to remove sdr files from FATE. There is no point in discussing anything further with you until that is done. > Thanks > > [...] > -- > Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB > > He who knows, does not speak. He who speaks, does not know. -- Lao Tsu > _______________________________________________ > 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". > _______________________________________________ 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-08-08 15:30 UTC|newest] Thread overview: 84+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-07-22 19:29 [FFmpeg-devel] [PATCH 1/6] configure: libavradio support Michael Niedermayer 2023-07-22 19:29 ` [FFmpeg-devel] [PATCH 2/6] avutil/log: Add AV_CLASS_CATEGORY_RADIO_INPUT Michael Niedermayer 2023-07-22 20:30 ` Paul B Mahol 2023-07-22 19:29 ` [FFmpeg-devel] [PATCH 3/6] avformat: add support for demuxers/inputs from avradio Michael Niedermayer 2023-07-22 20:35 ` Paul B Mahol 2023-07-22 19:29 ` [FFmpeg-devel] [PATCH 4/6] avdevice/utils: add test for AV_CLASS_CATEGORY_RADIO_INPUT Michael Niedermayer 2023-07-22 19:29 ` [FFmpeg-devel] [PATCH 5/6] fftools: avradio support Michael Niedermayer 2023-07-22 21:39 ` Lynne 2023-07-23 15:23 ` Michael Niedermayer 2023-07-23 18:49 ` Tomas Härdin 2023-07-23 19:01 ` James Almer 2023-07-23 22:56 ` Michael Niedermayer 2023-07-24 8:19 ` Nicolas George 2023-07-24 15:57 ` Michael Niedermayer 2023-07-24 22:30 ` Tomas Härdin 2023-07-25 14:17 ` Tomas Härdin 2023-07-24 20:19 ` Tomas Härdin 2023-07-25 9:37 ` Nicolas George 2023-07-26 10:37 ` Michael Niedermayer 2023-07-27 13:05 ` Tomas Härdin 2023-07-27 18:36 ` Michael Niedermayer 2023-07-27 18:48 ` Nicolas George [not found] ` <CC2992B9-B047-4724-8DE5-01C02CBE31FD@cosmin.at> 2023-08-01 19:51 ` Cosmin Stejerean 2023-08-01 20:06 ` Paul B Mahol 2023-08-02 12:46 ` Michael Niedermayer 2023-08-02 13:00 ` Paul B Mahol 2023-08-02 13:01 ` Michael Niedermayer 2023-07-24 8:13 ` Nicolas George 2023-07-24 20:22 ` Tomas Härdin 2023-07-25 9:33 ` Nicolas George 2023-07-25 9:51 ` Kieran Kunhya 2023-07-25 9:56 ` Nicolas George 2023-07-25 10:16 ` Kieran Kunhya 2023-07-25 13:55 ` Nicolas George 2023-07-25 14:37 ` Kieran Kunhya 2023-07-27 17:56 ` Nicolas George 2023-07-28 11:07 ` Kieran Kunhya 2023-07-30 13:04 ` [FFmpeg-devel] What is FFmpeg and what should it be Nicolas George 2023-07-30 17:07 ` Andrey Turkin 2023-07-30 18:29 ` Kieran Kunhya 2023-07-30 18:54 ` Nicolas George 2023-08-01 7:48 ` Rémi Denis-Courmont 2023-07-31 13:56 ` Tomas Härdin 2023-08-03 13:25 ` Nicolas George 2023-08-03 20:50 ` Tomas Härdin 2023-08-02 1:44 ` Vittorio Giovara 2023-08-02 12:55 ` Michael Niedermayer 2023-08-02 12:59 ` Jean-Baptiste Kempf 2023-08-02 14:12 ` Brad Isbell 2023-08-02 14:19 ` Nicolas George 2023-08-02 14:26 ` Michael Niedermayer 2023-08-02 14:30 ` Nicolas George [not found] ` <A3B35B92-8333-4637-B4AA-FA9D9750E784@cosmin.at> 2023-08-02 15:46 ` Cosmin Stejerean 2023-08-03 15:40 ` Michael Niedermayer 2023-08-02 14:20 ` Michael Niedermayer 2023-08-02 14:44 ` Jean-Baptiste Kempf 2023-08-03 17:45 ` Michael Niedermayer 2023-08-03 18:24 ` Kieran Kunhya 2023-08-03 19:25 ` Michael Niedermayer 2023-08-03 20:04 ` Kieran Kunhya 2023-08-04 17:09 ` Michael Niedermayer 2023-08-04 17:35 ` Nicolas George 2023-08-04 23:17 ` Kieran Kunhya 2023-08-05 18:55 ` Michael Niedermayer 2023-08-05 19:17 ` Paul B Mahol 2023-08-05 23:32 ` Vittorio Giovara 2023-08-06 8:28 ` Tomas Härdin 2023-08-06 19:53 ` Michael Niedermayer 2023-08-07 15:39 ` Rémi Denis-Courmont 2023-08-08 15:22 ` Michael Niedermayer 2023-08-08 15:37 ` Paul B Mahol [this message] 2023-08-08 18:53 ` Rémi Denis-Courmont 2023-08-09 15:59 ` Michael Niedermayer 2023-08-09 16:24 ` Paul B Mahol 2023-08-10 12:39 ` Nicolas George 2023-08-10 14:58 ` Vittorio Giovara 2023-08-12 17:12 ` Michael Niedermayer 2023-08-10 15:01 ` James Almer 2023-08-10 15:43 ` Jean-Baptiste Kempf 2023-08-10 18:39 ` Tomas Härdin 2023-08-03 11:38 ` Tomas Härdin 2023-08-03 13:29 ` Nicolas George 2023-07-25 12:02 ` [FFmpeg-devel] [PATCH 5/6] fftools: avradio support Tomas Härdin 2023-07-22 19:29 ` [FFmpeg-devel] [PATCH 6/6] tools/uncoded_frame: " Michael Niedermayer
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=CAPYw7P7-+KhCyvCJDPqY1baoqEo8zDL6UwNuKDtQH5MXSZfCGA@mail.gmail.com \ --to=onemda@gmail.com \ --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