Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Cosmin Stejerean via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: "FFmpeg development discussions and patches" <ffmpeg-devel@ffmpeg.org>
Cc: "Cosmin Stejerean" <cosmin@cosmin.at>
Subject: [FFmpeg-devel] SDR choices
Date: Tue, 26 Sep 2023 22:50:12 +0000
Message-ID: <0101018ad3af8f2d-b6b5fd6a-17a8-4d0e-bc9f-f31f0ca58a00-000000@us-west-2.amazonses.com> (raw)
In-Reply-To: <169575207748.6638.4929384189591808216@lain.khirnov.net>


> On Sep 26, 2023, at 11:14 AM, Anton Khirnov <anton@khirnov.net> wrote:
> 
> From my perspective, the objections to SDR have been largely
> technical,

From my perspective the objections against the current SDR implementation could be grouped into roughly 3 categories:

A) support for taking input from an SDR device doesn't belong in ffmpeg at all in any form, it's way too big and there are other projects out there for SDR there that one ought to use instead, and trying to do it in ffmpeg in any form would bloat the codebase and make a mess no matter which option is chosen

B) support for SDR is fine to have in ffmpeg, but it should be done via an external library that does not live in the ffmpeg source tree, and ffmpeg could be optionally compiled with a --enable-libsdr or some such

C) support for SDR is fine to have as long as it's in a separate module like a libavradio with a clean API rather than trying to beat it into libavdevice, the current implementation is too invasive

All 3 are united in objecting to the current implementation, which I'd summarize as SDR using libavdevice (let's call it option D). This makes it seem like there's a united front against SDR, but I think there's significant disagreement even among the people objecting to the current implementation as to which one of these 3 ought to be the right outcome for SDR. The discussion tends to go in circles. Discussions about C-vs-D tend to run into objections from B, trying to discuss the relative merits of B-vs-C runs into objections from A and so on.

This might be a good use of the TC (after a new GA and new TC is formed to avoid arguments about the validity of the decision). The TC could then settle on the direction for SDR in the project:

A. no SDR in ffmpeg at all
B. SDR via external library
C. SDR via a new libavradio library
D. SDR via libavdevice

For what it's worth as a user of ffmpeg I hope the outcome is not A, I believe having support for RTL-SDR in ffmpeg would be neat and I'd love to use it (at home, at work I'd compile ffmpeg with SDR disabled). I'm not qualified to comment on whether B,C or D are better ways to achieve it.

- Cosmin












_______________________________________________
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".

  parent reply	other threads:[~2023-09-26 22:50 UTC|newest]

Thread overview: 97+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-06 16:04 [FFmpeg-devel] [RFC] Release 6.1 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                   ` Cosmin Stejerean via ffmpeg-devel [this message]
2023-10-03 19:22                 ` Michael Niedermayer
2023-10-04 15:19                   ` 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=0101018ad3af8f2d-b6b5fd6a-17a8-4d0e-bc9f-f31f0ca58a00-000000@us-west-2.amazonses.com \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=cosmin@cosmin.at \
    /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