SysEx messages are explicitly handled at the MIDI output bus setup level. See that on View/Buses... just select the target MIDI bus. You can follow this quick hands-on tutorial, if you please. There, you can load .syx files, .mid files and you can write your own sysex stuff by hand, all in glorious hexadecimal notation :)
Please note that all this is about SysEx setup, usually sent out to external equipment upon starting or (re)connecting a session.
Recording SysEx messages, OTOH, is also supported last time I've checked. However, in that case, you'll end up with the blobs interleaved in your MIDI track and stored in plain SMF files (.mid). All SysEx events captured this way will get sent out whenever playback gets into them.
Ah, one other thing for you to keep in mind, is that SysEx messages are not MIDI channel aware, so the only way to record those things is through one MIDI track armed for Omni input mode or default assigned to MIDI channel 1 (one).
SysEx messages are explicitly handled at the MIDI output bus setup level. See that on View/Buses... just select the target MIDI bus. You can follow this quick hands-on tutorial, if you please. There, you can load .syx files, .mid files and you can write your own sysex stuff by hand, all in glorious hexadecimal notation :)
Please note that all this is about SysEx setup, usually sent out to external equipment upon starting or (re)connecting a session.
Recording SysEx messages, OTOH, is also supported last time I've checked. However, in that case, you'll end up with the blobs interleaved in your MIDI track and stored in plain SMF files (.mid). All SysEx events captured this way will get sent out whenever playback gets into them.
Ah, one other thing for you to keep in mind, is that SysEx messages are not MIDI channel aware, so the only way to record those things is through one MIDI track armed for Omni input mode or default assigned to MIDI channel 1 (one).
HTH
Cheers.