Cubase Quick Controls or MIDI Control assignments

[LeVzi]

I got given a MIDI controller for Xmas with 4 assignable knobs, yet when I try to assign them to a parameter in a VST , I simply cannot get it to stick

Im using Cubase 11 Pro, and well, it's baffling me.

I've assigned the knobs in the QC Track and VST options in the setup menu, there are only 4 so I did the first four to the correct CC number.

Trying to assign the QC parameters just won't work. Take Sylenth for example, I want to assign slot one to the Filter Cutoff, but when I try to assign it, it defaults to a set parameter, which is the attack in the ADSR.

What am I missing here ?

[pixel85]

Both are hot mess! It's simply that bad.
Just wait for C12 with hopefully a new rewritten MIDI implementation (which they're working on).

[LeVzi]

Both are hot mess! It's simply that bad.
Just wait for C12 with hopefully a new rewritten MIDI implementation (which they're working on).

It is a mess, but I finally worked it out. Why on earth is it that strange to assign midi controls to parameters ? Midi learn would be easier.

[jancivil]

I've only experienced a problem with assigning MIDI control in Cubase after I'd bought a device that was supposed to work using (alternately) Mackie universal or Generic controls, and it simply did not (Korg Nano-something, Korg ackknowledged a problem with Mac OS but seemed to not care in the least to address it). I use fairly extensive control, Quick or VST Controls have never been it for me. I do it in the piano roll, it just works, with that kind of caveat, a physical controller designed in that way. IME those two are not very well-thought-through to begin with, and it seems like 1996 or something to look at. It would suck to actually need it.

[pixel85]

Both are hot mess! It's simply that bad.
Just wait for C12 with hopefully a new rewritten MIDI implementation (which they're working on).

It is a mess, but I finally worked it out. Why on earth is it that strange to assign midi controls to parameters ? Midi learn would be easier.

It seems that everyone else can make midi learn and use other features of VST. Cubase has the weakest VST implementation for midi controllers, even though Steinberg created VST. I will never stop wondering how they manage to do it.
I hope that their rewritten midi system will allow for midi learn for all effects and instruments, like for example Ableton Live does.

[chk071]

Both are hot mess! It's simply that bad.
Just wait for C12 with hopefully a new rewritten MIDI implementation (which they're working on).

Really? That's good news, because, yeah, MIDI control is really shitty in Cubase.

Not that it's any better in other DAW's... It's just that Cubase has 4 ways of shitty, while others only have 1 way of shitty. I exclusively use MIDI learn in VST's, or Komplete Kontrol for that reason.

[jancivil]

I should be clearer. Except where something doesn't automatically work (I doubt I'm going to find anything I have that just doesn't) to learn either QC's assignation or the learn in the plugin, or when I actually did need it, when a hardware device doesn't learn itself (or CC from Cubase any kind of way) and needed to be a remote device. It's that aspect, remote device I find majorly deprecatable, unless everybody is still using a Mackie Universal Control as their go-to MIDI device and I think basically no one is.

Here, I was curious about this as a phenomenon as I was always baffled (why is it there) so I want an objective test of how this is. I never actually did.
I found something to load I know nothing about I can't see in the UI. Apparently a synth. It does not learn by right-click in VE Pro. It is not likely to behave different in Cubase, and this is what's set up. VE Pro's MIDI tab's learn sorts it. Cubase 11.0.41 QC sorts it, both instantly. I would actually need one of these for this (I never do) because the parameters in the plugin do not learn as things learn, my MO is learn and now change the controller value while in Key Editor.

The thing is limited as to doing 8, I guess in a project so it's strangely old in that way. I never had a sitution that was 'Ok I need Quick Control'.
BTW I'm down with the hate of the interface in Setup. That alone is definitely just re-do it.
Cubase is as good an MPE interface as yer gonna get, this basic MIDI problem is hard to relate to, I do so much with so little care. If I have stuff that's too much a PITA I tend to discard.

[pixel85]

After over w decade of using Cubase, I still don't know if it's possible to assign controller to effect plugins, in a normal, civilized way. If there's a way which involves skills like advanced c++ and black belt in karate, then I don't even wanna know

[jancivil]

Yep, that *really* isn't easy. Fortunately I don't need to generally. It's rather easy in VE Pro, BUT an effect has to be in an instrument channel to receive MIDI.
For most things I use Host Automation. CC, pitch bend, aftertouch, MPE slide and lift and now with SINE player I'm putting a CC7 lane in Key Editor because that's their MO (there's no host automation for the main instrument level) but for mixing I use Host Automation.

the synth I forget I'd installed is interesting, Nettle. It scans wavetables and uses velocity as a controller.

[xbitz]

not track but VST quick ... at the end I've started to use BCPatchwork/Zenith combo, in Zenith any number of control can be created and assigned to CC values, also dropping the creative effects into Patchwork


hell yeah but better than nothing at least Patchwork able to reopen the previously opened plugins in it and doesn't steal the focus from the host (space key/shortkeys is/are passed to Cubase even from plugin windows) otherwise I would be pretty sad

ps. Zenith has rent-to-own construction on splice, https://splice.com/plugins/38786250-zen ... y-audiaire 5$ per month

[pixel85]

So 3rd party solutions for something that is easy in other DAWs. Which also are not free. Oh Steinberg, Steinberg

It reminds me times around 2000's when FruityLoops had automations like we know them today, and Cubase had only MIDI CC but not for virtual instruments. I think that it was SX1 that had automations for vst for the first time? It's funny how sometimes small devs can beat big players in their own game


I'm staying with drawing automations with mouse Fortunately, recently I don't have to make any crazy automations (I only do it on synths and those I record to audio directly), so it's easy and fast.

[xbitz]

^^^ Infiltrator was a godsend plugin for Cubase users from this point of view

from 7:10 or

many/most of the crazy modulation kinds of stuff/idea can be solved with it (the rest can be solved with(in) instruments) mixing part, well: FabPlugins also have their own modulation system so only the macros of them need MIDI CC/quick control/automation/etc. assigning (as it can be seen on preset demo part of the video above)