I’m having the following problems during setup with Nuendo MIDI:
First off, I don’t know where to find the Mackie Control command object; I can only see the Nuendo Key and MIDI command objects? There’s an explainer video that shows all three of the aforementioned objects (had I not come across that, I wouldn’t even know that I can actually send Mackie Control commands…!)
Secondly, trying to configure a MIDI object, it says “MIDI configuration not OK” because of
1. “Generic Remote configuration data for {gr.Name} could not be read from Defaults.xml”
→ I don’t know what this means since it does say that “Defaults.xml successfully read”?
Nuendo “Generic Remote” MIDI Input should be assigned to “StreamDeck2DAW” but is assigned to “StreamDeck2Daw” … same error message for the other direction BTW.
→ I used loopMIDI to create various in- and outputs, first using upper case letters for “DAW”, but then I erased and recreated them using “Daw” (only first character in upper case). The latter ports appear correctly with Nuendo, but the Streamdeck app still asks for the upper case version, although they’ve been deleted…?!
Nuendo Generic Remote Commands ‘‘ could not be read
(that’s exactly the spelling, including the ‘‘ with nothingin between)
That being said, I’m using a rather old version of Nuendo (Version 7!!) / Win10, but all has been working fine so far (including installation of recent 3rd party plugins etc.)
I recommend using the Midi plugin instead of the Nuendo plugin. The things you are missing, e.g., Mackie Control, only exist in the Midi plugin.
To be honest, I don’t know if the Nuendo plugin works with Nuendo 7. Steinberg is changing functionality with each new version, and the file content may differ from what the plugin expects.
The Nuendo plugin requires the Generic Remote to be configured in Nuendo, along with key commands. The configuration files read by the Nuendo plugin are not created until you make a change to those settings, so you must, e.g., change a key command and save it. The plugin will not be able to read the key commands until you have done that.
As a matter of fact, I just purchased the MIDI plugin… didn’t see it in the Elgato store before, since a search for “Nuendo” didn’t seem to bring it up.
But I guess I’ll keep your Nuendo plugin in order to send Key commands (non-MIDI)…?
A quick test of some Mackie Control commands revealed that Nuendo seems to receive them correctly.
However, I have another controller using the Mackie protocol (an Icon Platform M+) hooked up with Nuendo, which now seems to behave erratically (no longer showing any channel names, operating any control will have no effect in Nuendo) - may that be caused by a possible conflict of StreamDeck and the Icon?
E.g. would I need to change the Device setting from “Main Device” to “Extender” and create extra MIDI ports for each?
Yes, if the plugin reads the key command file correctly from Nuendo 7, you can. It is also possible to use the Midi plugin to send Midi commands that trigger key commands, which have the added benefit of working even when Nuendo isn’t the active window.
You definitely need extra ports; two Mackie devices must not use the same ports, that would cause complete chaos.
I assume Nuendo works the same way as Cubase, with the odd definition that it is the LAST Mackie device in the remote device list that is considered to be the Main device.
It’s a Nuendo thing, not a plugin thing. In the Generic Remote, you can assign a remote command to the “device” command, and then select which command you want to control.
