Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: [FFmpeg-devel] [RFC] SDR
Date: Thu, 22 Jun 2023 16:57:09 +0200
Message-ID: <20230622145709.GB3250409@pb2> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2258 bytes --]

Hi all

My humble opinion(s) and plan(s) about SDR

FFmpeg as a multimedia framework should support SDR.

The only practical way to support SDR in FFmpeg ATM is through a demuxer (or equivalent)
Not everyone is happy about a SDR demuxer.

The "active" code could be in the demuxer itself or an external library.

I think the 2 important factors for external vs internal are
1. Does it support features beyond what a multimedia framework needs?
2. How many active developers work on it

If we support just audio and video (de)modulation it fits nicely in FFmpeg
maybe we should consider improving the APIs we have so we have better places
than demuxers for functionality like this, but thats a long term goal that
requires a team effort or a dedicated volunteer. Its not a bad idea at all and
I certainly am in favor for improving the APIs.

OTOH if we support things beyond audio/video, maybe wifi packets, bluetooth
and so forth then SDR should be a seperate library.

Also this choice is not a constant, we can easily start out inside libavformat
and
* if sdrdemux grows beyond what makes sense in FFmpeg split it out into an external
  libraray
* if APIs in FFmpeg evolve so that other places become possible, move it into
  libavfilter or whatever other place fits better

What i would suggest is:
* get the current code or revission of it into the git master branch as a demuxer.
* see how many people enjoy working on SDR and how far these people want to take it
* keep an open mind about the future of this code, and move it elsewhere when it
  makes sense to do so.
* ATM i think incubating this SDR stuff in FFmpeg and have it grow makes more sense
  than having it in a seperate place and a demuxer in FFmpeg depending on that.

PS: Also something like plugins would help for things like this. As one could then
maintain code like a sdr-demuxer outside the main repository. So noone who doesnt
like it needs to touch it in any way while users who want it can easily enable
it ...

Thx

-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

When you are offended at any man's fault, turn to yourself and study your
own failings. Then you will forget your anger. -- Epictetus

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

             reply	other threads:[~2023-06-22 14:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-22 14:57 Michael Niedermayer [this message]
2023-06-22 15:01 ` James Almer
2023-06-22 15:09   ` Thilo Borgmann
2023-06-22 16:09 ` Anton Khirnov
2023-06-22 17:43   ` Michael Niedermayer
2023-06-22 18:52     ` Michael Niedermayer
2023-06-23 11:26   ` James Almer
2023-06-23 20:18 ` Tomas Härdin
2023-06-23 20:19   ` Tomas Härdin
2023-06-23 21:36     ` Michael Niedermayer
2023-06-24 10:12       ` Tomas Härdin
2023-06-24 21:29         ` 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=20230622145709.GB3250409@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