Hmmm....it looks like a combination of key-switches and chord pads.
Can TouchOSC only send one event per pad? I"ve never tried the app, but if it can send a 'series of events' that could make your life much easier. If so, then stack the events in TouchOSC directly.
I can imagine a few ways to get similar effects directly in CuBase....without such a control pad; however it would not be so great for 'real-time' live playing. For step-entry composing however, have a look at 'expression maps'
. It might even be possible to set up combinations of generic remote map
, logic editors, and macros to drop articulations at the cursor position for step-entry into the Key-Editor or Score editor. Again, this would be more for step-entry composition, and would not work so well for 'live/real time playing'. Example: I have used a Generic Remote map so I can drive step entry in the Key Editor using MPC pads on my AKAI MPK261. I tap an MPC pad to set the type of note I want to enter, then tap a key, rinse, wash, repeat. I can step enter an entire part and never touch my computer qwerty keyboard (except to go back and drop in articulations/dynamics that I have not mapped a remote control for). "Translating" dynamic and articulation markings into 'MIDI events' is done through the 'expression map' system.
If these are a series of events you really need to send in real-time while playing, and if TouchOSC can only send 'one event per pad' at a time, then it might be worth while to rethink the patch choices in your plugin. I.E. Can you opt for putting single articulations on unique MIDI channels instead of using 'key-switches'? If that is possible with your plugin, then just set tracks to output 'any', drop in a channel filter for each track's 'local' transformer, and do channel bounces from your main MIDI controller when changing sounds. Again, you could also set up trigger remotes to change channels, or arm/disarm entire tracks with a generic remote map.
One can also set up an organ stop type of configuration using a generic remote map that would use your controller pads to arm/disarm individual tracks that have your articulations preloaded. Example: I have a live setup where I can load a single pipe organ rank per MIDI channel. I can toggle MPC pads to open/close each channel/stop (arm/disarm the track for live recording). With my organ/stop setup, I can easily do stop changes in real time while recording.
Under what I call the 'organ stop' approach, each articulation gets his very own track in the project during 'recording'. Of course I can mix and merge down to fewer tracks at it suits me in later stages of the project....but it's an easy and effective way to make CuBase function as a live console for hopping about among, or layering many plugins/channels while recording in real time. So, by using stacked maps, and loopMIDI, I can make single MPC pads arm/disarm 'groups' of tracks with a single push. I can record and play back my entire automation process to/from a MIDI track if desired.
It's also worth mentioning that while a single Remote Map cannot do multiple things with a single event, you CAN stack several maps and force a single event to send several DAW commands at once. You can also launch macros and logical editors. You can also use virtual loop-back ports to record and play-back all remote map movements on a standard MIDI track.
If you have an advanced Plugin like HALion 6, Kontakt, etc....then you can build your 'chording' system into the instrument itself. At that point all you need are 'single events' coming over the proper MIDI channel to trigger them.
It has been a long time since I have made panels for it, but it's worth knowing that CuBase has a pretty robust set of device panel
tools that were designed for classic MIDI gear. It's possible to make some pretty advanced stuff that can accept SYSEX, N/RPN data, etc...and do advanced things with it on the fly. You might find it useful, since it might be possible to adapt it for other uses.
Finally, if you really need to do alot of advanced real time MIDI transformations and send complex 'sequences' of events using a single key/button, real time key-switches, etc, then it might be worth the bother to check out Bome and/or Bidule (links provided in an earlier post). Either of these apps can help you create intense personalized work-flows, and otherwise force square pegs into round holes (milk various features out of almost any DAW that might not exist internally). Bome is great for creating chains of events and sending them via single MIDI event, or using your qwerty keyboard. Bidule is an whole host inside a host, with full OSC, VSTmeta, and MIDI CC/N-RPN automation support and a whole lot more.