Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
The track form contains information about a single track. It can be embedded in a Segment Form or stored in its own file.
<DMTK-form> -> RIFF( 'DMTK'
<trkh-ck>
[<trkx-ck>] // Optional track flags.
[<guid-ck>] // GUID for track object instance.
[<vers-ck>] // Version information.
[<UNFO-list>] // Name, author, copyright information, comments.
[<data>] // Track data.
)
<trkh-ck>
The first chunk contains the basic header information for a track.
<trkh-ck> -> trkh( <DMUS_IO_TRACK_HEADER> )
<trkx-ck>
This optional chunk contains flags for the track.
<trkx-ck> -> trkx( <DMUS_IO_TRACK_EXTRAS_HEADER> )
<guid-ck>, <vers-ck>, <UNFO-list>
For information on these three chunks, see Common Chunks.
<data>
The last element in the track form is the data for the track. The chunk type used for the data is identified in the DMUS_IO_TRACK_HEADER structure. The following standard track chunks are defined:
- Band Track Form
- Chord Track List
- Chordmap Track List
- Command Track Chunk
- Lyrics Track List
- Marker Track List
- Mute Track Chunk
- Parameter Control Track List
- Pattern Track Form
- Script Track List
- Segment Trigger Track List
- Sequence Track Chunk
- Signpost Track Chunk
- Style Track List
- Sysex Track Chunk
- Tempo Track Chunk
- Time Signature Track List
- Wave Track List