1. Introduction
MIDI 2.0 Compliance is defined in the M2-100-U MIDI 2.0 Specification Overview document and other related MIDI 2.0 specifications published by The MIDI Association (TMA) and the Association of Musical Electronics (AMEI).
THE MIDI MANUFACTURERS ASSOCIATION and ASSOCIATION OF MUSICAL ELECTRONICS INDUSTRY MIDI 2.0 TRADEMARK LICENSING MANAGEMENT AGREEMENT requires a developer to submit the following checklist as a claim for verification of MIDI 2.0 compliance by TMA or AMEI.
2. MIDI 2.0 Logo License Implementation Requirements
Any Device which claims MIDI 2.0 compatibility shall implement either A or B, or both A and B:
A. MIDI-CI* to at least its minimum requirements, including discovery mechanisms, plus any one or more of the following features:
- One or more Profiles controllable by MIDI-CI Profile Configuration messages.
- Any Property Data exchange by MIDI-CI Property Exchange messages.
- Any Process Inquiry exchange by MIDI-CI Process Inquiry messages.
B. The UMP Data Format** to at least its minimum requirements, including discovery mechanisms, plus any one or more of the following features:
- MIDI 2.0 Channel Voice Messages as defined by the Universal MIDI Packet (UMP) Format and MIDI 2.0 Protocol.
- Jitter Reduction Timestamps as defined by the Universal MIDI Packet (UMP) Format and MIDI 2.0 Protocol.
- System Exclusive 8 as defined by the Universal MIDI Packet (UMP) Format and MIDI 2.0 Protocol.
- Mixed Data Set as defined by the Universal MIDI Packet (UMP) Format and MIDI 2.0 Protocol.
*Note: MIDI-CI v1.2 requires the support of its discovery mechanisms. For a list of the complete minimum
requirements to implement MIDI-CI see the M2-101-UM MIDI Capability Inquiry (MIDI-CI) Version 1.2 specification.
**Note: UMP and MIDI 2.0 Protocol v1.1 requires the support of its UMP Endpoint discovery mechanisms.
For a list of the complete minimum requirements to implement UMP Format, see the M2-104-UM UMP and MIDI 2.0 Protocol
Version 1.1 specification.
Testing of MIDI 2.0 products is the sole responsibility of the individual manufacturer. The only requirement for
self-certification is to complete this MIDI 2.0 Logo Implementation Checklist, which documents which features
the specific product supports.
We strongly encourage your company to access all the documents and tools available to MIDI Association members.
A thorough understanding of all MIDI specifications is a vital prerequisite to correctly implementing MIDI 2.0.
2. Device Details
The identity of the device is declared on the cover page of this form. Following are identifier values used in various MIDI messages.
Table 1: Identifiers used in MIDI Messages
4. Discovery
Table 2: MIDI-CI Discovery
Table 2: MIDI-CI Discovery
5. MIDI-CI Support
Table 4:
Table 5:
Profile Configuration
Table 6: If Device declares support for Profile Configuration in Table 5, list supported Profiles.
Property Exchange
Table 7: If Device declares support for Property Exchange in Table 5, list supported Resources.
Process Inquiry
Table 8: If Device declares support for Process Inquiry in Table 5, confirm support here.
6. UMP Support
Table 9: If Device declares support for UMP.
Table 10: If Device declares support for MIDI 2.0 Protocol, then supporting at least one of the following MIDI 2.0 Protocol format messages is Required.
Transports
Table 11: