edit: This is in both Cubase Pro 12.0.30 as well as Cubase Elements 12.0.30
I’m working on setting up my midi controllers in Cubase right now, and wanted to make use of the built in GUI for making them, as opposed to scripting right now, as I’m just wanting to do some proof of concept while configuring things.
I have a consistent issue with controllers sending back incorrect (and oddly delayed) midi to my controllers.
Have a look at this data… in particular the last 3 rows here, as this behaviour is very consistent through multiple controllers I use:
For this example, I use my Faderfox MX12 fader controller which sends to Cubase controller channel volume.
In the last 3 rows you can see that my MX12 sends out midi cc value 14, and 40ms after, Cubase sends back midi cc value 13, and then another 500ms later another message comes through with 13 again.
This causes the value to bounce back to 13 on my controller…and unless I make a wider movement, i.e. sweep through more values, I’ll be stuck at 13, as this keeps happening all the time.
I noticed not all values behave like this, and it’s more often occurring on going UP in value. Going down it’s less frequent.
This looks like a rounding problem to me.
I have this issue consistently with several controllers using them either together, or only one connected at a time.
For info: I get this on my Faderfox MX12, Faderfox PC4 as well as my Adafruit Macropad that I set up for Cubase, so it doesn’t seem related to my controller.
This is how my controllers are set up for this:
Is this a known issue? It’s very easy to reproduce, as it happens all the time.
It makes it really hard to do fine movements to set values.
Is there a workaround? Can I solve this by just making my own scripts instead? This seems like something that should be working the way I set it up though.
If scripting is the only way around it for now I’ll do that though.