# Multiple CC remap

**URL:** <https://community.blokas.io/t/multiple-cc-remap/4561>\
**Category:** Support\
**Created:** [June 24, 2023, 6:04pm UTC](https://community.blokas.io/t/multiple-cc-remap/4561 "2023-06-24T18:04:33Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ryan\_farris](https://community.blokas.io/user_avatar/community.blokas.io/ryan_farris/32/3835_2.png) [@Ryan\_farris](https://community.blokas.io/u/Ryan_farris)\
**Post date:** [June 24, 2023, 6:04pm UTC](https://community.blokas.io/t/multiple-cc-remap/4561/1 "2023-06-24T18:04:33Z")

</div>

Hi all.  
I’m trying to get around a ‘limitation’ on my Midi  
Fighter Twister. Each knob—which you can assign CC’s to, has a secondary function in which you can depress the knob while turning to send another CC. The problem I’m running into is that it can only duplicate the initial CC on a set midi channel—5 in this case. Remapping the channel is easy enough. I’m hoping to be able to assign different CCs on multiple ‘pressed’ knobs. In the CC remap, it seems to be setup to only do one CC at a time. This would necessitate me using upwards of 16 pipes to accomplish my goal.  
Is there an easier way that I’m missing?  
Perhaps I should feature request a pipe that could have multiple instances of remap?

Thanks  
Ry

---

<div class="post-metadata">

**Author:** ![resonotter](https://community.blokas.io/user_avatar/community.blokas.io/resonotter/32/6354_2.png) [@resonotter](https://community.blokas.io/u/resonotter)\
**Post date:** [June 24, 2023, 10:14pm UTC](https://community.blokas.io/t/multiple-cc-remap/4561/2 "2023-06-24T22:14:02Z")

</div>

> [@Ryan\_farris](#):
>
> In the CC remap, it seems to be setup to only do one CC at a time.

CC remap deals with multiple CCs with linear transformations for e.g. [0, 1, 2, 3] → [35, 30, 25, 20]

(The bigger issue with multiple use of CC Remap is often that each instance requires its own _pipeline_ as it discards CC ids outside its input range)†  
  
  
Jot down your mapping list

- d0 → r0
- d1 → r1
- etc…  
…it may be possible to use a CCRemap for several in one go (alongside careful use of CCRangeFilter)

* * *

† if savings can’t be made, it’s better to use Transform so that several can take place in the same pipeline

---

<div class="post-metadata">

**Author:** ![JoeyButters](https://community.blokas.io/letter_avatar_proxy/v4/letter/j/8baadc/32.png) [@JoeyButters](https://community.blokas.io/u/JoeyButters)\
**Post date:** [June 25, 2023, 12:57am UTC](https://community.blokas.io/t/multiple-cc-remap/4561/3 "2023-06-25T00:57:06Z")

</div>

16 transforms is really the better option. I don’t see any reason to make it more complicated than that unless for some reason you really really need free pipes. Transform lets you remap any CC to any CC and not be stuck with batch remapping in increments of one.

---

<div class="post-metadata">

**Author:** ![Ryan\_farris](https://community.blokas.io/user_avatar/community.blokas.io/ryan_farris/32/3835_2.png) [@Ryan\_farris](https://community.blokas.io/u/Ryan_farris)\
**Post date:** [June 25, 2023, 1:46am UTC](https://community.blokas.io/t/multiple-cc-remap/4561/4 "2023-06-25T01:46:06Z")

</div>

Thanks for the input.  
I’ll put a feature request in. It’s seems totally doable to have a list of CC transformations in one pipe, ie when cc42 midi ch 5 shows up, transform to cc44 on midi 14, ALSO when cc43 ch 5 shows up transform cc45 ch 14 etc etc  
I think remember midi solutions event processor being able to have a list style of transforms setup in line.  
I’m curious if there is a limitation on number of pipes or pipelines or at the least a processing load as more build up? I don’t recall reading that info.  
Thanks again.

Rye

---

<div class="post-metadata">

**Author:** ![JoeyButters](https://community.blokas.io/letter_avatar_proxy/v4/letter/j/8baadc/32.png) [@JoeyButters](https://community.blokas.io/u/JoeyButters)\
**Post date:** [June 25, 2023, 3:45am UTC](https://community.blokas.io/t/multiple-cc-remap/4561/5 "2023-06-25T03:45:14Z")

</div>

255 pipes total.

---

<div class="post-metadata">

**Author:** ![resonotter](https://community.blokas.io/user_avatar/community.blokas.io/resonotter/32/6354_2.png) [@resonotter](https://community.blokas.io/u/resonotter)\
**Post date:** [June 25, 2023, 4:11am UTC](https://community.blokas.io/t/multiple-cc-remap/4561/6 "2023-06-25T04:11:26Z")

</div>

> [@Ryan\_farris](#):
>
> I’m curious if there is a limitation on number of pipes or pipelines or at the least a processing load as more build up?

bottom left of the Editor window:  
 ![Screen Shot 2023-06-25 at 04.30.09](https://community.blokas.io/uploads/default/original/2X/0/0cc6777af5e959e299ce5c67ea5f03d31dd36a1f.jpeg)

don’t know about pipeline limit.  
mappings: I think Giedrius mentioned 511/512  
  
~

> seems totally doable to have a list of CC transformations in one pipe

maybe doable but feels contrary to Midihub approach/philosophy/style of unitary building blocks that do one thing. (Just my opinion, though)

The other limitation which _ **would** _ come into play is the current patch structure:

- each pipe uses just 11 bytes.
- Given that Byte0 is “PipeType”&“isBypassed”, that leaves 10 to cover all the other properties of a given type.
- So, I’d estimate a _max_ of three cc pairs possible;  
and that’s _without_ considering other states like Transform’s `Mode` plus `In/Active` for each pairing! These and others (`Any Channel In`?) might bring it down to just two…

* * *

btw, Feel free to post your initial patch / CC mapping list; there might be the odd optimisation trick that could be brought into play.  
Sometimes it’s neat to find pipe-saving sub-patterns…  
…but, given the 255 max, rarely necessary!

---

<div class="post-metadata">

**Author:** ![Ryan\_farris](https://community.blokas.io/user_avatar/community.blokas.io/ryan_farris/32/3835_2.png) [@Ryan\_farris](https://community.blokas.io/u/Ryan_farris)\
**Post date:** [June 26, 2023, 1:46am UTC](https://community.blokas.io/t/multiple-cc-remap/4561/7 "2023-06-26T01:46:25Z")

</div>

Will certainly post it.  
Currently brainstorming layout of the controller and assigning the correct CC’s for the synth.

Such a great box they’ve come up with.  
I think to my past midi implements and this is just a giant leap forward for non computer setups.

R
