Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: James Almer <jamrial@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH v2] avformat: add Software Defined Radio support
Date: Thu, 22 Jun 2023 13:42:39 -0300
Message-ID: <020f7a32-60c4-22c4-19e9-9c25fef3b108@gmail.com> (raw)
In-Reply-To: <20230622162625.GD3250409@pb2>

On 6/22/2023 1:26 PM, Michael Niedermayer wrote:
> On Thu, Jun 22, 2023 at 12:10:06PM -0300, James Almer wrote:
>> On 6/22/2023 12:05 PM, Michael Niedermayer wrote:
>>> On Thu, Jun 22, 2023 at 10:55:44AM -0300, James Almer wrote:
>>>> On 6/22/2023 10:43 AM, Michael Niedermayer wrote:
>>>>> On Mon, Jun 19, 2023 at 12:28:05AM +0200, Michael Niedermayer wrote:
>>>>>> Signed-off-by: Michael Niedermayer <michael@niedermayer.cc>
>>>>>> ---
>>>>>>     configure                |    4 +
>>>>>>     doc/demuxers.texi        |   71 ++
>>>>>>     libavformat/Makefile     |    2 +
>>>>>>     libavformat/allformats.c |    2 +
>>>>>>     libavformat/sdrdemux.c   | 1739 ++++++++++++++++++++++++++++++++++++++
>>>>>>     5 files changed, 1818 insertions(+)
>>>>>>     create mode 100644 libavformat/sdrdemux.c
>>>>>
>>>>> Ill post a v3 later today or tomorrow that makes this work with the RTL-SDR Blog V3
>>>>
>>>> Shouldn't the SDR "demuxer" be in libavdevice? Being AVFMT_NOFILE and pretty
>>>> much a capture device, it seems to me that's the proper place.
>>>> I guess the problem arises with the sdrfile demuxer, which shares code with
>>>> the other one.
>>>
>>> I have no oppinon on this. I can move it to libavdevice if people prefer.
>>> do people prefer libavdevice for this ?
>>
>> I do. It's a capture device and depends on an external library to interface
>> with hardware. And like i said, you can keep the file demuxer in lavf, where
>> it does fit.
> 
> anyone objects if i move sdrfile then too into libavdevice ? because its the
> same code basically. Otherwise it would have to be some sort of #include of c
> file accross libs

It does not belong in lavd. The doxy in avdevice.h states "the 
(de)muxers in libavdevice are of the AVFMT_NOFILE type". And you can 
make the common code avpriv_ since both libraries are basically version 
locked. There's no need to duplicate it, but if you prefer that, you can 
indeed do an #include c file using the SHLIBOBJS list in Makefile which 
will trigger on shared builds.

> 
> 
>>
>>>
>>>
>>> personally i think libavdevice should be merged with libavformat.
>>
>> It's been suggested plenty of times. Anton attempted to at least kickstart
>> it once, but his plan was shot down.
>> No one has tried anything ever since.
> 
> How was it shut down ?
> 1. sent patch
> 2. apply it
> I think it should be done with the next major ABI bump
> 
> thx
> 
> [...]
> 
> 
> _______________________________________________
> 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".
_______________________________________________
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 16:42 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 [this message]
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
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=020f7a32-60c4-22c4-19e9-9c25fef3b108@gmail.com \
    --to=jamrial@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