MIDI Forum

[quotePost id=20238]Maybe there is some ID for general use, this is ID 0x7D -> educational, although it could be a manufacturer, I don't know, they ar...

Yes, I think it would be good if someone from MMA could clarify this. If you think about it, the situation is rather absurd. In MIDI 1.0, you only ...

JohnG, Yes, the MIDI-CI uses Universal System Exclusive commands that include Manufacturer SysEx ID, something that the "Details" page clearly stat...

Thanks for the thorough explanation. Unfortunately, you verify my fear that the MIDI 2.0 requirement for a Manufacturer SexEx ID will effectively bloc...

I assume that ONLY the SysEx components would be affected by the 'problem' of needing the SysEx ID. Yes, that is probably true. But since MIDI-CI i...

I don't want to spend the time and energy to learn MIDI 2.0 and implement a solution just to find out that I must pay $260/year to be able to use it. ...

OK, so we're back to where we started? Since MIDI-CI by definition is bidirectional (and SysEx based), everyone that wants to use MIDI 2.0 must have a...

In MIDI 1.0, I didn't have to talk via SysEx unless I had some special requirement. I can, e.g. (which I have done), create software that remote contr...

I'm developing software, not devices. From what I can see, the SysEx ID is not "optional" if I want to use Midi 2.0. I hope I misunderstand this, but ...

From the "Details about MIDI 2.0" page: "To implement MIDI-CI and MIDI 2.0, you need a manufacturers SysEx ID. A SysEx ID by itself is $260 a yea...