MIDI controllers in Cubase 13

[Scouser]

Are there any Cubase 13 users here who could tell me if Maschine Mikro Mk3 is supported in the midi controller drop-down ?

I hear they now support many controllers and even if they don’t it is relatively easy to set up a template, even so I would like to know if it’s there in the drop-down

[The Elf]

It's not provided in the supplied list. But I think you're missing the point...

The point of the new remote system is to be able to create your own definitions - and it's easy.

Essentially you make an image of your control surface using Cubase's preset shapes of knobs, buttons and faders, use 'MIDI learn' to store the MIDI ID of each of those controls, then decide what you want each control to do.

The first time you do it might take 20-30 minutes while you're finding your way - it can be a bit obscure. After that it really takes about 2 or 3 minutes to knock up a new remote.

I'm sure there are plenty of YouTube videos for guidance. Here's one:
https://www.youtube.com/watch?v=Q1ocxUbeXJE

[OneWorld]

It's not provided in the supplied list. But I think you're missing the point...

The point of the new remote system is to be able to create your own definitions - and it's easy.

Essentially you make an image of your control surface using Cubase's preset shapes of knobs, buttons and faders, use 'MIDI learn' to store the MIDI ID of each of those controls, then decide what you want each control to do.

The first time you do it might take 20-30 minutes while you're finding your way - it can be a bit obscure. After that it really takes about 2 or 3 minutes to knock up a new remote.

I'm sure there are plenty of YouTube videos for guidance. Here's one:
https://www.youtube.com/watch?v=Q1ocxUbeXJE

I got a Novation Launchpad for about £30. It has a matrix of 80 pads and a further 16 pads around the edge. I mapped 16 MIDI channels and 24 audio channels and the rest of the pads mapped to commnands and macros I made. It means I can press any pad and instantly leap to whatever channel.

I can't face the thought of mapping them all out again. But that said I do like the look of the MIDI Remote in C13. I suppose I could map 8 each day, rather than one big session. Or is there a script out there then when 2 pads/buttons are created and the numbers increase incrementally, then the user would slect a number of pads/buttons, say 48 and the script would do the rest, eg posit the requisite number of pads/buttons, say an automatic copy and paste and then add the commands too, eg SELECT Audio1, SELECT Audio2....and the script would iterate until it reach 48

[Scouser]

Thanks for your replies. I have purchased the upgrade as it seems creating a remote system is something even I might be able to do !

[The Elf]

Or is there a script out there...

If you're of an OO persuasion you could delve into the raw Javascript file (it looks baffling to me). Maybe a JS editor would let you apply some clever shortcuts.

[OneWorld]

Or is there a script out there...

If you're of an OO persuasion you could delve into the raw Javascript file (it looks baffling to me). Maybe a JS editor would let you apply some clever shortcuts.

It's not that difficult a coding challenge, basic incremental loop, what I don't know would be how to assign a variable to the add track code in the script. Of course it would be relatively easy to find in the script, but hardly worth untangling the code just for a one time event, or maybe not, once done who knows how many times one might use it, come to think of it, if a track, or whatever other repeating function to be added needed accompanying 'parts' such as pan level, sends, track arm etc thenb a one button press would become quite useful. I haven't used the3 Remote Editor yet, but I sort of feel instinctively that a batch run is there anyway, eg, if a button adds a track, with pan, mute, solo, etc then surely a copy and paste is possible which might automatically increment.

I guess I'll find out when I get to using MR, goodness me, look at the time, it's cup of tea time, must dash

[The Elf]

If you have an iPad, then try Avid Control (free) - you can create extremely sophisticated macros in there. I made a macro that adds all my default named mixer view configurations from one button.

Avid Control is one of the best things to ever happen to Cubase - ironic.

Off-topic, but worth mentioning.

[OneWorld]

If you have an iPad, then try Avid Control (free) - you can create extremely sophisticated macros in there. I made a macro that adds all my default named mixer view configurations from one button.

Avid Control is one of the best things to ever happen to Cubase - ironic.

Off-topic, but worth mentioning.

I'm impressed. I currently use 3 controllers, because neither of them, independently, handle all my needs, but Avid Control seems so comprehensive and flexible. Thanks for that.

[sonics]

I can't face the thought of mapping them all out again.

Isn't it an XML file? If so could you not simply code it?
Or a simple macro recorder to capture the process and reduce the button press count significantly?

[The Elf]

I can't face the thought of mapping them all out again.

Isn't it an XML file? If so could you not simply code it?
Or a simple macro recorder to capture the process and reduce the button press count significantly?

The new controller profiles I have seem to come in the form of .js files.

[OneWorld]

I can't face the thought of mapping them all out again.

Isn't it an XML file? If so could you not simply code it?
Or a simple macro recorder to capture the process and reduce the button press count significantly?

The existing/current facility is indeed xml, and that's why I was surprised to find that MIDI Remote had no import option. I haven't checked yet, but what Elf says seems to make sense, the MIDI Remote scripts are .js, hence no import

There exists various converters between js and xml, but to get a comprehensive 1-to-1 mapping is expecting a bit too much, it is probably less time consuming to do the job manually. In fact once done, it would be interesting to compare the completed Javacript to the XML, that would probably give quite considerable insight as to what bit does what.

In fact, once the function to add a single button, that will be assigned to a track in Cubase, in the js is identified, copy and paste the code the requisite number of times (I currently have 48 tracks selectable) eg button number (x) => track number (x) changing the value of (x) accordingly
button 1 => track 1
button 2 => track 2