Please read!
The Cubase plugin was designed to simplify Stream Deck configuration by reading Cubase configuration files and pre-populating the plugin with key commands and Generic Remote configurations made in Cubase. However, due to changes in Cubase made and announced by Steinberg, the plugin will eventually stop working.
Steinberg has announced that the Generic Remote device in Cubase will be removed in a future, unspecified Cubase version, and when that happens, the Midi part of the plugin will stop working.
Steinberg has changed how key commands are saved to the configuration file (and hence available to the plugin) in Cubase 13. When key commands are changed, the configuration file is not updated until Cubase is restarted. This change by Steinberg means that whenever you make a key command change in Cubase, you need to restart Cubase in order to have that change available in the Cubase plugin.
Using the Cubase plugin's key command feature will still be possible, but I believe the initial goal of simplifying things is no longer fulfilled. Sending key commands using the Stream Deck Hot-key plugin is easier, removing the need for a Cubase restart after key command changes.
Since the original design goals are no longer valid and the Midi part of the Cubase plugin will eventually stop working, the plugin will not be further developed or maintained.
Of course, you'll have to decide for yourself whether you want to use the Midi part of the Cubase plugin for the remaining time before Steinberg removes the Generic Remote. The same goes for the key command part, which still works but has become more cumbersome due to the Cubase restart requirement imposed by Steinberg's changes.
My recommendation, though, is to consider a move to the Midi plugin instead. The Midi plugin has far more features than the Cubase plugin, and it is future-proof, maintained and further developed.
Overview
- Key Commands
-
When using Key Commands, Cubase must have focus on the computer screen since the key codes sent are captured by the active window. All defined key commands in Cubase are directly selectable in the StreamDeck editor when configuring an action.
Key commands are unidirectional and don't get any feedback from Cubase. Due to this there is no way to determine the current state of an action by just looking at the StreamDeck.
The configuration is fairly simple; you only need to define the key commands you want to use in Cubase, and they will automatically be available in the StreamDeck plugin.
- Midi Access
-
When using Midi access there is no requirement that the Cubase window has focus on the computer. The StreamDeck plugin communicate directy to Cubase using Midi (of course).
Midi access is bidirectional and receives feedback from Cubase. The current state of an action can be seen on the StreamDeck even if the action is initiated directly in Cubase. If you e.g. hit the record button in Cubase, the record button on StreamDeck will show that recording is in progress.
The configuration is a bit more complex in that you have to install a separate program that act as "virtual Midi cables" used in the connection between StreamDeck and Cubase. You also have to configure the "Generic Remote Controller" in Cubase to define all the functions you want to control from StreamDeck.
The StreamDeck Cubase plugin and is available for PC and Mac (from version 2.0) and can interact with Cubase both using key commands and by using Midi. Both methods are closely integrated with Cubase and the definitions made in Cubase are automatically imported by the StreamDeck plugin.
The plugin is developed and tested on Windows 10/MacOS 11.4 with Cubase 10, 10.5 and 11. It may work with earlier Cubase versions but that is not tested. It may work with earlier version of MacOS but please note that it does not work in Windows 7.

Contributions of any size are greatly appreciated.