Curious as to what is the use case here??
Sorry, hard to explain. Trying to lay things out in an easy-to-digest manner. haha
If you’re at all familiar with the Make Noise Pressure Points module, that would be helpful in this convo.
That module has three rows of cv knobs (values) with three per step. When you touch the next step (with its own threes CV values) it will then output those voltages. So the three CV voltages in this case would be three cc numbers, say 1-3. It would be awesome to be able to hit a note an a midi controller, lets say C1, dial in your cc values (0-127) for cc 1-3 (that are mapped to a controller), then be able to hit the next note, D1, and dial in three new values (using the same cc numbers 1-3). As of now, if I have press C1 on the midi controller, set my cc values (which are mapped to a controller) and then press D1 and adjust for the new wanted cc values, it changes C1’s values since each pipeline isn’t isolated from one another.
I’m using this to ultimately convert cc to cv (out of an Expert Sleepers FH-2).
So in Midi Hub it would look something like this, this is for three messages (CC1-3) on two notes C1 and D1. Because each note uses the same CC messages, when changing the values of one note, that effects the other note since CC messaging is “global” in Midihub. Would be great if it were pipeline specific and isolated from one another. In this scenario a way around this could be a locking function. So once the CC value is dialed in, on one step, you could lock it and then move on.
I attached the preset. The first three are for note C1 and the last three are for D1.
Let me know how I can explain things better.
Nick
Pressure Points Example.mhp (366 Bytes)
Thanks for explanation!
Sometimes by going deeper into ideas, from a request by someone else, give results 
Your preset example… got me again confused; is it incomplete? just a “sketch”?
Sorry about that. haha.
I guess to distill things down to its simplest form; I’m looking to be able to use one CC message, let’s say CC76, in multiple pipelines independent of one another. So when changing the value on one pipeline, the other pipeline values of that same CC76 stay the same.
Make sense?
When would CC76 get actually sent to the output?
USBA (port1) out of midihub into a DAW (Logic Pro) if I want to record those note (message) changes, then out an external midi track to the FH2.
Or I can route USBA (port1) through Bome Midi Translator directly to the FH2 Midi to CV module.
Make sense?
I’m still right (about brainstorming and pushing to get results)
I think using different MIDI channels easy no?
@nmihalevich can you use CC76 coming from different MIDI channels?
1 Like
I can only assign one midi channel per FH-2 output. I’m looking for that same CC message to change values from step to step (C1 to D1) on the same FH2 output.
Here’s an idea:
NotesToSameCC.mhp (154 Bytes)
Map the Argument 2 parameter to the same or different CC knob on some controller, and use C4 and D4 keys to trigger one or the other value.
Is this what you’re after? 
2 Likes
Interesting! This looks intriguing. However, I’m not able to open the file. It consistently crashes MidiHub.
Cool, got things updated, checking out the preset now!
1 Like
Still working through this preset. Discovering a new issue. Midi C3 is being struck on the midi controller and working properly (midi data making its way through port 1to FH2) when MidiHub has C4 defined… I then changed MidiHub to C3 and struck C2 on the controller and it worked as well. So its offset by an octave? I know this is seemingly unrelated but wanted to call it out. Working fine with the offset at the moment.
Eternal discussion over “middle C” is what C3 or C4 or even C5?
1 Like
Ha! I always thought it was a discussion between C1 and C4. Yamaha vs whomever else.
Gotta say, love the ingenuity here! So far using the same CC message (76) isn’t really cutting it since the FH-2 is summing upon arrival. I see how you’re using the ports to potentially keep the same message separate?
With that being said using two CC messages (76/77) is working well. Being sent through two ports (A/B), retaining different values and summing out the same output on the FH2!
I wish I understood the Data Source 1/2 and Argument 1/2 a bit better…
Nick
Wait, forgot the Argument is the CC number.
1 Like
Gotcha!
Well thanks so much for working this idea through with me. This is amazing!
Would still be interested in seeing a parameter locking function per pipeline that sends the set values through for more of a switching mentality between the same CC message in multiple pipelines. That could be super nice for pulling more functionality out of one cc message (on the same channel).
My colleague and I were talking about how if you wanted to use the same control fader to set different values per pipeline, you could just map the cc message make the cc value adjustment on one pipeline, unmap to keep that value intact and the same, then map the same cc controller and same cc message, make the value adjustment on the new pipeline… rinse and repeat for as many pipelines you want to use. Is there a mapping/unmapping function for the map/unmap buttons? LOL
Thanks again, will dig into this work flow and let you know how it goes!
Nick
3 Likes