Posted: 07-30-22 2:26 am
After 15 years, Synthesia LLC has finally joined the MIDI Association, which means we've now got our own Manufacturer ID for SysEx messages:
Synthesia LLC Manufacturer ID: 0x00 0x02 0x45
Forum posts are easier to edit than websites (and keeping similar references on the forum has been a good experience), so this top post is now the official technical reference for all the SysEx messages the Synthesia client app can send and receive.
In general, messages will conform to the usual SysEx-style "packet":
If we ever reach 127 message types (... and I hope we don't), I'll use the same leading-zero trick that the MIDI Association uses for manufacturer IDs.
0x01 Version Identification
Added in Synthesia 10.9
This message is sent immediately as an output device is opened for use. It identifies the major and minor version of the Synthesia client app. There are two data bytes (using the version number for "Synthesia 10.9" as example values):
0x0A Major version
0x09 Minor version
Synthesia LLC Manufacturer ID: 0x00 0x02 0x45
Forum posts are easier to edit than websites (and keeping similar references on the forum has been a good experience), so this top post is now the official technical reference for all the SysEx messages the Synthesia client app can send and receive.
In general, messages will conform to the usual SysEx-style "packet":
Code: Select all
0xF7 Start of SysEx
0x00
0x02 Synthesia LLC Manufacturer ID
0x45
0xNN Message type byte
... message-specific payload (any number of data bytes)
0x7F End of SysEx
0x01 Version Identification
Added in Synthesia 10.9
This message is sent immediately as an output device is opened for use. It identifies the major and minor version of the Synthesia client app. There are two data bytes (using the version number for "Synthesia 10.9" as example values):
0x0A Major version
0x09 Minor version