Cubase12 MIDI Remote vs MIDI cc etc?

[Bartone]

What is the big difference with Cubase12’s MIDI remote if you compare ready made scripts to other DAWS’s midi remote stuffs?
I mean the situation when you don’t need to create your own scripts.

I’ve tried to watch YT videos how this Cubase12 MIDI remote works/why it’s such a big deal. The mapping/making own scripts seems to be easy. But…

I think many DAWs have factory scripts for plenty of MIDI controllers (at least Ableton and Studio 1 have good selection).

But Cubase12 seems only have handful factory scripts (6 factory scripts were listed Mar. 3).

[event2020]

I have no idea why Cubase only has so few scripts but it is kind of a joke really.

The idea of the MIDI Remote is a good one but I have found it does not work correctly with one of the controllers is has a script for.

Over in Steinbergs Cubase forum there are so many bugs and issues being reported and hardly any replies from Steinberg.

Such a shame.

[Bartone]

I also did read from other thread people having plenty of problems with the new version. Maybe that is why there is no demo version available since it would be just too buggy to show anyone:D

[David W]

Maybe that is why there is no demo version available since it would be just too buggy to show anyone:D

Standard Steinberg practice is that the trial version becomes available around four weeks after the release, often at the same time as the first maintenance release.

[rardier]

yes midi remote is a bit buggy, i have create with the editor with 3 pages of mapping for the atom sq, all the mapping (from editor to cubase function) are magically gone, but the editor is still there with all the midi control declared.

[chk071]

What is the big difference with Cubase12’s MIDI remote if you compare ready made scripts to other DAWS’s midi remote stuffs?
I mean the situation when you don’t need to create your own scripts.

It's a big step up when you compare it to Cubase's former Remote Control editor.

[c0nan]

What is the big difference with Cubase12’s MIDI remote if you compare ready made scripts to other DAWS’s midi remote stuffs?
I mean the situation when you don’t need to create your own scripts.

It's a big step up when you compare it to Cubase's former Remote Control editor.

As ancient as it was I really liked the old editor. All this dinosaur stuff being around for 30 years just tends to work
The new one is pretty cool though. It seemed a little unintuitive at first but it's actually quite simple. The only thing that annoys the hell out of me is that you can't control plugins anymore. The insert section of the 'selected channel' is gone. The same for control room. I was able to open an analyzer or switch MetricAB with a button - not working anymore. That is a huge pita. (The old remote is still there though - with a big dsiclaimer stating it's discontinued.)

[chk071]

The only thing that annoys the hell out of me is that you can't control plugins anymore.

Right. That's the reason why I don't use Control Link in Studio One anymore, but the VST's own MIDI assignment system.

I never really got my head around the VST/Track quick control thing in Cubase anyway (and when to use the one or the other), so, I probably wouldn't use the MIDI Remote thing in Cubase either.

[xbitz]

^^^ quick stuffs, Faderport supports them nicely (motorized ways)

without any mapping, never touched the remote controlling in Cubase, "VST/Track quick control thing" no needs mapping etc. using the Mackie Control protocol

I only mapped the faders to focused quicks in MIDI CC mode to be able to see this new feature works in C12 but MIDI CC is not motorized in Faderport so pretty worthless compared to the one above

[rardier]

i like studio one midi mapping more than cubase because you can have custom mapping for each plugin (and you are not restricted to 8qc), what s good with the cubase new one is that you can use more than 1 controller at the same time (but there s a workaround in s1 by creating anaggregate midi device with tools like midi ox), the midi editor is more friendly and the api dev guide script is public

[francium0]

It opens the door for users or vendors to create control scripts for midi remote controls. Much like Ableton Live you can actually develop your own script by Python 3. But Cubase also provide a GUI for development (although I think the GUI should be more limited compared to programming scripts).

[FreshmakerCC]

yes midi remote is a bit buggy, i have create with the editor with 3 pages of mapping for the atom sq, all the mapping (from editor to cubase function) are magically gone, but the editor is still there with all the midi control declared.

I made the same experience, MIDI remote mapping is full of bugs - unusable for me.