The New MIDI Remote is

[u-man]

@Jochen_Trappe

On the Arturia-keyboard the problem was that the text display is driven by one single sysex-message. We wanted to show different infos there, so the script needed to “remember” the states that came in via the callbacks.

I still wonder how that is working. For example, Text display on a Mackie is also driven by one single sysex message, but how does the “character” translation work? I assume that every company use different code for characters. How Cubase knows the code to use to create the text/characters?

[skijumptoes]

@Jochen_Trappe

At the moment the way to read track names, colors etc is by using the callbacks mOnTitleChange etc on the API’s HostValues.

Ok thanks for that, so where would you gather the plugin(FQC) parameter value and name if you wanted to translate that to a screen? - are they also in the mOnTitleChange callbacks, too?

Also any method or plans to read the RGB colours from Groove Agent pads?

I really hope you stay active on here for us in this initial stage of understanding… please please please

[Jochen_Trappe]

No worries, I’m here.

[oqion]

@Jochen_Trappe

No worries, I’m here.

@Jochen_Trappe Thank you!

Can you tell me if it is possible to connect more than one device/port to a single script?
Also… would you consider yourself a Psy-Trance artist? Listening to your tracks.

[Jochen_Trappe]

1. No
2. No

[IvanZ]

For now we decided to stick with the Quick Controls as the decoupling layer of choice.
but why only 8 Quick Controls???

[u-man]

Looks like i am alone with my questions. Could talk to a wall, would have the same effect .

[brittleheadritchie]

I agree, Quick Controls is a fairly limited abstraction to use as a decoupling layer.

It also restricts what can be achieved by a hardware controller - I could see some awesome things I could do with my Faderfox EC4 - but because plugins have been abstracted way, there’s no way to even see what’s possible.

I think what is really missing here is a ‘discovery’ type API for VST Plugins and VST Instruments that could make all manner of funky workflows possible. I mean this must be available under the hood in Cubase today, as you can see the plugins describe their parameters in Generic Remote - but it’s limited/tied to the specific track / insert slot. Would be awesome to be able to cycle through every open instance of a plug and control that with a hardware controller in the same fashion

[IvanZ]

In current form The New MIDI Remote is useless. It is less useful then old generic editor. And generic editor is very limited as well. It’s strange because with Quick Controls I can controll 95% of what I want…but only 8 is not enought.

[Trensharo]

Totally agree.

IMO, it’s only useful for supporting really old controllers that don’t have Mackie or HUI Emulation.

If that was the intent, then it was a success… but I am guessing now, since everything else has been deprecated and labeled as Legacy/Slated for Removal in the application GUI.

This update also seemed to break some things on the “legacy” side, as well.

[skijumptoes]

@IvanZ

It’s strange because with Quick Controls I can controll 95% of what I want…but only 8 is not enought.

This is why I put this request in, pages/layers exist within the remote setups so it’s possible to manually change VSTi pages as per my post:-

Enable VSTi layer change to function list

Is it possible we could please have the option to control the quick control layer via the MIDI API? i.e. for instruments you get the first 8 quick control parameters. [image] And if you change the layer to Page 2 (using a mouse) it updates the focus QC to the next 8 of controls, which is brilliant:- [image] However, there’s no option to map that layer change function to a controller, so you have to use a mouse to move between pages. This is the current functions available:- [image] If …

If SB provide the option to change pages via the MIDI Remote then we should have a much more flexible system. What’s frustrating is that it’s already there via mouse wheel, it just needs a MIDI control mechanism. (Which you’d hope is a simple addition).

Ok, so that’s not perfect if you want to assign 16,24,32 controls in a single page - but it’s an advancement to provide us banks of 8.

[IvanZ]

Now, we have generic editor doomed to extinction, New crippled MIDI Remote and 8 Quick Controls. I have 16 buttons/16 knobs midi fighter twister and it perfectly working in Lightroom but it’s almost useless in C12. Pity.

[IvanZ]

It is worrying that it is easier to use midi controller with photo editing software than 600 EUR DAW. Personally I have been married to Cubase since ST but if I were younger…well.

