From: Stefano Sabatini <stefasab@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Stefano Sabatini <stefasab@gmail.com>
Subject: [FFmpeg-devel] [PATCH] doc/muxers: add ircam
Date: Fri, 29 Mar 2024 14:21:08 +0100
Message-ID: <20240329132108.38069-1-stefasab@gmail.com> (raw)
Most of the content copy&pasted from:
http://fileformats.archiveteam.org/wiki/Berkeley/IRCAM/Carl_Sound_Format
---
doc/muxers.texi | 18 ++++++++++++++++++
1 file changed, 18 insertions(+)
diff --git a/doc/muxers.texi b/doc/muxers.texi
index 5cce26a43f..39597e000b 100644
--- a/doc/muxers.texi
+++ b/doc/muxers.texi
@@ -2682,6 +2682,24 @@ ffmpeg -f x11grab -framerate 1 -i :0.0 -q:v 6 -update 1 -protocol_opts method=PU
@end example
@end itemize
+@section ircam
+Berkeley / IRCAM / CARL Sound Filesystem (BICSF) format muxer.
+
+The Berkeley/IRCAM/CARL Sound Format, developed in the 1980s, is a result of the
+merging of several different earlier sound file formats and systems including
+the csound system developed by Dr Gareth Loy at the Computer Audio Research Lab
+(CARL) at UC San Diego, the IRCAM sound file system developed by Rob Gross and
+Dan Timis at the Institut de Recherche et Coordination Acoustique / Musique in
+Paris and the Berkeley Fast Filesystem.
+
+It was developed initially as part of the Berkeley/IRCAM/CARL Sound Filesystem,
+a suite of programs designed to implement a filesystem for audio applications
+running under Berkeley UNIX. It was particularly popular in academic music
+research centres, and was used a number of times in the creation of early
+computer-generated compositions.
+
+This muxer accepts a single audio stream containing PCM data.
+
@section matroska
Matroska container muxer.
--
2.34.1
_______________________________________________
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:[~2024-03-29 13:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20240329132108.38069-1-stefasab@gmail.com \
--to=stefasab@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