Quote:
Originally Posted by Banned
Yeah, using a CC for a modifier switch is probably easiest, at least as a starting point to wrap your head around using Pd.
I made another simple patch to demonstrate the basic concept, deliberately keeping things simple (I made it from scratch in just a few minutes): it takes one CC# (default = CC#17, editable) and applies an offset to the CC# number (default = 24, configurable) when the modifier CC#'s value is above some threshold (default = 63, also editable). So, for example, if you would find zero vs. non-zero more comfortable for a threshold value, replace 63 in the [63( message to [1(.
NB: it works on all MIDI channels (to keep things simple). But since you are only using 24 CC# knobs, that should not be a problem, I hope? Let me know if this works for you; hopefully you get inspired to build something that suits your preferred workflow even better that what you already have.
|
alright that works (I tweaked ita lot to figure what does what, still have empty spots but it makes sense more and more) thanks!
now the new issue that arose is that all of this affects my midi keys on the same controller (it's a keyboard/controller by Arturia (minilab))
So yeah midi keys don't get thru Pure data to loopbe that i'm using which goes to Reaper.
Same with program changes. They don't go thru. Plus an issue i have is I use different program changes for things like mute and solo because these are momentary switches that actually send a single param, which reaper uses for toggling mute and solo. With CC momentary I figured it sends an on state and then when I release it sends an off state so if I dont want my pad to be lit all the time (especially because I use this pad to mute selected tracks, it doesnt only reflect a single track state so I better not see the state at all on my controller)
So long question short: how would I do the following
1. send midi keys thru unaffected
2. affect program changes the same way as CCs