Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Neal Gompa <ngompa13@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] FFmpeg release 6.1 (SDR Plans)
Date: Sat, 23 Sep 2023 02:49:47 -0400
Message-ID: <CAEg-Je_=1oUfZfrHLD=xTNFxaF1mDG5B7O+e5JSSY4STBwCY3A@mail.gmail.com> (raw)
In-Reply-To: <20230922163258.GX8640@pb2>

On Fri, Sep 22, 2023 at 12:33 PM Michael Niedermayer
<michael@niedermayer.cc> wrote:
>
> On Fri, Sep 22, 2023 at 03:55:57PM +0200, Gijs Peskens wrote:
> >
> > On 21-09-2023 18:21, Michael Niedermayer wrote:
> > > Hi all
> > >
> > > As the 6.1 release is upcoming and as it was previously stated by me that sdr
> > > will be part of 6.1. Heres some update of what i intend to do about that.
> > >
> > > People previously agreed to including a SDR input device in libavdevice with
> > > SDR in a seperate library.
> > >
> > > If the community and the SDR code are happy with each other before the release
> > > then SDR will simply be merged and be part of 6.1 like any other feature.
> > >
> > > OTOH If a majority of people are against the SDR code at the time of
> > > branching 6.1. Then i will make a separate release identical to 6.1 with
> > > the SDR code and of course also provide security support
> > What does this mean? Does this mean an FFmpeg release containing code that
> > interfaces with your SDR library? Or does it mean the library fully
> > integrated into FFmpeg?
>
> It depends on the code at the time of release. ATM there is no seperate
> library, just a SDR input device.
> creating a separte library and the related API/ABI needs to be done with
> thought and care not something to rush quickly.
>

What does this code *do*? All these arguments about the SDR code, and
I haven't seen it myself (because the email patch workflow really
makes it hard to track this stuff down, and I assume it was submitted
on list somewhere?)

If it's just taking SDR devices as inputs and allowing you to encode
audio and video streams, I'm not sure why you *wouldn't* have this as
something in libavdevice or extended from it as a separate library.




--
真実はいつも一つ!/ Always, there's only one truth!
_______________________________________________
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-09-23  6:50 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-10 22:14 [FFmpeg-devel] FFmpeg release 6.1 Michael Niedermayer
2023-04-10 22:16 ` James Almer
2023-04-11  8:46 ` Neal Gompa
2023-09-19 17:18 ` Niklas Haas
2023-09-19 19:16   ` Michael Niedermayer
2023-09-19 21:58     ` Lynne
2023-09-20  0:38       ` Neal Gompa
2023-09-20  2:24         ` Xiang, Haihao
2023-09-20 17:24       ` Michael Niedermayer
2023-09-20 17:43         ` Kieran Kunhya
2023-09-20 18:10           ` Michael Niedermayer
2023-09-20 22:47             ` Kieran Kunhya
2023-09-21  3:19               ` Jean-Baptiste Kempf
2023-09-21 12:51               ` Michael Niedermayer
2023-09-20 12:47     ` Niklas Haas
2023-09-20 18:00       ` Michael Niedermayer
2023-09-21 11:46     ` Dawid Kozinski/Multimedia (PLT) /SRPOL/Staff Engineer/Samsung Electronics
2023-09-21 16:21 ` [FFmpeg-devel] FFmpeg release 6.1 (SDR Plans) Michael Niedermayer
2023-09-21 16:33   ` Kieran Kunhya via ffmpeg-devel
2023-09-21 17:16     ` Nicolas George
2023-09-21 18:14       ` Vittorio Giovara
2023-09-21 18:19         ` Nicolas George
2023-09-21 18:47           ` Vittorio Giovara
2023-09-21 18:51             ` Nicolas George
2023-09-21 18:54               ` Vittorio Giovara
2023-09-21 19:04                 ` Nicolas George
2023-09-21 19:08                   ` Paul B Mahol
2023-09-26 18:14                     ` Nicolas George
2023-09-21 19:18                   ` Vittorio Giovara
2023-09-21 19:37                     ` Nicolas George
2023-09-21 19:44                       ` Paul B Mahol
2023-09-21 18:56     ` Michael Niedermayer
2023-09-26 19:59       ` Rémi Denis-Courmont
2023-09-21 16:39   ` Paul B Mahol
2023-09-22 13:55   ` Gijs Peskens
2023-09-22 16:32     ` Michael Niedermayer
2023-09-23  6:49       ` Neal Gompa [this message]
2023-09-23 10:55         ` Michael Niedermayer
2023-09-23 23:31           ` Neal Gompa
2023-09-24  9:12         ` Nicolas George
2023-09-24 11:56           ` Paul B Mahol
2023-09-24 12:17             ` Nicolas George
2023-09-24 17:33               ` Paul B Mahol
2023-09-24 17:45                 ` [FFmpeg-devel] libavdevice (was: FFmpeg release 6.1 (SDR Plans)) Nicolas George
2023-09-24 17:49                   ` Paul B Mahol
2023-09-24 17:54                     ` Nicolas George
2023-09-24 18:05                       ` Paul B Mahol
2023-09-24 18:09                         ` Nicolas George
2023-09-25 11:20                           ` Paul B Mahol
2023-09-26 18:12                             ` Nicolas George
2023-09-25  8:24                 ` [FFmpeg-devel] FFmpeg release 6.1 (SDR Plans) Kieran Kunhya
2023-09-26 20:17         ` Rémi Denis-Courmont

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='CAEg-Je_=1oUfZfrHLD=xTNFxaF1mDG5B7O+e5JSSY4STBwCY3A@mail.gmail.com' \
    --to=ngompa13@gmail.com \
    --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