Excellent!!!!!! Kudos to atom for posing the question, Aaron for providing (as usual) the needed tips, and both for advancing the OS2.0 sysex knowledge base in this forum. --Steve --- In xl7@yahoogroups.com, Atom Smasher <atom@...> wrote: > > cool... > > this works to select a new pattern: > F0 18 0F id 55 01 08 // sysex header, command, count > 07 21 pp bb // choose next pattern > 04 21 pp bb // confirm next pattern > 7F F7 // checksum, EOX > > this works to select a new pattern with "mute hold": > F0 18 0F id 55 01 10 // sysex header, command, count > 07 21 pp bb // choose next pattern > 79 20 01 00 // "tap" press > 04 21 pp bb // confirm next pattern > 79 20 00 00 // "tap" release > 7F F7 // checksum, EOX > > id = system id > pp = pattern > bb = bank > > based on my understanding of the sysex docs, this works in > abbreviated form (all within a single sysex message) only because > all of the "commands" are 0x01 (parameter value edit). > for anyone experimenting with this, pay attention to the last > byte-pair on the first lines (0x08 & 0x10) which are counters, > telling the command station how many byte-pairs of data to expect. > also note that the "7F" checksum means "ignore checksum". > > i do think it's bizarre that the "choose" and "confirm" are two > separate commands, but both require the pattern and bank to be > specified. > > thanks aaron!!! > > > -- > ...atom
Message
Re: Sysex Pattern Change
2008-04-21 by steve_the_composer
Attachments
- No local attachments were found for this message.