[u-man]

The Remote Control Editor (RCE) does exactly this, but is limited to certain controllers. I use Bome Midi Translator Pro with the Mackie C4. I fool Cubase into thinking it is a Mackie MCU. I can use all the parameters that i setup in the RCE. If there are more then 32 parameters, i just page to the next 32. So I guess it is either a licensing thing why we do not have that or it will maybe come in a future update.

I wished the Midi Remote would be as simple as Bome´s Midi Translator. It would be a relief for every “normal” user.

[Yvan]

@Elias1957

e nice if Steinberg can invest here and give us a result, if Steinberg or the vendors must fix this.

This is due to the plugins vendors. Their plugins report a size of 0 (as width and height) just after creating the UI of the plugin. This leads to resize issue in the plugin header including the attachment of the top right buttons…
You should contact these vendors and inform them about this issue. If they need more info they could contact Steinberg.

[MarcoE]

@Jochen_Trappe

Thank you for deep diving into the API without any fear.
You’ve already reached a topic that shook our heads a lot when designing the API. How to stay “generic” but access custom project setups using 3rd-party plugin etc as well. For now we decided to stick with the Quick Controls as the decoupling layer of choice.

Maybe by having a (solution oriented) discussion about it, we’ll find the right way to stay “generic” and access individual plugin-setups as well.

And could you please explain what bug you encountered in the API?

I can follow your reasoning to do it generic and I agree from a Cubase UI perspective. The new MIDI Remote UI should be generic of course.
I’m out of the generic scope as soon as I write 1 line of code as this code is specific to a controller and specific to an application. I don’t want to write generic scripts as I want to support my very specific workflow and plugins. I hope I can contribute to a solution oriented discussion. I like the concept so far (incl. JavaScript) and it has a lot of potential. I dream of possibilities like the Live Script Engine allows…

I will DM you with the bug report.

Keep on the good work on the new MIDI Remote API.

[Torbjorn_Hedberg]

Just want to report that the Behringer Xtouch mini works REALLY great here. And values reflect immediately on the LED rings around controllers and on buttons.

Super easy. All I miss right now is the ability to adress specific channels, so generic remote got some love for that purpose.

Cheap, small and simple. Couldn’t get any better.

[u-man]

So how about you share your script here? So that others can enjoy this like you do.

[Torbjorn_Hedberg]

Yeah. No problem. Here it is. But I don’t think it’s necessarily very useful for anyone else - it depends a bit on my specific setup.
My Xtouch mini.zip (2.8 KB)

[Nico5]

I’m very excited about the new Midi Remote for the ease of creating mappings. For simple and quick mappings it works great!

So I’m hoping that it will quickly gain at least a couple of additional features to become useful for more ambitious setups:.

All of these have been mentioned previously, so I just want to add my voice to the chorus of requests:

---

Remote Control for VST Quick Control Pages

As several forum posters, including @skijumptoes has requested (I’ve used one of my few forum votes in support as well), the main thing I’m missing in the Quick Controls is to remotely change the pages.

This is a really, really big deal to create a more useful hardware surface for modern instrument plugins and more elaborate fx plugins (for example guitar pedalboard).

While I’ve been able to effectively get to 16 Quick Controls via utilizing the Track Quick Controls in addition to the VST Quick Controls, that doesn’t solve the real issue.

---

Controlling Audio Insert chain

As a few others have already mentioned, the second biggest thing I’m missing in the new Midi Remote is the ability to control the Insert chain via the Selected Track hierarchy.

For 8 insert parameters this can be worked around via using the Track VST Controls, but anything beyond 8 doesn’t seem possible.

So for that use case, I still need the Generic Remote.

---

Mapping a PlayStop button

EDIT / Correction: This does work - I just needed a hint from @Jochen_Trappe in another thread:

Here’s how it worked for me:

No "Start/Stop" in transport options for Midi Remote?

Just got it to work as (@Jochen_Trappe suggested) for my Maschine Jam: The remote controller is set to Gate behavior: [image] And the Cubase Midi Remote is set to Jump and Toggle On [image] Thank you @Jochen_Trappe !!