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

More

Browse Source
This commit is contained in:
Jamie Hardt
2023-11-08 12:47:44 -08:00
parent f3f9f6b784
commit 75ec68f500
1 changed files with 25 additions and 38 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -70,17 +70,17 @@ 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 unlikely an audio app would recognize one if it saw it.
.SS Broadcast-WAVE Metadata .SS Broadcast-WAVE Metadata
Broadcast-WAVE is a set of extensions to WAVE files to facilitate media Broadcast-WAVE is a set of extensions to WAVE files to facilitate media
production maintained by the EBU. production maintained by the EBU.
@@ -194,41 +194,28 @@ metadata (Suppl. 6), and other things.
.TP .TP
.B SMPTE 330M-2011 \- Unique Material Identifier. SMPTE, 2011. .B SMPTE 330M-2011 \- Unique Material Identifier. SMPTE, 2011.
Describes the format of the SMPTE UMID field, a 32- or 64-byte UUID used to Describes the format of the SMPTE UMID field, a 32- or 64-byte UUID used to
identify media files. Broadcast-WAVE files conforming to identify media files. UMIDs are usually a dumb number in their 32-byte form,
but the extended form can encode a high-precision timestamp (with options for
epoch and timescale) and geolocation information. Broadcast-WAVE files
conforming to
.B "EBU 3285 v2" .B "EBU 3285 v2"
have a SMPTE UMID embedded in the have a SMPTE UMID embedded in the
.I bext .I bext
chunk. chunk.
.\" .UR https://datatracker.ietf.org/doc/html/rfc2361 .SS Audio Definition Model
.\" RFC 2361 .TP
.\" .UE .B ITU Recommendation BS.2076-2-2019 \- Audio definition model. ITU, 2019.
.\" A large RFC compilation of all of the known (in 1998) audio encoding formats Defines the Audio Definition Model, entities, relationships and properties. If
.\" in use. 104 different codecs are documented with a name, the corresponding you ever had any questions about how ADM works, this is where you would start.
.\" magic number, and a vendor contact name, phone number and address (no .SS iXML Metadata
.\" emails, strangely). Almost all of these are of historical interest only. .TP
.\" .SS RF64/Extended WAVE Format .B iXML Specification v3.01. Gallery Software, 2021.
.\" iXML is a standard for embedding mostly human-created metadata into WAVE files,
.\" .TP and mostly with an emphasis on location sound recorders used on film and
.\" .UR https://www.itu.int/dms_pubrec/itu-r/rec/bs/R-REC-BS.2088-1-201910-I!!PDF-E.pdf television productions. Frustratingly the developer has never published a DTD
.\" ITU Recommendation BS.2088-1-2019 or schema validation or strict formal standard, and encourages vendors to just
.\" .UE do whatever, but most of the heavily-traveled metadata fields are standardized,
.\" BS.2088 gives a detailed description of the internals of an RF64 file, for recording information like a recording's scene, take, recording notes,
.\" .I ds64 circled or alt status. iXML also has a system of
.\" structure and all formal requirements. It also defines the use of .B "families"
.\" .IR <axml> , for associating several WAVE files together into one recording.
.\" .IR <bxml> ,
.\" .IR <sxml> ,
.\" and
.\" .I <chna>
.\" metadata chunks for the carriage of Audio Definition Model metadata.
.\" .TP
.\" .UR https://tech.ebu.ch/docs/tech/tech3306.pdf
.\" EBU Tech 3306 "RF64: An Extended File Format for Audio Data"
.\" .UE
.\" Version 1 of Tech 3306 laid out the
.\" .I RF64
.\" extended WAVE
.\" file format almost identically to
.\" .IR BS.2088 ,
.\" Version 2 of the standard wholly adopted
.\" .IR BS.2088 .