The New MIDI Remote is

[Nico5]

@Javier_Cerezo

I tried to do with Maschine MK3, but I couln’t to do it. If anyone gets the script, tell me please!

you may be interested in this:

Cubase 12 MIDI Remote with Native Instruments Maschine (Video, HowTo)

[MIDI Remote Masterclass: Cubase 12 + Maschine. The ultimate setup!] Jef Gibbons made an excellent video about setting up his Maschine controller with the new MIDI Remote.

[Javier_Cerezo]

thanks!

[DrPaultje]

Hi All,

In the video Jef is telling at the end that he will post his script on forums.
Does anyone got it anywhere?
Thanks in advance!

[Pauly]

Hi Matthias,
I am trying to get a Midas m32 to control and be controlled by cubase 12. It all seems to work fine (faders, mute buttons, and pan controls) with 2 banks of 16 main faders, however when I setup the console to receive and transmit midi data, the faders all seem to ‘fight’ themselves, and if I (for example) try to move a fader, it forces itself back to where it was and they jitter. Any ideas on how I could make it work? Thanks.
Pauly

[Nico5]

@DrPaultje

In the video Jef is telling at the end that he will post his script on forums.
Does anyone got it anywhere?
Thanks in advance!

Hopefully this is what you were looking for:

Cubase MIDI Remote Templates for NI Maschine - eMXR.com

[Nico5]

@Pauly

… the faders all seem to ‘fight’ themselves, and if I (for example) try to move a fader, it forces itself back to where it was and they jitter.

Yeah - this is a known issue with apparently a solution on the way. This thread has discussed this issue in some depth:

Midi "ghosting/Jitter" Cubase 12 with midi controller encoders (Midi Remote Control)

Not sure if you read this entire thread in detail. – This is a known issue with an already known solution on the way. Specifically my old post, showing that it’s related to the input midi message being echoed back with some latency: Midi "ghosting/Jitter" Cubase 12 with midi controller encoders (Midi Remote Control) - #5 by Nico5 And Jochen already replied, that a solution is on the way, via being able to suppress the echoing: p.s. Yes, because scale will make the target controller respo…

[Pauly]

Hi @Nico5
Thanks for that - I anxiously await the fix as it will be absolutely awsome to use the desk to mix!
Having said that, it appears that the current understanding is that disabling the midi output solves the problem. It sure does (easy to test with the Midas) but of course then the console doesn’t receive the fader positions so it’s a fix that causes other problems.
Hoping I’ve misunderstood that.

Thanks
Pauly

[Nico5]

@Pauly

… but of course then the console doesn’t receive the fader positions so it’s a fix that causes other problems.
Hoping I’ve misunderstood that.

I don’t think you’ve misunderstood.

[Pauly]

HI again,

Hmm (If I Have not misunderstood), the current solution will be to disable output to the console entirely? So… when I open a project, and want to use the console as the controller, the console will not receive fader positions from Cubase and will therefore not be configured correctly. In that state, every time I touch a fader, the matching fader in the Cubase mixer will immediately take up the physical console’s position, and therefore destroy the mix. Also, if I (for example) manually modify fader positions in Cubase (actually, playback …ever!) , then play back the project, the physical faders will not follow what’s in Cubase.
I’m still hoping that I have misunderstood the solution!
Thanks
Pauly

[Nico5]

@Pauly

I’m still hoping that I have misunderstood the solution!

You can hope (I know it springs eternal ) and repeat as many times as you wish, but it’s the only thing currently doable, and it only makes sense for some workflow situations, and absolutely not for many others (like obviously yours – and also mine).

The real solution (hopefully) will be this:

Midi "ghosting/Jitter" Cubase 12 with midi controller encoders (Midi Remote Control)

The first maintenance update will provide a function in the Surface Editor to disable the midi feedback to the hardware. That will hopefully solve it.

[oqion]

@Nico5

The real solution (hopefully) will be this:

I’m not so sure. Yes that would be great as it would stop the feedback loop, and allow devices like Novation and Akai, to set response based colour feedback. But just disabling the automatic Feedback, while still allowing scripted feedback won’t move the faders.

