The New MIDI Remote is

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.


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.


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.

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

1 Like

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 (2.8 KB)

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:


Family issues haha

Why a decoupling layer at all?

Lua would have been preferable if performance is the concern, but if you look at Logic, which also uses JavaScript, where is the decoupling layer there?

Something doesn’t make sense here. We are not working with all of the information. It isn’t clear what Steinberg is trying to do when they seem to intentionally set limitations. It can’t possibly be a lack of skill. It isn’t a lack of understanding what they are competing with. So there has to be some reason. I just want to understand what that is.

It is, I converted my generic remote with transport controls. The only issue is that it is a key command, so without writing a script and just using the UI, the result will be that there is no feedback to the device for lighting the button.

But then there wasn’t in the Generic Remote either.

Also be aware that the Track Controls such as monitor, mute, solo, record, write, read. Any of the buttons on a channel strip for the selected track will NOT work for MIDI tracks. For those you will also have to use the “edit” key commands, and therefore also have no feedback to the button on the device.

Was that intended to have more than one page?
When I move the JSON from one computer to another it doesn’t seem to bring along more than the UI setup and the bindings for the default page.

… but in the Generic Remote I could make a different output mapping from the input mapping, so I could get the LED to behave properly.

Very cool. I tried that and it didn’t work no mater which way I configured the device or the GR. So, until they fix this, use the GR the same way, only just for the output? Or write a JavaScript .

Interestingly enough @Jochen_Trappe implied in another thread, that it should be possible to make a StartStop, …

EDIT / Correction: And YES it works!!

p.s. This was the old way in the Generic Remote:

In the Generic Remote, I’ve done the following workaround, and it seems to work great:

Of course the first thing I did was to map Transport/Start to see if it worked. It did not!

sigh All of this shouldn’t be this difficult with so many workarounds to do what would be super simple otherwise. I mean, is the audio engine full of this sort of thing?

I was so thrilled with this release at first, but the scripting is a bit of a let down. This should be easy. The Audio part should be hard. But if the easy part is sort of phoned in…

1 Like

Ahh. Sorry. It wasn’t well structured. I made an extra page but removed the bindings on it.

Sloppy of me. I’d like to make a more generally useful script with several pages for different purposes an upload it here. Maybe tonight.

Thank you :wink:
I’ve reported this to Spectrasonics.

The reason I am asking is that I took the JSON from my laptop and put it on the studio computer and only got the first page.

Then I went to

C:\Users\<user>\Documents\Steinberg\Cubase\MIDI Remote\User Settings

And there was one there with a GUID in it’s name and not formatted. When I moved this one over it worked, as it was not missing the other pages.

I just got it to work!

My options are “Momentary”, “Toggle”, and “Trigger” on the device I am using. (Launchpad Mini mk3).
Momentary would be the one I would expect to work.

Ill try it again and see if its. EBKAC

1 Like

Please use the provided Export/Import-Script functionality in the MIDI Remote Manager. Only that way your mappings will be included.