I finally did a sample sysex test I have wanted to try for a while. (See below.) I am wondering if others have tried anything like this and what the practical possibilities and limitations are. Aaron, if you have any insights to share, I'd be interested to hear them. I am also wondering (for example) if embedded sysex commands degrade the performance of OS2.0, and other questions of memory/performance integrity, possible pitfalls, possible usages--esp. which push the gear beyond what is already capable with CC and patchcord controls, etc. I. Embedding sysex commands in an e-mu sequencer pattern. (1) Using a software sequencer, create a pattern with sysex commands. (2) Save the pattern as a standard midi file. (3) Using e-loader, download the pattern into the e-mu sequencer. II. Test # 1: ROM instrument change in preset edit buffer. --embedded sysex commands (single parameter edit) change ROM instruments in a single preset as part of the pattern III. Thoughts on possible applications: --Changing the CC # [functionality] of the 16 knobs in different sections of a song [pattern chain] without having to change multisetups. --Changing trigger functionality in different sections of a song. --Changing filter type of a single preset as part of a pattern. --Steve
Message
Pushing the limits of sysex: embedded commands
2005-02-17 by steve_the_composer
Attachments
- No local attachments were found for this message.