Hello, I’m hoping to get some clues on how to MIDI control Helix Native in C12. This VST doesn’t have MIDI remote mapping for the individual parameters, just for the quick controls.
I’m using the Qube Audio Mobi One as a controller, and have set up an audio track with Native as an insert, and a MIDI track with the Mobi as the MIDI in, and Native as the MIDI out.
I can set up the quick controls easily enough, but I’m having less luck with setting up parameter-based controls - the Mobi has a lot of encoders and ideally I’d love to be able to control multiple blocks within Helix Native.
I can use MIDI Learn or set the CC manually to map an encoder to a parameter in Native, BUT turning the dial sets the value of the parameter to either 0 or 100%, there is no ‘continuous control’.
Any idea how I can fix this? Is there a hardware, Cubase or Native setting somewhere that I need to change? When use MIDI learn, I can’t find any settings for the controls similar to the absolute versus Relative Twos Complement setting in MIDI remote - am I missing something?
I’m not entirely sure what you mean by the MIDI Binding in MIDI Remote. This is an example of one of the encoders which I can link to any of the Steinberg effects / VSTs, but not the parameter in HX Native (unless I map them to the quick controls first).
If I select “automation assign”, I can choose to assign it to a knob, which I can then map in turn to a quick control, and it will work perfectly.
The controller has 30 assignable knobs though, and the VST has a vast number of assignable parameters, so I’d like to use more than the 8 quick controls. So I’ve selected “controller assign” instead and mapped to a MIDI CC. The assigned knob then does interact with the parameter - but as above, it sets it to either max value if I turn the knob left, or min value if I turn the knob right.
I can’t understand why the knob is behaving as expected under MIDI Remote mapping, but not when I assign it to a MIDI CC (or use MIDI Learn) - any ideas?
I really thought would work! unfortunately not though… do those mappings only apply to MIDI remote, or to the overall mapping of the unit even when using other means of control?
I have however found a workaroud using Generic Remote. I’ve mapped some of the Helix Native parameters to MIDI CC numbers corresponding to the Mobi outputs (although some are reserved by HX Native eg CC0-4 so creativity is required).
Then I’ve used the generic remote to set up each Mobi dial to send those MIDI CCs to the plug-in, with flags Receive and Relative set.
The only issue arises if I change the parameter setting via mouse rather than the hardware, in which case when using the hardware again, the value jumps back to the last value set by the Mobi. Still it’s usable and if I get it mapped correctly then hopefully I’ll stick to the unit rather than mouse.
Let me know if you think this sounds like the best solution, I would still love to use MIDI Remote but this solution is definitely better than nothing!
Sure - on the Helix Native side, it’s basically the same screenshot as the one in post #9 on this thread, then select a MIDI CC number for the parameter (cc9 and cc11 for the example below).
Then move into Generic Remote, switch on Learn and assign address 9 (and then address 11) to the chosen dials as you move them.
Then change the flags so that Receive and Relative are selected - I also have Pick-up on the first one shown here, I was trying out verious combinations but any combinations including R,R seem to work.
Finally, I changed the control names to match the labels on the unit.
Hi @ggmanestraki , they do turn pretty smoothly. If Helix Native mapped to MIDI Remote I think this would have been a very short thread… the Generic Remote workaround is less satisfying and harder work but will I hope keep me going until (hopefully) an upgrade somewhere in the chain fixes things properly.