Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: "Tomas Härdin" <git@haerdin.se>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v2] avformat: add Software Defined Radio support
Date: Sat, 24 Jun 2023 23:03:58 +0200
Message-ID: <ba2c709b793a720b2f81d39e6a962b2685a96746.camel@haerdin.se> (raw)
In-Reply-To: <F07245E0-1575-4D39-BFE3-A32B90442943@remlab.net>

lör 2023-06-24 klockan 22:27 +0200 skrev Rémi Denis-Courmont:
> Unless you're connecting to the radio receiver via IP (which would be
> a kludge IMO)

Just a minor point: piping IQ data over TCP or UDP is actually quite
common in the radio scene. I also wouldn't be surprised if Linux gains
an API for dealing with IQ data in the future. That would allow writing
more driver-esque radio stuff.

Because radio is such a wide field, there's no place where adding it in
FFmpeg is likely to be appropriate. A demodulator could output data
packets, or bitstreams, or audio, or video, or fax images, or IQ data
etc etc. Should we have an APRS implementation in lavf? AX.25? Maybe we
should implement WiFi?

This reminds me of the IPFS debacle.

/Tomas
_______________________________________________
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-24 21:04 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
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 [this message]
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=ba2c709b793a720b2f81d39e6a962b2685a96746.camel@haerdin.se \
    --to=git@haerdin.se \
    --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