In the past I kind of ignored Chord Pads. With the introduction of Pattern Events I want to explore triggering Chords with Patterns, but I’ve got a MIDI Routing problem I can’t sort out. When I click on a Pad the correct chord plays on the top Halion Track - so the playback routing is OK. But when I try to use the MIDI Track (selected below) to trigger the Pads I can’t figure out how to route it there. I expected to see the Chord Pads as a destination, but they are not. I know I’m missing something obvious.
I don’t think the Chord Pads are a valid internal destination in Cubase.
They maybe more akin to the MIDI Remote - sitting between the outside and Cubase.
If that’s the case, a virtual MIDI loopback cable may be a workaround?
EDIT: I think the Chord Pads listen to “All MIDI Inputs”, so the other end of the loopback virtual cable needs to be enabled as such.
EDIT of the EDIT: Thanks to @m.c for pointing out, that there’s a MIDI port setting, that allows a choice of MIDI input port, analogous to MIDI or Instrument tracks.
1 Like
Exactly, since a loopback port acts both as a midi input and output, i.e. echoing the input.
Here’s a midi track (careful here, instead of setting the midi input to all, to switch to a controller of your choice, in order to avoid unwanted feedback) with its output connected to a loopMIDI Port:
So, whenever we trigger something on our “real” controller, this will be sent to this port.
Now, we can proceed with setting up the chord pads, i.e. setting it to listen to this specific port:
And obviously we can then connect the chord pads (because they’re virtual midi input) to Halion for example.
What we achieved is that now the pattern created in our midi track, will properly echo to the loop port which then will trigger the corresponding chords which then will trigger the notes in Halion.
1 Like
Yeah, I thought that might be the answer in the end but figured it made sense to check I wasn’t missing anything.
