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: Re: [FFmpeg-devel] [PATCH v6 0/1] avformat: add Software Defined Radio support
Date: Sat, 1 Jul 2023 22:06:35 +0200
Message-ID: <20230701200635.GH1093384@pb2> (raw)
In-Reply-To: <2e90ba71-f56f-974d-d76d-a750c480c09c@martin.st>


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

On Sat, Jul 01, 2023 at 10:41:34PM +0300, Martin Storsjö wrote:
> On Sat, 1 Jul 2023, Michael Niedermayer wrote:
> 
> > On Sat, Jul 01, 2023 at 12:36:06AM +0300, Martin Storsjö wrote:
> > > On Fri, 30 Jun 2023, Michael Niedermayer wrote:
> > > 
> > > > On Thu, Jun 29, 2023 at 05:43:53PM +0200, Paul B Mahol wrote:
> > > > > If you apply this I will apply my pending libswresample commits and also
> > > > > remove sonic decoder from libavcodec.
> > > > 
> > > > ok, if you plan to fix the bugs in the libswresample patches
> > > > 
> > > > ill wait a bit, so others can object and if no objections will
> > > > apply the current SDR patch with the probe function disabled.
> > > > That ensures it will not be used without the user explicitly
> > > > selecting it.
> > > 
> > > I object to merging this patch.
> > > 
> > > As numerous others have said already, this is at the wrong level of
> > > abstraction, even if it happens to work for you for the current use case.
> > > 
> > > Even if it is disabled by default, git master isn't a playground for
> > > personal projects.
> > 
> > If you belive this is implemented at the wrong level,
> > can you please elaborately explain the implementation which is
> > in your oppinion at the correct level ?
> 
> As there are talks about receiving DAB/DVB from the same source, those would
> definitely be on a different level than libavformat, since the output of
> them would be an mpegts stream (or multiple), or whatever transport format
> DAB uses.

If i search for "mpegts" in libavformat i find
hls, rtp, rtsp, segment, wtv
but iam sure these arent the only mixed containers.

If we look at DAB or DVB in a more fundamental way, they have no need
for mpegts.
Should this (apparently unneeded) design decission in DAB/DVB dictate
design on our side when it has not previously ?

If so, what design ?



> As for purely AM/FM, I'm not quire sure what the right level for
> that is though.

>
> In any case, I disagree with the procedure of stating to push the patch if
> there's no objections, when there has been numerous objections from
> essentially most of the active community already.

The objections have been unclear, are they against SDR, against the
implementation.
I took the liberty to be pushy here to get this more clear. And i will
continue to do this until i get clear responses. Because otherwise
iam just stuck as i dont know how to correct the design and code.

Thank you for clarifying the libavformat issue.

[...]

-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Breaking DRM is a little like attempting to break through a door even
though the window is wide open and the only thing in the house is a bunch
of things you dont want and which you would get tomorrow for free anyway

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

  parent reply	other threads:[~2023-07-01 20:06 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-28 21:25 Michael Niedermayer
2023-06-28 21:25 ` [FFmpeg-devel] [PATCH v6] " Michael Niedermayer
2023-06-29 15:43 ` [FFmpeg-devel] [PATCH v6 0/1] " Paul B Mahol
2023-06-30 14:08   ` Michael Niedermayer
2023-06-30 14:38     ` Jean-Baptiste Kempf
2023-06-30 17:40       ` Michael Niedermayer
2023-06-30 17:57         ` Paul B Mahol
2023-06-30 18:02         ` Michael Niedermayer
2023-07-01 15:28           ` Rémi Denis-Courmont
2023-07-01 18:56             ` Michael Niedermayer
2023-07-01 19:30               ` Paul B Mahol
2023-07-02  9:40           ` Nicolas George
2023-07-02 10:08             ` Paul B Mahol
2023-07-02 13:47               ` Rémi Denis-Courmont
2023-07-02 16:01                 ` Nicolas George
2023-07-02 18:21                   ` Rémi Denis-Courmont
2023-07-02 11:00       ` Michael Niedermayer
2023-07-02 16:11         ` Nicolas George
2023-07-02 18:55         ` Lynne
2023-07-02 21:14           ` Michael Niedermayer
2023-07-02 22:03             ` Lynne
2023-07-02 22:46               ` Michael Niedermayer
2023-07-10  6:57                 ` Lynne
2023-07-11 21:09                   ` Michael Niedermayer
2023-06-30 17:00     ` Kieran Kunhya
2023-07-01 15:20       ` Michael Niedermayer
2023-06-30 21:36     ` Martin Storsjö
2023-07-01 14:44       ` Michael Niedermayer
2023-07-01 19:41         ` Martin Storsjö
2023-07-01 19:56           ` Tomas Härdin
2023-07-01 20:06           ` Michael Niedermayer [this message]
2023-07-01 20:42             ` Kieran Kunhya
2023-07-01 21:25               ` Michael Niedermayer
2023-07-01 21:32                 ` Kieran Kunhya
2023-07-01 19:08       ` Anton Khirnov
2023-07-01 19:35       ` Michael Niedermayer
2023-07-02  9:58       ` Nicolas George
2023-07-02 10:10         ` Paul B Mahol
2023-07-02 10:43         ` Jean-Baptiste Kempf
2023-07-02 16:07           ` Nicolas George
2023-07-02 18:13             ` Jean-Baptiste Kempf
2023-07-02 18:20               ` Nicolas George
2023-07-02 18:32                 ` Michael Niedermayer
2023-07-02 18:52             ` Lynne
2023-07-02 19:52               ` Nicolas George
2023-07-02 20:29                 ` Lynne
2023-06-30 22:02     ` Tomas Härdin
2023-07-02  9:28       ` Nicolas George

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=20230701200635.GH1093384@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