I have a torso t1 that I am using to trigger an argon 8. I figured out how to use the torso cc mode and the midi hub to control the desired knobs on the argon. My question is this. Is there a way where the torso is made to know the initial values of the cc inputs on the argon. At the moment when a nob on the torso is used the value of the preset on the argon jumps to the value that the torso was set to. Is there a way to prevent this jump. Can the sequencer know the value state on the synth and when it is made to change that value can it start from that number?
Thank you.
Also. To change each knob I currently set the path: in midi a, cc value change ( example low in 71 low high 71 to low out 16 high out 16) out midi A. Is there a faster way or must I create 14 separate path ways.
Hi, I see from Argon 8’s manual that it does send matching MIDI CCs for every parameter you change. If you provide that input into Midihub, and use CC Table pipe for creating mappings for every parameter from 2 sources (Argon 8 itself and Torso T1), when CC Table’s mode is in Takeover, it should pretty much achieve this. The only cave-at is that upon power on, CC Table won’t know the parameter values, until it’s changed. Some devices have a way to trigger a “CC Dump” that outputs every parameter upon a request (like receiving a particular CC), but I don’t see this implemented for Argon 8. You may ask the manufacturer whether they have it. If they’d add such a feature, it would ideally be triggerable with a simple message (like an otherwise unused CC #, or special dedicated channel or note number out of its playable range) As a workaround, you could twiddle the relevant knobs on the device itself after powering on, so they take over the control.
Here’s a two parameter example on how to go about this:
This is set up to share controls of Distortion (CC #12) and Osc 1 Tune (CC #14). The remaining 6 CC Table slots are in default state, ready for customization.
The main thing for making use of the Takeover mode is to make multiple mappings to the same parameter.
At the moment if you change the preset on the synth and move the knobs, it won’t automatically ‘take control ownership’ away from T1 if it already had it, but I think we should implement a new Mode for CC Table called “1st Mapping Priority” which would allow for the very first mapping to always take ownership of the value which would be ideal for your use case.
