MIDI Pass-through issue (not sure if this is the best way to describe it)

725 viewsCSS Questionsmidi output
0

Here’s my use case:  I’ve repurposed my Korg Kaoss Replay as purely a midi instrument as it was adding noise to my audio signal and I prefer to work non-destructively any how.  I also love it’s drum pads.

The challenge I was trying to fix was being able to dynamically choose which of the drum instruments in the instrument rack using repurposed Kaoss Replay buttons assigned to specific values on the chain selector (as an encoder is so imprecise.)   So I got CSS in order to pass specific parameter values to the Instrument Rack Chain selector.  Still working on getting that working but that’s not the issue here.

By installing the script, CSS has for lack of a better term, hijacked the physical MIDI instrument itself, and it doesn’t even appear in Live or track input selectors.  (Note, I am passing CSS hard values for track selection because I want it to work on the first track which is my drums.)  CSS is then using scripting to change the input device for the track, essentially eliminating the functionality of the instrument itself, in this case the Kaoss Replay’s drum pads.

How can I get this done where I can still actually play the drums I’m trying to automate?  I have a number of applications for CSS on live MIDI tracks and it may not always be the same device intended to play the midi instrument as CSS is routing automation through.

JohnC Answered question
0

If you have pads or other inputs on the unit which you don’t want to be taken over (hijacked) by the script, then  remove them from Controller Template.

JohnC Answered question