With the introduction of MIDI 2.0 and MIDI-CI there has been an increased use of Manufacturer Id’s, more commonly known as SysEx Ids. Some core mechanisms in MIDI 2.0, including the discovery mechanisms of the UMP Format and MIDI-CI, require the use of a SysEx Id. This was not a requirement in MIDI 1.0.
In 2025 The MIDI Association is introducing significant changes to the way SysEx Ids are handled.
- SysEx Ids are now permanent and owned in perpetuity. We no longer require an annual renewal fee.
- Any company or entity that is a current MIDI Association corporate member or becomes a corporate member in the future will now own the SysEx Id they are assigned at membership in perpetuity
- Any company that has an active SysEx Id listed on the MIDI Association website now owns that SysEx Id in perpetuity
- Even those companies that are out of business, or have lapsed their SysEx membership now own the SysEx Ids listed on the MIDI Association website in perpetuity.
The reasons for this change in policy are practical in nature. Interoperability has always been the cornerstone of MIDI. The MIDI Association has never rescinded a SysEx Id and doing so could cause problems even with decades old products in the market.
Where are SysEx Ids used in MIDI 2.0?
MIDI 2.0 requires the use of Manufacturer Ids in several key areas:
- MIDI-CI Discovery Messages require the Manufacturer, Family, Model Ids
- MIDI-CI Manufacturer defined Profiles
- MIDI-CI Property Exchange DeviceInfo Resource declares the Manufacturer, Family, Model Id’s as JSON properties.
- UMP Device Identity Notification Message optionally provides the Manufacturer, Family, Model Id’s
- UMP System Exclusive 8 uses the 16 bit Manufacturer Id, Special Id 0x7D, or Universal System Exclusive Id in the initial data bytes.
- UMP Mixed Data Set uses the 16 bit Manufacturer Id, Special Id 0x7D, or Universal System Exclusive Id.
Note: in MIDI 1.0 byte Streams and UMP, System Exclusive Message payload shall include the Manufacturer Id, Special Id 0x7D, or Universal System Exclusive Id in the initial data bytes.
Which System Exclusive Id should I use?
There are several ways to get a System Exclusive Id for enabling MIDI 2.0 in a product:
- Join the MIDI Association. A System Exclusive Id is assigned as a benefit of paid membership.
- Purchase a System Exclusive Id from the MIDI Association
- The System Exclusive Id 0x7C may be used with the limitations described below.
- The System Exclusive Id 0x7D may be used with the limitations described below.
1. Join as Corporate Member
Cost from $600/year
Small to large companies who create and distribute products using the MIDI protocol.
There are significant benefits to being a corporate member:
- Unique SysEx Id included
- Get access to MIDI 2.0 specifications under development and Member Only developer tools for those new specifications
- Have a voice and be a voting member on new MIDI specs
- Apply to use the MIDI 2.0 logo marks at no charge
The annual membership cost is dependent on the annual turn-over of your organization.
https://midi.org/corporate-membership-app
2. Paid SysEx Id Holder
Cost $240 (one time fee)
For smaller developers and startups, there is the choice to purchase a non-voting SysEx Id membership that uniquely identifies your MIDI products and lets you do all sorts of creative products with MIDI including MIDI 2.0.
https://midi.org/sysex-only-app
3. 0x7C Limited Non-Commercial Id: Products can be released to the Public (Introduced in 2025)
No Charge to Use
Special Id 0x7C is defined by MIDI 2.0 specifications for non-commercial use. Special Id 0x7C Id may be used on any product released to the public, so long as the product does not receive any financial gain either directly or indirectly. Special Id 0x7C may be used only for the following:
- UMP Endpoint Discovery mechanisms
- MIDI-CI Discovery Mechanisms
MIDI-CI Discovery is required for and enables:- Standardized MIDI-CI Profiles
- Standardized MIDI-CI Property Exchange Resources
- MIDI-CI Process Inquiry
- Property Exchange DeviceInfo Resource
The Id shall not be used for any of the following mechanisms:
- MIDI-CI Manufacturer defined Profiles
- UMP System Exclusive 8
- UMP Mixed Data Set
- System Exclusive messages with custom or manufacturer defined data format.
Example 1: You are working on a Open Source DIY synth using MIDI-CI Piano Profile hosted on Github and the product is not sold.
Example 2: You provide a free software tool for monitoring MIDI Messages.
Devices using this special id are encouraged to enter the MIDI Innovation Awards. This way the MIDI Association, and the world, can see how you use 0x7C to make new and interesting MIDI devices and applications!
4. 0x7D Non-commercial: Products cannot be released to the Public
No Charge to Use
Special Id 0x7D is defined by MIDI 1.0 specifications for non-commercial use (e.g. schools, research, etc.) and is not to be used on any product released to the public.
Example 1: You are working on a one off art project for your own benefit.
Example 2: You are researching and prototyping an idea for a school project.
FAQ
Can I upgrade my membership?
Yes! For example, it is common for companies that upgrade from being a SysEx Holder to being members.
Can my Manufacturer Id be reassigned?
While this may have occurred in the very distant past, MIDI Association does not reassign unused Manufacturer Ids.
Can I transfer ownership of my Manufacturer Id?
Yes, However the entity that acquires the Manufacturer Id will need to pay the one off fee again to cover handling costs.