jamie/wavinfo
1
0
Fork 0
mirror of https://github.com/iluvcapra/wavinfo.git synced 2026-01-02 18:00:41 +00:00
Code Issues Packages Projects Releases Wiki Activity

More info

Browse Source
This commit is contained in:
Jamie Hardt
2023-11-08 09:36:58 -08:00
parent 6654a194ba
commit 9e41d39b26
1 changed files with 26 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

31
data/share/man/man7/wavinfo.7
View File

@@ -1,4 +1,4 @@
.TH waveinfo 7 "2023-11-07" "Jamie Hardt" "Miscellaneous Information Manuals" .TH waveinfo 7 "2023-11-08" "Jamie Hardt" "Miscellaneous Information Manuals"
.SH NAME .SH NAME
wavinfo \- information about wave sound file metadata wavinfo \- information about wave sound file metadata
.\" .SH DESCRIPTION .\" .SH DESCRIPTION
@@ -14,6 +14,7 @@ alignment and other data. May take an "extended" form, with additional data
the file or if it is a compressed format. the file or if it is a compressed format.
.IP data .IP data
The audio data itself. PCM audio data is always stored as interleaved samples. The audio data itself. PCM audio data is always stored as interleaved samples.
.SS Auxiliary WAV Chunks
.IP JUNK .IP JUNK
A region of the file not currently in use. Clients sometimes add these before A region of the file not currently in use. Clients sometimes add these before
the the
@@ -38,6 +39,24 @@ four-character code identifying the form of the list, and is then followed
by chunks of the standard key-length-data form, which may themselves be by chunks of the standard key-length-data form, which may themselves be
LISTs that themselves contain child chunks. WAVE files don't tend to have a LISTs that themselves contain child chunks. WAVE files don't tend to have a
very deep heirarchy of chunks, compared to AVI files. very deep heirarchy of chunks, compared to AVI files.
.SS Extensions for Large Files
.IP RF64
An RF64 file has affordances to hold chunks larger than four gigabytes.
RF64 is designed so that a RIFF WAVE file can be in-place upgraded to an
RF64 without having to rewrite any audio or metadata that may already be
written. An RF64 file begins with an
.I RF64 LIST
form instead of a
.I RIFF
form. This is immediately followed by the obligatory...
.IP ds64
In RF64 files, the ds64 chunk begins the chunk list (in fact it must appear at
a fixed offset) and provides a list of 64-bit chunk sizes for any chunks in the
file that exceed four gigabytes. In an RF64 file, any chunk that exceeds the
32 bit size restriction will set its length field (after the identifier) to
.I 0xFFFFFFFF
and will write its true size into the list in
.IR ds64 .
.SS RIFF Metadata .SS RIFF Metadata
The RIFF container format has a metadata system common to all RIFF files, WAVE The RIFF container format has a metadata system common to all RIFF files, WAVE
being the most common at present, AVI being another very common format being the most common at present, AVI being another very common format
@@ -73,14 +92,14 @@ but hosts tend to use notes for longer text), and "length text"
.I ltxt .I ltxt
metadata records, which can give a cue a length, making it a range, and a text metadata records, which can give a cue a length, making it a range, and a text
field that defines its own encoding. field that defines its own encoding.
.IP CSET .IP cset
Defines the character set for all text fields in Defines the character set for all text fields in
.IR INFO , .IR INFO ,
.I adtl .I adtl
and other RIFF-defined text fields. By default, all of the text in RIFF and other RIFF-defined text fields. By default, all of the text in RIFF
metadata fields is Windows Latin 1/ISO 8859-1, though as time passes many metadata fields is Windows Latin 1/ISO 8859-1, though as time passes many
clients have simply taken to sticking UTF-8 into these fields. The clients have simply taken to sticking UTF-8 into these fields. The
.I CSET .I cset
cannot represent UTF-8 as a valid option for text encoding, it only speaks cannot represent UTF-8 as a valid option for text encoding, it only speaks
Windows codepages, and we've never seen one in a WAVE file in any event and Windows codepages, and we've never seen one in a WAVE file in any event and
it's vanishingly likely an audio app would recognize one if it saw it. it's vanishingly likely an audio app would recognize one if it saw it.
@@ -117,13 +136,14 @@ and encoding properties of individual channels in the WAVE file, and if the
WAVE file contains object-based audio, it will also give all of the positioning WAVE file contains object-based audio, it will also give all of the positioning
and panning automation envelopes. and panning automation envelopes.
.IP bxml .IP bxml
This is defined by the ITU as a gzip-compressed version of the A gzip-compressed version of the
.I axml .I axml
chunk. chunk.
.IP sxml .IP sxml
This is a hybrid binary/gzip-compressed-XML chunk that associates ADM A hybrid binary/gzip-compressed-XML chunk that associates ADM
documents with timed ranges of a WAVE file. documents with timed ranges of a WAVE file.
.SS Dolby Metadata .SS Dolby Metadata
Dolby metadata appears in Dolby Atmos Master ADM WAVE files.
.IP dbmd .IP dbmd
Records hints for Dolby playback applications for downmixing, level Records hints for Dolby playback applications for downmixing, level
normalization and other things. normalization and other things.
@@ -138,6 +158,7 @@ Region and cue point metadata.
.IP elm1 .IP elm1
.IP minf .IP minf
.IP umid .IP umid
Doesn't actually hold a SMPTE UMID!
.SH HISTORY .SH HISTORY
The oldest document that defines the form of a Wave file is the The oldest document that defines the form of a Wave file is the
.I Multimedia Programming Interface and Data Specifications 1.0 .I Multimedia Programming Interface and Data Specifications 1.0