The New MIDI Remote is

[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…