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

Update wavinfo.7

Browse Source
This commit is contained in:
Jamie Hardt
2023-11-08 15:37:08 -08:00
committed by GitHub
parent d04af2d194
commit d7540b0a79
1 changed files with 10 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -4,7 +4,7 @@ wavinfo \- everything you ever wanted to know about WAVE metadata but were
afraid to ask afraid to ask
.SH DESCRIPTION .SH DESCRIPTION
.PP .PP
The WAVE file format is forwards-compatible, apart from audio data it can The WAVE file format is forwards-compatible. Apart from audio data, it can
hold arbitrary blocks of bytes which clients will automatically ignore hold arbitrary blocks of bytes which clients will automatically ignore
unless they recognize them and know how to read them. unless they recognize them and know how to read them.
.PP .PP
@@ -14,10 +14,10 @@ divided into segments or
.BR chunks , .BR chunks ,
which a client parser can either read or skip without reading. Chunks have which a client parser can either read or skip without reading. Chunks have
an identifier, or signature: a four-character-code which informs a client an identifier, or signature: a four-character-code which informs a client
what kind of chunk it is, and a length, which gives the client enough what kind of chunk it is, and a length. Based on this information, a client
information to skip over the chunk and find the next chunk in the file, can look at the identifier and decide if it knows how to read that chunk or
in the case the client doesn't care about it or doesn't know how to read if it wants to. If it doesn't, it can simply read the length and skip
it. past it.
.PP .PP
Some chunks are mandated by the Microsoft standard, specifically Some chunks are mandated by the Microsoft standard, specifically
.I fmt .I fmt
@@ -27,12 +27,12 @@ in the case of PCM-encoded WAVE files. Other chunks, like
.I cue .I cue
or or
.I bext .I bext
are optional, and hold metadata. Chunks can also nest inside other are optional, and hold metadata.
chunks, a special identifier .PP
Chunks can also nest inside other chunks, a special identifier
.I LIST .I LIST
is used to indicate these. A WAVE file is used to indicate these. A WAVE file is a recursive list: a top level
is a recursive list: a top level list of chunks, where chunks may contain list of chunks, where chunks may contain a list of chunks themselves.
a list of chunks themselves.
.SS Order of Metadata Chunks in a WAVE File .SS Order of Metadata Chunks in a WAVE File
.PP .PP
Chunks in a WAVE file can appear in any order, and a capable parser can Chunks in a WAVE file can appear in any order, and a capable parser can