From: Kieran Kunhya <kierank@obe.tv> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH v2] avformat: add Software Defined Radio support Date: Fri, 23 Jun 2023 19:36:53 +0800 Message-ID: <CAK+ULv7mwASCnfwpmGQCFgjDPAWtDANyV8WKaj5QByrh7_vBwg@mail.gmail.com> (raw) In-Reply-To: <20230623111728.GM3250409@pb2> On Fri, 23 Jun 2023, 19:17 Michael Niedermayer, <michael@niedermayer.cc> wrote: > On Fri, Jun 23, 2023 at 10:34:10AM +0800, Kieran Kunhya wrote: > > FFmpeg is not the place for SDR. SDR is as large and complex as the > > entirety of multimedia. > > > > What next, is FFmpeg going to implement TCP in userspace, Wifi, Ethernet, > > an entire 4G and 5G stack? > > https://en.wikipedia.org/wiki/Straw_man It's not a straw man, I'm asking why you want to add layers far below multimedia to ffmpeg. All of those examples are similar examples of physical layers. > What my patch is doing is adding support for AM demodulation, the AM > specific code is like 2 pages. The future plan for FM demodulation will > not add alot of code either. DAB/DVB should also not be anything big > (if that is implemented at all by anyone) > If the code grows beyond that it could be split out into a seperate > library outside FFmpeg. > Then just put it in a library outside of FFmpeg to begin with. DVB-T2 and S2 are very complex to implement well. AM and FM are toys in comparison. > The size of all of SDR really has as much bearing on FFmpeg as the size > of all of mathematics has on the use of mathematics in FFmpeg. > I have no idea what this means, mathematics is needed in multimedia, SDR is not. > > All without any separation of layers (the problem you currently have)? > > Lets see where the review process leads to. > It is possible iam missing some things, its possible others are missing > some factors. > Ultimately sdr is more similar than it is different from existing input > devices and demuxers. > The review process may identify possible solutions that benefit other > input devices too. It might identify shortcommings in FFmpeg that > could lead to improvments. > I dont really enjoy the review process ATM, no ;) but lets see where it > leads to. > No input device needs to do active mathematical processing on the data at a analogue layer. SDR isn't similar at all. Kieran _______________________________________________ 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-06-23 11:37 UTC|newest] Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-18 22:28 Michael Niedermayer 2023-06-22 13:43 ` Michael Niedermayer 2023-06-22 13:55 ` James Almer 2023-06-22 15:05 ` Michael Niedermayer 2023-06-22 15:10 ` James Almer 2023-06-22 16:26 ` Michael Niedermayer 2023-06-22 16:42 ` James Almer 2023-06-22 22:00 ` Michael Niedermayer 2023-06-23 2:34 ` Kieran Kunhya 2023-06-23 11:17 ` Michael Niedermayer 2023-06-23 11:36 ` Kieran Kunhya [this message] 2023-06-23 16:37 ` Rémi Denis-Courmont 2023-06-23 18:12 ` Michael Niedermayer 2023-06-23 18:17 ` Paul B Mahol 2023-06-23 18:56 ` Michael Niedermayer 2023-06-23 19:10 ` Paul B Mahol 2023-06-23 19:16 ` James Almer 2023-06-24 20:27 ` Rémi Denis-Courmont 2023-06-24 21:03 ` Tomas Härdin 2023-06-25 13:53 ` Michael Niedermayer 2023-06-25 14:25 ` Michael Niedermayer 2023-06-24 22:19 ` Nicolas George 2023-06-25 14:10 ` Michael Niedermayer 2023-06-27 19:09 ` Rémi Denis-Courmont 2023-06-28 22:15 ` Tomas Härdin 2023-06-29 7:14 ` Nicolas George 2023-06-29 9:46 ` Jean-Baptiste Kempf 2023-06-30 21:51 ` Tomas Härdin 2023-07-02 8:11 ` Michael Niedermayer 2023-07-02 9:34 ` Nicolas George 2023-07-02 9:54 ` Tomas Härdin 2023-07-02 9:56 ` Nicolas George 2023-06-23 20:10 ` Tomas Härdin 2023-06-23 21:18 ` Michael Niedermayer 2023-06-24 9:51 ` Tomas Härdin 2023-06-24 21:01 ` Michael Niedermayer 2023-06-24 22:01 ` Tomas Härdin 2023-06-25 9:54 ` Michael Niedermayer 2023-06-27 9:00 ` Tomas Härdin 2023-06-27 10:57 ` Nicolas George 2023-06-27 17:07 ` Tomas Härdin 2023-06-27 17:11 ` Nicolas George 2023-06-25 10:23 ` Kieran Kunhya
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=CAK+ULv7mwASCnfwpmGQCFgjDPAWtDANyV8WKaj5QByrh7_vBwg@mail.gmail.com \ --to=kierank@obe.tv \ --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