Hi there,

Quite new to PD and am I am finding it quite difficult to get the following happen:

On my hardware midi controller I have a momentary button and a rotary encoder. The button sends CC34 on ch11 with value 127 if pushed, 0 when released. The encoder sends CC10 on ch11, with value 0 - 127.

What I want to achieve is when the button is pushed, it modifies the midi channel of the encoder to channel 12. On release of the button, the encoder reverts back to channel 11. CC and value are preserved as is. This will allow the encoder to have two layers. I have gotten this to work in Bome Midi Translator Pro using a global variable for the button state, but was curious if this could be achieved in PD as well?

So far my attempts have been poor. Using Pd 0.49.0 on OSX.
Hope this is asked in the correct subforum, if not please move it.

@silverdrive To change the channel of the encoder, i guess you would have to send some midi command to the hardware controller? If you just want to route the input of the encoder on channel 11 within Pd, this would be easy, but if you want to modify the behavior of the controller itself you would need to know the right command and then send it from Pd.

@silverdrive the [ctlin] objects recieves all cc messgaes from all channels and outputs three floats: value, cc# and channel. There's a multitude of ways to reroute, rescale etc the cc values inside your pd patch. I'd use [pack] and [route] (see screenshot) but I'm sure there are other ways.

@bocanegra Not sure if this matters here, but it is always good to be cautious about the order of inputs. [list prepend] can be used to switch the order of values while preserving the order of inputs

Thank you very much @bocanegra and @ingox.

I successfully managed to get it working. See screenshot below.

Is it possible to simplify it to any extent or is it fine as is? The [ctlout] goes to a virtual midi cable. It would seem that combining the if/else logic at the end, serving only one [ctlout] would be more efficient, from a programming view, but I don't know how to do that.

And the final question. How do I route every other CC on channel 11 that does not match the conditions in route 10 34? I can't use the [ctlin] directly, since it also contains CC 10 34.

I thought about using the last right output of the [route 10 34] and grab the non matching CCs there, and using [unpack f f] and sending it to a new [ctlout]. But that didn't work. It seems that PD got confused as to the order of what todo first and last.

@silverdrive I have no way of testing it, but this could work:

The left one assumes that you don't have to do anything when the button is not pressed, as the controller already sends on channel 11.

The idea is to use the input of the button to directly route the messages to where they should go.

@silverdrive As shown above you can use the arguments of [ctlin] to filter the messages.

Pd doesn't confuse the order of operations, as it strictly obeys to right-to-left order. Only exceptions are [delay] == [del] and [pipe], which break the order of operations.

You can always use [print] everywhere to see what messages arrive at any point.

@ingox Thank you. Your simplified solution worked great.

Now if I could get the other encoders that are not using cc10 and cc34 to go unmodified through to a [ctlout], it would be even more perfect.

@silverdrive I would probably do it this way, if this even makes sense :

@ingox Thank you. I think I have it completed now, fully working.
Appreciate your help figuring this thing out. Here is what it ended up like:

Now if only there was a boolean function to check if a value is in an array of numbers?
Instead of using an expression if statement

@silverdrive Well, there isn't. You can use [list-find] from list-abs extension to check whether a value is in a list. Or instead of using [expr] you can use [select] == [sel] or [route] like in the examples above and build your own logic.

For example, this should work, as beauty lies in the eye of the beholder :