List chunk (of a Wave file)

5

A list chunk defines a list of sub-chunks and has the following format.


Byte sequence descriptionLength in bytesStarts with byte in the chunkValue
chunk ID40x00The ASCII character string "list"
size40x04The size of the sub-chunk less 8 (less the "chunk ID" and the "size")
list type ID40x08Various ASCII character strings. Two common types are "adtl" (associated data list) and "info" (text information about copyright, authorship, etc.)
datavarious0x0CDepends on the list type ID

An associated data list, for example, would define text labels and names for cue points. An associated data list typically uses label sub-chunks, note sub-chunks, and labeled text sub-chunks.

A label sub-chunk and a note sub-chunk have the same structure.


Byte sequence descriptionLength in bytesStarts with byte in the sub-chunkValue
sub-chunk ID40x00The ASCII character string "labl" or "note"
size40x04The size of the chunk less 8 (less the "sub-chunk ID" and the "size")
cue point ID40x08The ID of the relevant cue point (see Cue chunk (of a Wave file))
datavarious0x0CSome ASCII text

The ASCII text is null terminated and must be padded, if not word aligned.

The labeled text sub-chunk associates some portion of the audio data with text and serves as a marker. This sub-chunk has the following format.


Byte sequence descriptionLength in bytesStarts at byte in the sub-chunkValue
sub-chunk ID40x00The ASCII character string "ltxt"
size40x04The size of the sub-chunk less 8 (less the "sub-chunk ID" and the "size")
cue point ID40x08The ID of the relevant cue point
sample length40x0CThe number of samples in the segment of audio data described by this chunk
purpose ID40x10The purpose of the text. Common IDs are "scrp" for script and "capt" for closed captioning
country20x14The country of the text
language20x16The language of the text
dialect20x18The dialect of the text
code page20x1AThe code page for the text
datavarious0x1CSome ASCII text

The labeled text sub-chunk is always a part of an associated data list chunk.

When a list chunk carries the list type ID "info", the list contains information about the copyright, author, engineer of the file, and other similar text. The data of the list chunk is organized as follows.

Info ID (4 byte ASCII text) for information 1
Size of text 1
Text 1
Info ID (4 byte ASCII text) for information 2
Size of text 2
Text 2

Common info IDs in Wave files are as follows.


Info IDThe corresponding text describes
"iart"The artist of the original subject of the file
"icms"The name of the person or organization that commissioned the original subject of the file
"icmt"General comments about the file or its subject
"icop"Copyright information about the file (e.g., "Copyright Some Company 2011")
"icrd"The date the subject of the file was created (creation date)
"ieng"The name of the engineer who worked on the file
"ignr"The genre of the subject
"ikey"A list of keywords for the file or its subject
"imed"Medium for the original subject of the file
"inam"Title of the subject of the file (name)
"iprd"Name of the title the subject was originally intended for
"isbj"Description of the contents of the file (subject)
"isft"Name of the software package used to create the file
"isrc"The name of the person or organization that supplied the original subject of the file
"isrf"The original form of the material that was digitized (source form)
"itch"The name of the technician who digitized the subject file

All text must be word aligned.

See also:
Wave file format



  Rating
Rate This Page: Poor Great   |  Rate Content |
Average rating:  5   
00001
12345
Number of Ratings : 1
  Comments
Add Comment
mic
This is correct. It should be "ltxt". It is now fixed.
Posted At 11-08-2016 10:11:32

Richard Lee
As per the above comment - the second listl/note table is incorrect - the ChunkId should read "ltxt” (labelled text) not "note"/"labl".
Posted At 10-05-2015 01:34:44

The "labl" or "note" tables (above) seem to replicate but the first row "Byte sequence description" is sub-chunk ID vs chunk-ID... My assumption is that the tables are documenting the same sub-chunk - and as a result the use of "chunk-ID" in the second table is incorrect --- If my assumption is correct I would remove the redundant table because it suggests that there are two chunk/sub-chunks that have the same "Byte sequence description"
Posted At 08-02-2015 18:03:46



Copyright 2006 by Kaliopa Publishing, LLC