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: Tue, 27 Jun 2023 19:07:30 +0200
Message-ID: <9c3a83eb42734540063fa25df65d669e6740dc1f.camel@haerdin.se> (raw)
In-Reply-To: <ZJrAh64p5NGWaUvT@phare.normalesup.org>

tis 2023-06-27 klockan 12:57 +0200 skrev Nicolas George:
> Tomas Härdin (12023-06-27):
> > Yes those are all fine use cases. But that doesn't explain why they
> > belong in FFmpeg rather than say a driver that turns generic SDRs
> > into
> > V4L FM devices, or a dedicated GUI application.
> 
> They can be implemented in any of these pieces of software, including
> FFmpeg, and each solution will have its own set of benefits and
> drawbacks in terms of performance, features, user interaction, etc.
> 
> In other words, a simple point of logic: X can Y does not imply X
> cannot
> Z for all Z not equal to Y.

I propose we add the ability for ffmpeg to send email. After all some
users might find that useful. And because many users use webmail we
should also implement HTML parsing.

/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-27 17:07 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
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 [this message]
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=9c3a83eb42734540063fa25df65d669e6740dc1f.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