Advanced configuration
The StreamDeck Nuendo plugin by default locates the highest installed Nuendo version and uses key and midi definitions from that version. It also assumes that the first defined Generic Remote device is to be used for midi definitions. If these two criteria match your installation, you don't need to do anything.
If, however, you have multiple Generic Remote devices or want to "talk to" a lower Nuendo version, you can change the behavior through the file "StreamDeckNuendoUserSettings.xml". As installed during the plugin installation, this file looks like this:
<?xml version="1.0" encoding="utf-8" ?>
<Settings>
<NuendoPath></NuendoPath>
<GenericRemoteName></GenericRemoteName>
</Settings>If you want to use this file, you must first make a copy of the file to the root of your Documents folder or to a subfolder Trevliga Spel. Starting with plugin version 2.0, the preferred location is to store all Trevliga Spel custom plugin files in the folder Trevliga Spel. If there are copies of the file both in the root and in the subfolder, the file in the Trevliga Spel folder is used.
Copy the file from "%appdata%\
Changes to this file are immediately read by the plugin.
- Alternate Nuendo version
-
The NuendoPath parameter defines the path to the Nuendo folder to use. If the parameter is empty, the default behavior (locate the highest installed version) is used. If the parameter contains a path, that path is used. The recommended configuration on PC is to use the %appdata% environment variable, on Mac "~" (tilde), and then add the rest of the path to the Nuendo folder that contains "Defaults.xml" and "Key Commands.xml":
<NuendoPath>%appdata%\Steinberg\Nuendo 11_64</NuendoPath>
<NuendoPath>~/Library/Preferences/Nuendo11</NuendoPath> - Alternate Generic Remote device
-
The GenericRemoteName parameter defines the name of the Generic Remote device present in the Nuendo Studio Setup Remote Devices list. If this parameter is empty, the first defined Generic Remote device is used. If you want the plugin to work with another instance of Generic Remote device, you need to define the name here:
Please note that the English name "Generic Remote" should be used regardless of how it is presented in the Nuendo Studio Setup window. If you have a non-English version of Nuendo you will have a localized name in the Studio window but must still use the English name in this file.<GenericRemoteName>Generic Remote 2</GenericRemoteName>
- Multiple Generic Remote devices
-
You can add multiple rows of GenericRemoteName declarations if you want to use multiple Generic Remote devices in Nuendo.
<GenericRemoteName>Generic Remote</GenericRemoteName> <GenericRemoteName DisplayName="Mixer">Generic Remote 2</GenericRemoteName>If two or more GenericRemoteName declarations are present, the action will display a dropdown where you can decide which remote device to access for that action. The commands available in the Commands dropdown will update to display the commands available in the selected Generic Remote device in Nuendo.
It is possible to add a "DisplayName" attribute (see the example above) that will be displayed in the dropdown for the action. If no "DisplayName" attribute is present, the name of the Generic Remote device is displayed.
Please note that you must yourself make certain that definitions in different Generic Remote devices doesn't overlap and specify the same channel/address. When you use (i.e. send) a command selected from a specific Generic Remote device you don't really reference the Generic Remote device in any way. The only thing that is sent is a Control Change command with the parameters that were defined in the Generic Remote setup. If you have multiple Remote Devices that have actions that respond to the same channel/address, all of those actions will be triggered which can create a difficult-to-diagnose result.
