Difference between revisions of "SysEx"
Jump to navigation
Jump to search
(Created SysEx page) |
|||
| Line 3: | Line 3: | ||
System-specific MIDI messages that can be used to access deeper system functionality than the standard general MIDI specification allows. Please see http://en.wikipedia.org/wiki/Sysex for more details. | System-specific MIDI messages that can be used to access deeper system functionality than the standard general MIDI specification allows. Please see http://en.wikipedia.org/wiki/Sysex for more details. | ||
| − | The Axe-Fx makes extensive use of SysEx messages. Indeed, this is how the Axe-Editor controls your Axe-Fx. There is a user project under way to document the SysEx messages both sent and received by the Axe-Fx. You can find the the results of this project [[ | + | The Axe-Fx makes extensive use of SysEx messages. Indeed, this is how the Axe-Editor controls your Axe-Fx. There is a user project under way to document the SysEx messages both sent and received by the Axe-Fx. You can find the the results of this project [[Axe-Fx SysEx Documentation|here]]. |
| − | For controllers capable of sending SysEx messages to the Axe-Fx please see [[ | + | For controllers capable of sending SysEx messages to the Axe-Fx please see [[SysEx Capable Controllers|this page]]. |
Latest revision as of 15:08, 20 August 2009
SysEx (System Exclusive) Messages
System-specific MIDI messages that can be used to access deeper system functionality than the standard general MIDI specification allows. Please see http://en.wikipedia.org/wiki/Sysex for more details.
The Axe-Fx makes extensive use of SysEx messages. Indeed, this is how the Axe-Editor controls your Axe-Fx. There is a user project under way to document the SysEx messages both sent and received by the Axe-Fx. You can find the the results of this project here.
For controllers capable of sending SysEx messages to the Axe-Fx please see this page.
