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: Fri, 30 Jun 2023 19:40:53 +0200
Message-ID: <20230630174053.GB1093384@pb2> (raw)
In-Reply-To: <1ea6a4a3-ed1a-4c8c-8a99-82b670f6868f@betaapp.fastmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2113 bytes --]
On Fri, Jun 30, 2023 at 04:38:46PM +0200, Jean-Baptiste Kempf wrote:
> On Fri, 30 Jun 2023, at 16:08, Michael Niedermayer wrote:
> > Also as said previously, If there is at least a 2nd developer working
> > on this then we could & should move this to a seperate libraray (libavradio)
>
> Why wait for a 2nd dev?
It is significant work
And if there is no 2nd developer interrested then for whom am i doing that
work ?
The sdr code as it is currently, is usefull to end users. (already as it is
with the bugs it still has but as these get squished it will become more
usefull)
If its changed to a libavradio, the end user wont gain anything. Its
developers who may gain, but if there is no 2nd developer interrested then
well. I may be misunderstanding why iam being asked to do this work
Does anyone want to use libavradio ?
If yes, please volunteer to help create libavradio
If no, please do not ask for someone else to create something you do not intend to use
Also what is meant by a seperate libraray exactly by people is not clear to me
I can create a libavradio similar to libavformat and libavdevice
I fail to see the point of doing that but i can do that
so the code keeps the same demuxer interface and is used the same way
by players.
If people want me to create something else, I have to point out that
sofar noone explained what that would be. Or how that would interface
into the rest of the ecosystem.
I have no idea what use cases people have in mind, i have no idea
what APIs people have in mind.
I mean, if someone sees the demuxer and thinks
darn i wanted to use this for X but i cannot because Y. And then goes on explaining
X and Y and the suggestion for a seperate library, thats something to look into but
I dont think we had these suggestions.
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
If you fake or manipulate statistics in a paper in physics you will never
get a job again.
If you fake or manipulate statistics in a paper in medicin you will get
a job for life at the pharma industry.
[-- 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".
next prev parent reply other threads:[~2023-06-30 17:41 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 [this message]
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
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=20230630174053.GB1093384@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