The AAS Multiphonics CV-2 (a Eurorack emulation) comes in two versions, a VSTi and and another as an audio effect. While the instrument version has a MIDI Input section, the effect version does not. It seems the only way Cubase can communicate with the effects version is via Quick Controls.
This post is only about the effects version. I’ve got a patch where I want to be able to manually trigger some portions of the patch on & off. Initially I used a Focus QC which works as expected - turning the knob on my MIDI Remote turns the trigger on when it moves beyond a threshold and off when it drops below the threshold.
Since this is for a specific and not general use I changed from a Focus QC to a the Track’s QC. This also works as expected. The problem is using a knob to change the trigger’s state is both inaccurate & cumbersome. What I’d like to do is be able to play a Note on my Keyboard Controller (or play a MIDI Part) and have the Note’s On & Off change the value of the Track’s QC. Anyone have ideas on how to do that?
I may be confused about how MIDI Remote works then.
My impression is that I’d need to create a MIDI Remote Surface for the keyboard after which I could only use it for MIDI Remote stuff and not general purpose MIDI.
Nope. Interestingly there is an open thread just for this, where I’ve replied a while ago:
Long story short, as long as your midi message, be it a note or cc, is not “drawn” in the midi remote, or if it is, it’s not occupied by an assignment, it will pass.
Well, that’s gonna need some cogitation to sus out the implications.
Another concern is right now my FQCs are mapped to a MIDIMix. Wouldn’t I need to get rid of one of those in order to use a Note? Or is that something that can be easily changed on the fly?
Basically I bumbled through setting up the MIDIMix & that was it. Also I don’t like the GUI - it feels too compartmentalized & hard to find stuff you know exists. But I suppose you just stick to scripts.
Well that quote is from when I erroneously thought using MIDI Remote would preclude using the Keyboard for other purposes.
I think my description so far has been a bit ambiguous. My goal is to be able to ‘play’ the effect live much like you would a VSTi and capture that performance into a MIDI Part so it can be copied, moved, edited etc.
It seems so, but actually the majority of the remotes I use are based on the assistant I scripted for devices with displays, where I liked to send feedback, and then for my core controllers, for using “shift” type of states and dual functionality of knobs.
Yes, I guess a time to adapt is needed, but everything needs some time., isn’t it?
Not until a few hours ago. Been away from my studio a bit.
For example, right now I’m stuck trying to change the MIDI IN port which I’d initially set wrong. I know there’s a page that lets me do that. I’d seen & used it just an hour before But I can’t find it again. I even asked Copilot, which suggested using an apparently non-existent button.
Ouch. As far as I know, there’s not an option to change the midi ports (and the name of the device) directly from the UI. One has to edit the json file of the MIDI remote surface, and remove the midi port names (by setting them to blank). Then upon restarting Cubase, we can re-add the surface and we’ll be asked again for the ports.
In the json file, we have to set the “FilterValue” keys’ values to empty (“”) for the “members” object of the objects with “type” set to “DetectionInputNameFilterEquals” and “DetectionOutputNameFilterEquals”.
Here’s the place we need to edit:
Unfortunate and a pain I guess. But I’m glad I’ve beaten the copilot. Wondering, if you feed it with this info, will it get it right next time? I think so
Good to know, at least now I can stop looking for it.
In that case I think the easiest is to just delete & start over. Normally I’d have done that already, but I really wanted to learn my way around the GUI.
I’m starting to think the devs modeled the MIDI Remote interface on the Darien Gap.
A few minutes ago I would have agreed. But the response included 3 forum links in its “Learn more” section. Each of those threads was about how you can’t change it once it is set except for editing the scripts. So it didn’t seem to understand its own references.
I scripted for devices with displays, where I liked to send feedback, and then for my core controllers, for using “shift” type of states and dual functionality of knobs.
