2016-05-17 Resolution: This MIDI target requires a real output throttle in MIDI Designer. Coming soon
I'm trying to set up a MIDI Designer layout for use with my Elektron Octatrack. Basically, I want to create an 8x8 grid of pads that will trigger slices of a sample.
The way that the Octatrack implements slice triggering is a little unusual. Rather than use simple MIDI notes per slice, it uses CC messages to set the slice. Then a MIDI note triggers the track.
So if I wanted to select slice 3, I'd send CC17 - value 4. (Note that there are up to 64 slices, selected with 0, 2, 4, 6, etc.) Then I'd send the standard note value (C - 36) to actually trigger it. In my case, all of this happens on channel 11.
I have both of these steps working as separate buttons - that's all set. But when I chain one to the other via supercontrols, I'm running into an issue. The previously selected slice is always triggered before the selected slice is updated. So I'm always playing the last note I played, rather than the new one.
I first tried the setup out using the CC SELECTOR button as the supercontrol with the NOTE TRIGGER as subcontrol, but I've tried both ways and keep running into this same issue. (I do have Supercontrols send own values set.) I'm also running into some weird toggling on and off behavior - what's the correct type of button to use here, momentary? Is there another easier way to implement this? Ultimately I need 64 of these buttons on screen...
Please let me know how I can solve this problem and get the MIDI message order right! It seems like it might be a problem with the sampler itself, but other users have reported getting this to work with software, so it ought to be possible. I appreciate your help!
