hi guys…i have the horrible suspect that the Remote Controller Editor may just be a special “GUI” for the plugin (ie you still have to set up your hardware controller in the Generic Remote setup page), since I don’t see any MIDI IN/OUT option in the Remote Controller Editor (and that should apply also to Houston, Mackie, Avid, etc).
I have to try a bit better, but i fear it’s not what I (we??) had expected: something “a la” Presonus Studio one, ie I map my hardware controller to the Remote Controller Editor knobs/switch and that’s all I have to do to connect the hardware to the software side - everything else is done within the host, I can create a map for any plugin which is automatically connected trough the Remote Controller Editor to my hw controller as I open the GUI…
Really hope to be proven wrong, i have a BCR2000 sitting on a shelf and taking dust…dloaded Cubase 7 installer before upgrading just to peek in the manual, and the new Remote Controller Editor was one of the main reason to jump on the upgrade!
@Helge: it would be nice to add Generic Remote Q&A to the sticky post about common one…
What would that be good for? We already have “MIDI device” panels, that would be redundant then…
What the heck, I somehow feel tricked now. “We listen to you and we delivered”, “supports xyz right out of the box” meaning abc not IN the box can be integrated. “It cant get any easier”… Nobody knows how things are supposed to work, the manual doesn’t help, several PMs to Marcus, EdDoll, JHP etc were ignored…
yes this one is still a mystery working with mackie etc… but why need this with this type of contrioller but the standart one don’t recieve midi message from simple CC ! mystery mystery !!!
And I assume it’s a Mystery even for Marcus, JHP, EdDoll, the manual writers… Nobody/nothing wants or can explain it.
From the advert:
"Remote control this
You asked for it and Cubase 7 delivers! Supporting many hardware remote controllers right out of the box, the all-new Remote Control Editor lets you visually customize the parameter layout of individual effects and instruments on your control surface. It’s as simple as it sounds — just select a hardware knob or button and chose which parameter to control and there you go! Various modes for rotaries and knobs plus the Learn mode make it even easier to assign parameters. Simply reassign the cutoff parameter of your favorite filter effect or synth to whatever rotary you want.
Remote Control Editor supports Avid System 5 MC, Avid Artist Series, Mackie Control, Steinberg Houston, WK-Audio’s ID, Yamaha DM2000 and more right out of the box."
ooof… You MAY be able to import your devices from another version of cubase? Maybe? I have no idea if they are imbedded in the app or just stored in the devices folder.
Ok, well i have no idea what you mean by this. I don’t have C7, I am just posing options. In other cubase upgrade, I have had to copy controllers from the old version’s devices folder to the new version’s devices folder. This is so to have them available in the midi devices setup menu.
Well, that’s exactly the question here: how does it all work? What do you have to setup, connect etc… Which plugin is controlled by which hardware, and when?
The HOW (a hw control controls a automation param) is explained in the manual/videos…
yes & manual just talk about learn from plugin to remote but not remote to controller exept the controller like Mackie nuage or WK which did it automaticaly !
In the Midi Devices there are all the same ones from Cubase 6 however, in the Remote Control Editor there are only 5 options, Standard, Nuage, System 5, Artist and WK and these seem more like control templates than actual input devices. Who knows how you’re supposed to assign a control surface to the editor. It sure would be great if someone at Steiny would respond?
