While this hasn’t caused a decrease in MIDI performance, I was curious if this is the typical behavior of Cubase.
I have a Streamdeck device configured as a MIDI Remote. The Streamdeck’s MIDI plugin can receive MIDI data from the DAW.
I’ve set up a MIDI viewer to read the MIDI Out messages, and I’ve observed an unusual behavior. Whenever I hover the mouse over the track, zoom in the timeline, or interact anywhere on the screen, it sends MIDI Out from Cubase to the Virtual Out port, even if I’m not triggering any MIDI remote commands from my Streamdeck. Is this normal? I understand that it may be necessary to send data back to my Streamdeck for the On/Off state or the V-pot positioning, but I’m curious if others have experienced this behavior and if there are any insights into it.
Hi,
What kind of parameter(s) do you observe from Cubase, please?
I
I have an extensive MIDI Remote Script with over 900 commands using MIDI CC from a Streamdeck device with the Trevliga Spel MIDI Plugin. The script is configured to receive MIDI IN data from the “StreamDeck2DawTrack” virtual port and send MIDI Out data from “DawTrack2Streamdeck.”
I’ve set up MIDI View to monitor outgoing MIDI data from Cubase back to my Streamdeck, focusing on the data from the “DawTrack2Streamdeck” virtual port. An unusual behavior occurs when I hover my mouse over the Zoom timeline or anywhere on the screen – it sends MIDI data messages from Cubase to “DawTrack2Streamdeck” without pressing any Streamdeck buttons.
I assume the data sent from Cubase represents the Off State of the MIDI CC I’ve used. However, it shouldn’t send this data when I’m just hovering my mouse, right? It should only transmit when I press the Streamdeck device or select a track.
This behavior seems odd, and whenever I hover, it continually sends repeating MIDI data until I move the mouse elsewhere.
here’s a video example
I’ve tried to configure another Midi Remote Script with a different Midi ports.
It did not display the same behavior at first. But when i added The AI Mouse Dial action it display the same Behavior. At least I know now what’s triggering it. But isn’t this ODD?
or it’s just the way Cubase is configured.
Hi,
The AI Knob emulated the scroll wheel some way. So if you hover over a scroll-able parameter, it can do something.
Yeah I understand that But Upon inspection it’s sending all the off state for Mute, solo, Read, Play, stop and etc.? and It is not stopping until I hover the mouse elsewhere.
