MIDI Logo Implementation Checklist

Checklist Version 1.8
Please see specific Logo Implementation Checklist Help

 


Version:

Submission:
Embargo:

AMEI Logo
https://www.amei.or.jp
MIDI Association Logo
https://www.midi.org

© 2021 Association of Musical Electronic Industry (AMEI) (Japan)
© 2021 MIDI Manufacturers Association Incorporated (MMA) (Worldwide except Japan)

ALL RIGHTS RESERVED. NO PART OF THIS DOCUMENT MAY BE REPRODUCED OR TRANSMITTED IN ANY FORM OR BY ANY MEANS, ELECTRONIC OR MECHANICAL, INCLUDING INFORMATION STORAGE AND RETRIEVAL SYSTEMS, WITHOUT PERMISSION IN WRITING FROM THE MIDI MANUFACTURERS ASSOCIATION.

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.

3. 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
Device Identifier Byte 1 (hex) Byte 2 (hex) Byte 3 (hex) Byte 4 (hex)
Device Manufacturer (System Exclusive ID Number)
Device Family (LSB first)
Device Family Model Number (LSB first)
Software Revision Level (Format is Device specific)

4. Discovery

Table 2: MIDI-CI Discovery
MIDI-CI Support Version
If MIDI-CI is Supported MIDI Capability (MIDI-CI) Version
MIDI-CI Discovery Add "Yes" to Confirm
The Device performs MIDI-CI Discovery Transaction as an Initiator Recommended
The Device replies to MIDI-CI Discovery message as a Responder by sending a Reply to Discovery message. Required

Table 3: UMP Discovery
UMP Format Support Version
If UMP is Supported Universal MIDI Packet (UMP) Format Version
UMP Discovery (If UMP Version 1.1 or Higher) Add "Yes" to Confirm
The Device sends Endpoint Discovery message Recommended
The Device replies to Discovery message by sending an Endpoint Info Notification message Required

5. MIDI-CI Support

Table 4:
Basic MIDI-CI Functions (All Required) Add "Yes" to Confirm
Upon each power up, device creates a new, randomly generated MUID
The Device conforms to all other minimum requirements of the M2-101-UM MIDI-CI Specification, Version 1.1

Table 5:
Capability Inquiry Category Supported Requirement Add "Yes" to Confirm
Category 1: Protocol Negotiation Deprecated in MIDI-CI v1.2
Category 2: Profile Configuration At least one of Category 2, 3 or 4 is Required
Category 3: Property Exchange
Category 4: Process Inquiry

Profile Configuration

Table 6: If Device declares support for Profile Configuration in Table 5, list supported Profiles.
Name of Profile Supported Profile Level Add "Yes" to Confirm
GM2 Function Block (0x00 0x00)
Piano Profile (0x20 0x00)
Drawbar Organ Profile (0x20 0x01)
GM2 Single Channel (0x20 0x02)
Default Control Change Mapping (0x21 0x00)
Rotary Speaker (0x22 0x00)
MPE (0x31 0x00)

Property Exchange

Table 7: If Device declares support for Property Exchange in Table 5, list supported Resources.
Name of Property Exchange Resource Supported Requirement Note Add "Yes" to Confirm
ResourceList Required*
DeviceInfo (Foundational) Recommended
JSONSchema (Foundational) Optional
ChannelList Recommended
ProgramList Recommended
ModeList Optional
CurrentMode Optional
ExternalSync Optional
LocalOn Optional
ChannelMode Optional
BasicChannelRx Optional
BasicChannelTx Optional
State Optional
StateList Optional
AllCtrlList Optional
ChCtrlList Optional
CtrlMapList Optional
MaxSysex8Streams Deprecated June 2023
*Required if Property Exchange is supported.

Process Inquiry

Table 8: If Device declares support for Process Inquiry in Table 5, confirm support here.
Name of Process Inquiry Function Supported Requirement Note Add "Yes" to Confirm
The Device replies to Inquiry: MIDI Message Report message as a Responder by sending a Reply to MIDI Message Report, any available requested data, and End of MIDI Message Report message. Required*
*Required if Process Inquiry is supported.

6. UMP Support

Table 9: If Device declares support for UMP.
UMP Messages Supported Requirement Note Add "Yes" to Confirm
Device Reports Function Blocks Recommended For Most Devices
Not Recommended for DAWs
Stream Configuration Recommended
System Messages Optional
MIDI 1.0 Channel Voice Messages Recommended
MIDI 2.0 Channel Voice Messages Supporting at least one of these MIDI 2.0 features is Required.
Jitter Reduction Timestamps
System Exclusive 8
Mixed Data Set
Flex Data Messages Optional

Transports

Table 10:
Name of Transport Supported Add "Yes" to Confirm
USB MIDI 2.0
Other Transports, List Here:
Standard MIDI File v2.0 MIDI Clip File