From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: [FFmpeg-devel] SDR lib comments
Date: Sat, 23 Sep 2023 18:43:44 +0200
Message-ID: <20230923164344.GG3543730@pb2> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1274 bytes --]
Hi all
ive promised to write a mail about SDR at the confernece about a seperate lib,
here is it (i in fact had this half written already before)
The SDR code in FFmpeg was and is intended to be a plain simple libavdevice input device
same as x11 and others
SDR is complex and not a simple memcpy() from a /dev file. To implement SDR many
design decissions have to be made, there are often more than one way things can be
done.
In the inside of a SDR input module these decissions are invissible,
they can be changed each commit as bugfixes and optimizatzions require.
OTOH, if SDR or parts of SDR are in a seperate library, some decissions now would
affect the public API and ABI, thats a added difficulty.
With audio resampling, FFmpeg supported resampling internally long before
providing libswresample. Audio resampling is also simpler than SDR.
Is a seperate library really the right choice for SDR in FFmpeg at this stage ?
Also code can always be moved into an seperate library but its much harder
to move or change it once such library is public.
Thx
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
It is dangerous to be right in matters on which the established authorities
are wrong. -- Voltaire
[-- 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 reply other threads:[~2023-09-23 16:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-23 16:43 Michael Niedermayer [this message]
2023-09-28 10:28 ` Anton Khirnov
2023-09-28 19:28 ` Michael Niedermayer
2023-09-28 21:05 ` Rémi Denis-Courmont
2023-09-28 22:18 ` Michael Niedermayer
2023-09-29 7:03 ` Nicolas George
2023-09-29 8:23 ` Rémi Denis-Courmont
2023-10-02 10:08 ` Nicolas George
2023-09-29 8:34 ` Rémi Denis-Courmont
2023-10-02 10:06 ` Nicolas George
2023-09-29 12:59 ` Vittorio Giovara
2023-10-02 10:05 ` Nicolas George
2023-09-28 21:07 ` Vittorio Giovara
2023-09-28 22:58 ` Michael Niedermayer
2023-09-29 9:43 ` Anton Khirnov
2023-09-29 11:43 ` Nicolas George
2023-09-29 13:29 ` Rémi Denis-Courmont
2023-09-29 13:53 ` 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=20230923164344.GG3543730@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