Cubase / Nuendo

Description

Integrates with Cubase and Nuendo via Steinberg's MIDI Remote API. Provides a Selected Channel surface, a Commands surface, two Generic Remote macro banks, and Logical Editor / Project Logical Editor presets. Covers the full command set and selected-channel parameters. Requires Cubase 12 or Nuendo 12 or later.

Setup

Open MetaServer → Integrations → Cubase (or Nuendo). MetaServer installs every required file directly into the DAW's preferences folder — no manual file placement needed. Configure the surfaces inside Cubase once installation completes.

The Integration Components card groups setup into three sections:

• MIDI Remote — Selected Channel script + Commands script (Cubase 13+ recommended path)
• PLE / LE Presets — Logical Editor and Project Logical Editor preset bundles
• Generic Remote Devices — Optional macro slots for custom workflows

Click Install on a component row to deploy it. Each section's sub-page below covers the in-DAW configuration that follows.

Topics on This Page

• MIDI Remote setup — Cubase 13+ recommended path
• Generic Remote setup — works on every Cubase version
• Plugin Manager — surface insert / send slots on MetaGrid Pro
• LE Macros — Logical Editor presets via Generic Remote
• PLE & Scene Macros — Project Logical Editor and scene-switching macros

Which Method to Use

MIDI Remote (recommended for Cubase 13+): Steinberg's modern MIDI Remote API with dedicated MetaGrid Pro controller surface scripts. Provides bi-directional communication, selected channel control, and command mapping.

Generic Remote (Cubase 12 and earlier, or if you prefer the legacy approach): 5 XML files imported as Generic Remote devices. Covers commands, selected channel control, and LE/PLE macros in a single system.

Both methods coexist without conflict. MetaServer drives the MIDI Remote install end-to-end; Generic Remote still requires manual XML import inside Cubase (MetaServer downloads the bundled XMLs to your Downloads folder when you click Download Generic Remote devices).

MIDI Ports

MetaServer creates the required MIDI ports automatically on both Mac and Windows (MetaServer 6+). See MIDI Ports for the full port list and the legacy LoopMIDI fallback if you're on an older MetaServer. On Windows 11 specifically, if the Metasystem - Cubase - … ports don't appear in Cubase after MetaServer launches, follow Native Windows MIDI Services Setup once to enable the native MIDI stack — then loopMIDI isn't needed at all.

For MIDI Remote you need: Metasystem – Cubase Sync – In/Out, Metasystem – Cubase – In/Out, and Metasystem – MIDI – In/Out. For Generic Remote you need: Metasystem – Cubase – In/Out and Metasystem – MIDI – In/Out.

Prevent MIDI Feedback

Regardless of which method you use, exclude MetaSystem ports from Cubase's global MIDI input.

Step 1: Open MIDI Port Setup

Go to Studio → Studio Setup → MIDI Port Setup (under the MIDI folder).

Step 2: Uncheck "In All MIDI Inputs"

Uncheck the In All MIDI Inputs column for all Metasystem ports except Metasystem - MIDI - In (keep that checked if you want to record MIDI from MetaGrid Pro on tracks).

LE and PLE Macros

Custom Logical Editor and Project Logical Editor macros use the Generic Remote system regardless of whether you use MIDI Remote or Generic Remote for commands. See LE Macros and PLE & Scene Macros.

Menu Commands (Mac Only)

On Mac, the Menu Command action provides access to every Cubase menu item without any MIDI configuration. Works alongside either integration method.