The QCs are limited to 8 parameters BUT

[cubic13]

@mlib

@cubic13

A question, though : how does the MIDI Remote definition knows which VSTi is involved ?

It would operate on the selected track.

@cubic13

I guess that we have to create a layout in the RCE for each of our instruments

Correct. Luckily, you only have to do it once for each VSTi.

@cubic13

hoping that the MIDI Remote will recognized each of them…

It does. I’ve been using this setup for close to a year now.

@Nico5

@cubic13

How the RCE knows that the change has been done ?

Each plugin has their own RCE mapping. That’s the whole trick.

So when changing tracks, Cubase will use the RCE mapping applicable to the instrument of that track.

OK. Thanks to you all for the precisions. I’m going to try this ASAP and eventually report back how things have gone.

[Nico5]

On a historical note: When first introduced, the RCE mappings beyond the first 8 were mostly useful only for a few high end (expensive) controllers that were programmed with highly customized extensions a little akin to Mackie controls. Might also have been useful with Mackie controls, but I never got into that ecosystem.

Now with the MIDI Remote, we get to to use that mapping functionality with any MIDI controller.

[estevancarlos]

@Nico5

I would think that alternative plugin UI enthusiasts would quickly reach for 3rd party tools like plugin wrappers or chainers. And that’s because those would generally be a lot easier to create and maintain than the obviously ancient Cubase Device Panels and also would open more creative opportunities

I think the potential presented with the Device Panel extends beyond what the plugin wrappers could do.

Benefits, as I see them:

• The Inspector Device Panel could be faster to view instead of a random VST UI
• No need for a pop-up Window VST interferring with the information on the screen

Additionally, part of the reason I wrote this post is to point out that since the Device Panel provides this feature, Steinberg should update it and fix it to make it easier to use.

[skijumptoes]

@estevancarlos

Additionally, part of the reason I wrote this post is to point out that since the Device Panel provides this feature, Steinberg should update it and fix it to make it easier to use.

I gave up using it years ago because of the lack of updates and quirks with it. It was a great idea back in the day, hand on heart I think they’d be better making the MIDI Remote interface controllable via mouse if that’s what your underlying intention was with the device panels.

The number of ways to map in Cubase is getting out of hand really, they need to unify it all into the new remote. i.e We’ve got quick controls, track quick controls, focused quick controls, RCE, Device panels, Generic Remote etc.

Personally, I much prefer the banked versions of instrument and insert controls as found in the MIDI Remote, and this along with FQC should be the core standard that manufacturers create factory devices too.

In fact, bankable instrument and insert controls i’d prefer if they were one control set where if any instrument exists, it takes slot 1.

My opinion of course!

[estevancarlos]

The number of ways to map in Cubase is getting out of hand really, they need to unify it all into the new remote. i.e We’ve got quick controls, track quick controls, focused quick controls, RCE, Device panels, Generic Remote etc.

Yeah, that’s part of the reason I bring this up. If Device Panels existed before QCs, then why not just fix/improve Device Panels instead? What you describe is strange (but typical for old software).

I agree with you. It should be unified. If anything, the new “remote” features should also be built into the inspector like a Device Panel. Ableton Live is growing their unified remote mapping features with their recent release.

All these features you list are adding to cruft and complexity.

[m.c]

@skijumptoes

i’d prefer if they were one control set where if any instrument exists, it takes slot 1.

This could be of less overhead, I understand that. However, a) the instrument slot and the fx slots in Cubase (not just the Midi Remote) are different entities, and b) based on the current implementation of the insertsViewer object, one can control just one slot each time. In my case, I have some knobs/faders setup to control the instrument, and another set of controls for the inserts slots. So, this wouldn’t fit. That being said, I’m sure that in the future, we can have control of multiple slots at the same time, so this small “objection” would vanish.

[skijumptoes]

@m.c

This could be of less overhead, I understand that. However, a) the instrument slot and the fx slots in Cubase (not just the Midi Remote) are different entities

Just thinking more about this, I guess it could be possible to do as part of the API anyway.

It would only take a detection of whether there’s a valid instrument parameter on the selected track and then present instrument mappings on a pseudo slot 0, which then allows movement to the standard insert slots without requiring a separate mapping page.

I’ll not hijack this thread, instead will quietly move into the shadows and have a play of this idea!

[m.c]

@skijumptoes

I’ll not hijack this thread, instead will quietly move into the shadows and have a play of this idea!

Cool! Yes, it would actually be nice to start a new thread if you face any difficulty on this attempt. In the past I used a snippet for this.

[cubic13]

@cubic13

OK. Thanks to you all for the precisions. I’m going to try this ASAP and eventually report back how things have gone.

@Nico5

…
Now with the MIDI Remote, we get to to use that mapping functionality with any MIDI controller.

@m.c

The RCE is not involved in this process. You can setup using the RCE the parameters as suggested by @Nico5 and it’s all set. Then, whenever you change track, the MIDI Remote will see the change and adapt to the parameters of the plugin in this track.

@mlib

…
The process is not that complicated.

As a side note, RCE mappings are available not only for VSTi’s but VSTfx as well.

I finally found the time to give all this a shot.

First issue : I have this, as available layouts and was expecting, at least, to see the MIDI Remote definiton already defined, in this list. So, what am I doing wrong, as I guess, following our past discussion, that it’s a mandatory stage before going further ? I’m rather lost, I admit : Cubase operation Manual is of no help and the few threads I have seen about the RCE, either.

Second issue : the Learn function doesn’t seem to make a given control react in the RCE, though the hardware controller is detected as expected in the MIDI Remote definition…

I’m about to give up again, already, as the whole thing is as cryptic as can be…

[m.c]

@cubic13

the Learn function

The “Learn” function inside RCE is used this way: We click on a knob in our layout, thus we set it selected. Then we turn whichever knob/button/whatever in the plugin window. Now, the element in our layout should be updated to show the control of the plugin we just turned.

@cubic13

the hardware controller is detected as expected in the MIDI Remote definition

In your screenshot, I see no assignments at all to your knobs and faders, apart from the last two faders which are assigned to two volume elements.

[cubic13]

OK. I got the RCE knobs to react, thanks to the Selected Track > Parameters options. Will continue to look at this further, thanks…