Yes but it is undocumented and rather complicated/confusing…But I’ll try to explain the basics. Feel free to ask other questions.
In the top window you can create entries (“new” command on the right). Be shure to give them an uniqe name, and export (=save to a file) your changes before you restart cubase. If you don’t the next time you start cubase all your entries are gone.…
Now suppose you have 8 faders and 8 buttons you would like to experiment with. I would create 16 entries, call them fader 1-8 and button 1-8. Now you can use the “learn” function to automaticly assign the fader/button to the entry of your choice. Actualy the same as it workd in reason I think.
Now comes the boring bit: For every parameter you want to connect to someting in cubase you have to go down to the bottom row, select the apropriate command in cubase, and apply AND export your generic remote settings to keep them next time you start cubase. If you rename, move or delete the file outside of cubase you will have to re-import the file: cubase remembers and looks up the file by name/location everyime it restarts.
So this does not work like in reason, you have to do this manualy everytime you want to connect something different/new. Not very flexible indeed. The use of “Quickcommands” (manual:page 337 Track Quick Controls) might work for you, but I believe this way of working has it’s own problems.
Note that there is one very usefulll type of entry called “selected”, (in the second row I think), “Vstmixer” (or “mixer”, I never noticed any difference), and then “selected”, and then any parameter, for example “volume”.
This wil control the volume of the selected channel. (device>>selected>> volume).
But you have to assign every parameter yourself here, so no learn function like in Reason. Only for the top row. Pitty…
I’ve attached an example pic here:
https://dl.dropbox.com/u/20606376/Cubase%20generic%20remote%20example.JPG
You can control a lot of things in cubase, but some commands do not work as they should. The mixer window for example is a toggeled window, (not 0= off, 127= on, but everytime you touch the state changes) so you will never be able to make a button or a script that reflects the state of the mixer.
One way to expand your controls might be the use of mixer maps, in my pic the first “mixermap” is called “VST 1-16”.
You can rename and create as many maps as you like (I think), and by this you would be able to make differerent commands to the same buttons on your keybord in every map. (for example map 1: fader 1-8 = volume 1-8, map2: fader 1-8 = volume 9-16, and so on.
Now if you would resreve two buttons for “map up and down switching” (be shure to assing these buttons in every map), “command>>remote”>> and then bank increment and /or decrement, you would be able to switch banks by this buttons.
Note that some functions can be found in multiple categories, for example in “transport” you can only assign “stop” and “start” buttons, but in the “command” section you can find the “start-stop” button (why??). It is messy, undocumented, outdated, and it looks like they never realy finished it. But most of it works, if you spend some time to find out how.
Hope this helps, have fun,
Jurgen
