Make a inline series of Transform pipes to do this. Sometimes it’s convenient to have the first Transform pipe to convert the original event to a completely unrelated event type like Aftertouch, as you’re converting PC to another PC as well as some other message, for it to not interfere in the process it’s easiest to use an unrelated event as the temporary information carrier.
So I’d suggest doing something like this:
[FROM A] → [Transform PC 1 to Aftertouch Note 1 by Replacing] → [Transform AT#1 to CC #32 1 Inserting Before] → [Transform AT#1 to PC 11 Inserting Before] → [Transform AT#1 to PC 11 Inserting Before] → [Transform AT#1 to CC# 115 1 by Replacing] → [TO A]
@andrismattson your filter is blocking PC messages from leaving.
Drag the filter to beginning of the pipeline and change it so that it only lets PC messages in.
I haven’t had time to test it but line 1 looks OK
If you’re still having problems upload Monitor screenshots (if you show the pipe selected like in my recent examples to you, it helps the community see exactly what’s going on)
PS. I’ve moved your topics over to Midihub:Support so you can mark as Solved when appropriate
…and puts all the PC-specific CC#115 values in a 2nd line
(it could be all one pipeline, but this feels more organised)
It uses Note On instead of Poly Aftertouch just because that allows us to use Note Range Filter to discard the PC# numbers the pipeline is not meant for
I’ve attached the pipeline i’m using with your first solution (the second one didn’t work on my end)
With this first one, pipeling 1 (PC 1 conversion) worked as intended. The rest showed no activity at all when i hit the corresponding midi buttons. What am I missing here? pc conversion still not working.mhp (577 Bytes)
If it is helpful, here is the pipeline that is working for me. these are the messages that are being sent successfully (assuming that I have manually switched to the correct Bank and Preset on my pedal - Bank 1 Preset 6)
All I am seeking is a way to replicate this pipeline in a way that also includes initial messages that tell the pedal which Bank and Preset need to be selected before the subsequent CC message is sent. This way i don’t have to manually switch to that preset.
Yes, the pedal is expecting Channel 8, and the values are correct.
I’m wondering if this might be an issue with how the pedal interprets the data.
When I switch to Bank 1, Preset 6, the CC messages (CC #115 with values 0–9) function as sub-presets within that single preset (6). Because of this, i wonder if it may not be possible to directly switch to Preset 6, Sub-Preset 2 (i.e., CC #115 = 1) from a different preset.
but then when i change the CC#115 value on this line to Value 9 (aka subpreset 9)
It doesn’t want to jump to that one. I execute the action and it still just brings me to Bank 1 Preset 6 Subpreset 1 Single line.mhp (337 Bytes)
It seems incapable of getting to Bank 1 Preset 6 subpreset 9 in one step