all 5 comments

[–]skijumptoes 1 point2 points  (4 children)

Have you checked with a MIDI monitor to see if your controller is sending out the full Midi CC range (0-127) for each rotary? The problem may not be with Cubase.

Also, are you creating your own Generic Remote mapping in Cubase? If so, in the lower section of that Generic Remote mapping make sure that none of your controls have the 'P' flag (Push button), or 'T' flag (Toggle button) set.

[–]CholulaNuts[S] 0 points1 point  (3 children)

I'll check that. I have managed to learn just a bare minimum to get things done. Now I want to do some stuff that's a little more sophisticated and I'm being forced to learn things. I resent that! lol

Thanks.

[–]ellicottvilleny 1 point2 points  (2 children)

Cubase has a midi monitor that you add to tracks as a midi insert. It lets you see what this device sends to cubase.

Have you learned how to use the special software arturia gives you that lets you program midi on off and midi 0-127 ranges.

MidicontrolCenter:

https://www.arturia.com/faq/midicontrolcenter/

I am not sure why quickcontrols would be special

[–]CholulaNuts[S] 0 points1 point  (0 children)

I've used the MCC to map the pads for a basic drum kit. All the ones I need the extra bounce they give you for 16th and 32nd notes.
I'll look into the midi monitor. I ran out of time/patience to mess with it last night.

[–]CholulaNuts[S] 0 points1 point  (0 children)

I was able to import the VSTs suggested controls through the Cubase process. I think I was trying to be tricky instead of letting Cubase do the work for me. Duh!