11-09-2024, 08:11 PM
The situation hasn't changed. The way that MRCC modifiers are applied is in series, so there's nothing that can be done without a system wide rewrite of the firmware unfortunately. the only thing I can think of is something like A) swap 0 and any number CC the target synth doesn't care about,(let's call it X) then B) 30 and any number the target synth doesn't care about, (Lets call it Y), then C), X to CC30 D), Y to CC0 and place them strategically so that:
1 for a case that wants CC0 but not 30, you would use B ,
2 if you need CC30 sent to CC0 and don't care about CC0, you would place A>B>C
3 if you need CC30 but not CC0, you would place A, if you wanted them both but swapped you would place A>B>C>D
I'm not 100 percent sure whether this is a solution, but it's as close as we're going to get at the moment, so my apologies if that isn't a optimal solution. I will put a request in for adding an exclusive mode, but it's not going to happen this year for sure.
1 for a case that wants CC0 but not 30, you would use B ,
2 if you need CC30 sent to CC0 and don't care about CC0, you would place A>B>C
3 if you need CC30 but not CC0, you would place A, if you wanted them both but swapped you would place A>B>C>D
I'm not 100 percent sure whether this is a solution, but it's as close as we're going to get at the moment, so my apologies if that isn't a optimal solution. I will put a request in for adding an exclusive mode, but it's not going to happen this year for sure.