MIDI meta events. If empty, the value for the event is contained in an attribute, following the pattern of the MMA's MIDI DTD. Textual meta events have their values as text within the element. Standard MIDI File DTD: MIDI XML Version 2.0 - 18 June 2007 Copyright © 2004-2007 Recordare LLC. http://www.recordare.com/ This MusicXML™ work is being provided by the copyright holder under the MusicXML Document Type Definition Public License Version 2.0, available from: http://www.recordare.com/dtds/license.html MIDI XML is an XML representation of standard MIDI files for MIDI 1.0. Unlike standard MIDI files, it can have timestamps present as either absolute or delta values. This makes it convenient as an intermediate format to convert from the MusicXML format and other formats where note on and note off are not represented as discrete events. To convert to Standard MIDI Files, delta values must be used. Suggested use: <!DOCTYPE MIDIFile PUBLIC "-//Recordare//DTD MusicXML 2.0 MIDI//EN" "http://www.musicxml.org/dtds/midixml.dtd"> For Standard MIDI Files, channels are required; events are not rechannelized. Component DTD modules The MMA MIDI DTD contains the definitions of all MIDI events. Its regular address is: http://www.midi.org/dtds/MIDIEvents10.dtd For convenience, we include a local copy with our definition, and reference that here. Timestamps are either delta or absolute. They must all be one or the other throughout the MIDI XML file. Timestamps are numeric values measured in MIDI ticks. Standard MIDI File events include MIDI Channel messages, meta-events, and system exclusive events. Each track is a series of events. The MetaEvent and SysExEvent elements are defined below. The MIDIChannelMessage and MIDIMessage events are defined in the MMA's MIDI DTD (RP-038). The ProgramName and DeviceName meta-events are described in RP-019 from the MMA. They allow a Standard MIDI file to address multiple devices, enabling more than 16 channels of MIDI playback. The XMFPatchTypePrefix meta-event is described in RP-032 from the MMA. It allows specification of using General MIDI 1, General MIDI 2, or DLS to interpret subsequent program change and bank select messages in the same track. The meta-event hex 21 has been used, though unofficially, for a MIDI port or cable number. RP-019 deprecates this in favor of the DeviceName meta-event, but some programs still use this. An unrecognized meta-event has an attribute for its event type number. The data for the event is represented in hex within the element, as is done for system exclusives. MIDI system exclusive and end of exclusive events have their data represented as a series of 2-digit hex elements separated by spaces, as in the MMA MIDI DTD. MIDI is the root element Format indicates MIDI format 0, 1, or 2. So far only types 0 and 1 are explicitly supported by the MIDI XML format. TrackCount indicate the number of tracks in a file: 1 for type 0, usually more for types 1 and 2. The TrackCount matches the number of Track elements in the MIDI XML file. How many ticks in a beat (MIDI quarter note). Frame rate and ticks per frame are used with SMPTE time codes. TimestampType should be Delta or Absolute. Indicates the element name to look for in the initial timestamp in each MIDI event. Tracks contain the musical data and are made up of a series of events. The track number attribute is required.