Hopefully the intent of mOnProcessValueChange will be that of what I called mOnHostValueChange

@oqion

[ mOnHostValueChange ] : When the actual value (0 to 1) of the bound value changes and it did not come from the device , this functor is called.

[ mOnEncoderValueChange ] : When the value (0 to 1) of the encoder value sent to Cubase changes and it did not come from Cubase , this functor is called.

[Nico5]

@oqion

I’m not so sure. Yes that would be great as it would stop the feedback loop,

I think you’re convoluting the easy GUI mapping mode and the JavaScript way of doing things?

I was working under the assumption, that this thread was about the former.

And so it’s arguably more comparable to working with the now legacy Generic Remote, which does not echo midi messages back to the sending remote device (while still sending midi messages from changes initiated by Cubase or other remotes).

So the approach Jochen offered for the next maintenance release seems to sound fine to me for the simple MIDI Remote mapping GUI.

[Sparqee]

I use my Midi Fighter twister with the generic remote and it’s far from “useless”. I doubt that the generic remote is going away any time soon.

[IvanZ]

You twist my words but I don’t want to go any deeper. They’ll no listen anyway.

[Jochen_Trappe]

@IvanZ

They’ll no listen anyway

true

[Nico5]

@Pauly

HI again,

Hmm (If I Have not misunderstood), the current solution will be to disable output to the console entirely? So… when I open a project, and want to use the console as the controller, the console will not receive fader positions from Cubase and will therefore not be configured correctly. In that state, every time I touch a fader, the matching fader in the Cubase mixer will immediately take up the physical console’s position, and therefore destroy the mix. Also, if I (for example) manually modify fader positions in Cubase (actually, playback …ever!) , then play back the project, the physical faders will not follow what’s in Cubase.
I’m still hoping that I have misunderstood the solution!
Thanks
Pauly

I’m sorry, but it seems your interpretation was correct, and I was wrong in my optimism:

Midi "ghosting/Jitter" Cubase 12 with midi controller encoders (Midi Remote Control)

I just tested this in the 12.0.10 update (on Win10), but I don’t think it delivered the right solution for motorized faders and endless encoders that track current position in the hardware When disabling the midi feedback to the hardware, the MIDI Remote now seems to stop sending midi messages, even when the change to the Quick Control is originating from Cubase (or from another control surface). I think the MIDI Remote needs to work like the Generic Remote: The Generic Remote sends messa…

[dragsquares]

So what I’d like is if upon selection of a track, based on a string being present in the name (like “SM Horn”), that a specific page with mappings could be selected and a MIDI/OSC trigger be sent out, so that I could change pages in a TouchOSC setup - so if I select an SM Horn track, my TouchOSC immediately displays an appropriate editor with controllers specific to that instrument. Quick Controls are okay, but on more complex and controllable instruments one wants not just 8 knobs but often more like 3 knobs, ten faders and some keyswitches, maybe even a lot of them, and all labeled, and in positions best suited to their use with that instrument. And the goal here is for the user to always be presented with what they need in any context. How doable is this with the scripting?

Why do we need to address QC anyway, in the case of tablet control, when so much can be established simply by associating a page with the name of a track?

[Pauly]

Unfortunately I can confirm that the 12.10 fix does not fix the problem. Bummer.
Pauly

[frazer_thomson]

Workflow: Audio and Music Production

Dont k ow if this is interesing to anyone

[oqion]

Those are so cool, and if they were reasonably priced they would be selling as fast.
But they don’t really provide anything you can’t get from a Launch Control or MIDIMIX.

A measly 3 knobs with Monogram costs MORE than 24 knobs, 8 faders, and 16 buttons. +.

So why would you invest in Monogram?
It just doesn’t make any sense!

What has their response to all of the quality issues that have been reported? They offer a “Care Plan” that is more expensive that buying one of the above mentioned alternatives.

The price is just ridiculous! This is beyond the point of opinion, it is objectively a scam product.