REMOTE SURFACE: Mixer fader not feeding back to controller but does in generic

As above
I have a row of encoders sending to track 1-8 vol in mixer bank
Output of CS is pointing to the hardware but not feedback seems to be happening
I test by disabling script, connecting MC remote (controller is using MCU emu) and moving a fader, selecting acts as expected
Reenabling CS does not send feedback…shouldnt the movement of the fader on the mixer replicate the feedback or is it 14bit and Im missing something


What do you mean by CS, please?

(C)ontrol (S)urface


And what do you mean by Control Surface, please?

Could you use Cubase terminology, please?

Hi @Martin.Jirsak
Sorry for any confusion.
Control surface is a very common term. I do work for OEM midi hardware manufacturers in China and thats what they call midi hardware designed for controlling daws etc
Remote midi is a function not the object


What kind of connection/surface do you use in Cubase, if this doesn’t work for you, please? Is it a Generic Remote Device, a dedicated Remote Device component, or a MIDI Remote device?

Could you attach a screenshot of your settings?

So Im working in the remote editor which is connecting to the hardware and is responding correctly however the output from cubase is not send the correct info back to the controller as the LEDs are not responding
You can see here, this map is simply the one to do the basic mixer functions of vol etc.

To test if cubase is able to correctly send midi back to the controller, I disabled the script and setup a legacy Mackie Control and set only the output to the control hardware and this works ie I grab a fader on the mixer and move it, select a track etc


OK, so you are using MIDI Remote, and you are not writing a script, you are using the Mapping Assistant.

From this sentence I expect, the hardware controller has any kind of rotary encoders and a LED ring around. Something, like Mackie Control’s V-Pots.

If this is the case, the LEDs are very often receiving other MIDI Message then the encoder is sending out. This is, what Mackie Control with the V-Pots also does. Use any MIDI Monitor application to verify, Cubase is sending the MIDI data out (I can confirm, it does). But your hardware is expecting other MIDI data to be received.

Correct. I really dont want to learn any more code…as mentioned…doing it all my life…it is antithetical to creative music. The assistant should be able to do most stuff. I urge Steinberg to view other middleman editors like Remotify for Ableton…it allows both graphic and code and anywhere in between

No, I was testing using just simple mute and select (buttons) which the hardware does receive properly from the legacy/mackie remote.
It is a simple, small but flexible unit suited to use above the keyboard


Is the hardware device still in the Mackie Mode, when do you test it?

Why you don’t use one of the MIDI Remote Mackie emulation custom script?

Ill explain a bit more.
Im only using the legacy mode to test as I know it is a baseline that absolutely works.
I have have a range of presets that are switched using a shift key
Map 1. The navigation preset. This is a temporary preset that presents a choice of the maps i can choose from. If i dont choose a map, on release, of the shift button, it returns me back to the IFX (insert fx map)

Map 2. Insert FX…this is the main need for this control surface. Im yet to be able to implement this without kludging because there are so many roadblocks to simply making it work…as far as I can see.
I simply want the columns of buttons to select a plugin by number ie button number 2 opens plugin 2, the gui opens and the controls now address parameter 1-8 etc

Map3. This is the standard mixer which just does the normal mackie stuff… I rarely use this but its to level match as Im doing the fine sculpting using plugins. I actually use another control surface (bcf2000) for actual mixing and automation ie as it has faders

Hope this helps


As you are not using the terminology, it’s still very hard for me to understand, what you are doing, what do you want to achieve and what is not working.

By the Map, do you mean the MIDI Remote Page? What do you mean by present in this context?

Hi @Martin.Jirsak
I do apologise…Ive spent a number of years doing UI/UX so perhaps Im unaware of a developed culture/language with other vendors.

Im actually using the terms used by the remote editor…
So when I say, ‘Map.1’ I mean the ordinal index (1) of the first mapping page in the Midi Remote Editor
I had a quick look at the api and its seems its straightforward although there are no direct access to the index of mappings and you have to use the method ‘GetIndexBy(n)’

I then extend the to the word ‘Preset’ as its a group of functions relative to a mode or phase. ie the mapping page is a virtual container holding the actual functional group(s).

In the first mapping page (Map.1), this is a preset/mode that is concerned with ‘navigation’ using a momentary shift button and other ‘global’ type settings of this particular remote editor script.
They are preset, in other words there are not really any variables/parameters…just preset buttons to step to other mapping pages or global on/off etc.

I use the mapping name ‘default’ as its persistent across all other mapping pages (momentarily) and seemed logical as it cant be renamed.

UI/UX of course needs to be synapse friendly, hence the forks/pathways being presented with this psychology…which will make more sense once I can get gestures working (which I will do in the interim using Bome as its seems painful in JS5 without a callback timer)

Does that make it any clearer?


Could you please use any MIDI Monitor software to verify, which data does Cubase send out?

I was doing that.
Im working today (not music) but Ill set it up again and do screen grab.

1 Like