Cubase: Generic Remote

The Generic Remote method works with all Cubase and Nuendo versions. It uses 5 XML files imported as Generic Remote devices to handle commands, selected channel control, and macro slots.

Overview of XML Files

The integration uses 5 XML files:

• Metasystem1.xml — Core Cubase/Nuendo commands (part 1)
• Metasystem2.xml — Core commands (part 2), including scene and LE macro triggers
• Metasystem3.xml — Selected channel parameters (volume, pan, mute, solo) with bi-directional communication
• Metasystem_macros.xml — Custom LE/PLE macro slots (Macro 001–008)
• Metasystem_macros2.xml — Additional macro slots (Macro 201–208)

Full integration requires all 5 devices.

Download the Macro XMLs via MetaServer

MetaServer hands you the two macro-slot files directly.

Step 1: Open MetaServer

Open MetaServer → Integrations → Cubase (or Nuendo).

Step 2: Click "Download Generic Remote devices"

In the Generic Remote Devices section of the Integration Components card, click Download Generic Remote devices. MetaServer copies metasystem_macros.xml and metasystem_macros2.xml into your Downloads folder and reveals them in Finder / Explorer.

For the other three XMLs (Metasystem1.xml, Metasystem2.xml, Metasystem3.xml), open the App Specific Resources package and copy them out of the Cubase folder.

Import the Generic Remote Devices

Repeat these steps for each XML file:

Step 1: Open Studio Setup

Go to Studio → Studio Setup.

Step 2: Add a Generic Remote

Click the + icon in the upper-left corner. Select Generic Remote from the list.

Step 3: Import the XML File

Click Import and select the XML file.

Step 4: Set MIDI Ports

For Metasystem1.xml and Metasystem2.xml: set MIDI Input/Output to Metasystem - Cubase - In/Out (Mac) or the corresponding LoopMIDI port (Windows).

For Metasystem3.xml: set MIDI Input/Output to Metasystem - MIDI - In/Out. This file handles selected channel parameters and requires the MIDI port for bi-directional communication.

For Metasystem_macros.xml and Metasystem_macros2.xml: set MIDI Input to Metasystem - Cubase - In (Mac) or the corresponding LoopMIDI port (Windows).

Step 5: Repeat

Add a new Generic Remote for each remaining XML file. You should have 5 Generic Remote devices when finished.

Point MetaServer at the Macro Files

Once the macro XMLs are imported into Cubase, point MetaServer at the files you imported so it can read your custom macro names back to MetaGrid Pro.

Step 1: Open the Cubase Integration in MetaServer

In MetaServer → Integrations → Cubase, scroll to the Generic Remote Devices section.

Step 2: Locate Each Slot

For Generic Remote macro 1, click Locate… and pick the metasystem_macros.xml file. For Generic Remote macro 2, click Locate… and pick metasystem_macros2.xml.

If the file is later moved or deleted, the row shows File not found at the saved location with a Reinstall button — clicking it re-downloads the bundled XML to Downloads and re-points the slot in one step.

Verify the Setup

In Studio → Studio Setup, you should see 5 Generic Remote devices listed under Remote Devices (Legacy):

1. Generic Remote (Metasystem1) — Cubase port
2. Generic Remote 2 (Metasystem2) — Cubase port
3. Generic Remote 3 (Metasystem3) — MIDI port
4. Generic Remote 4 (Metasystem_macros) — Cubase port
5. Generic Remote 5 (Metasystem_macros2) — Cubase port

Bi-Directional Communication

Metasystem3.xml enables two-way sync for selected channel parameters. When you change volume, pan, or solo/mute state in Cubase, MetaGrid Pro's faders and buttons update to reflect the current value.

Important: If you experience unexpected behavior with bi-directional communication on the Selected Channel grid, try disabling Metasystem – MIDI – In in the "All MIDI" column as well. This prevents Cubase from routing MetaSystem's MIDI back into the selected track. The tradeoff is that generic MIDI messages (CC from faders) will no longer register on the selected track.

Assigning Custom Macros

The macro slots in Metasystem_macros.xml and Metasystem_macros2.xml are unassigned by default. Map them to any Cubase command:

Step 1: Open the Generic Remote

Go to Studio → Studio Setup and select the Metasystem – Macros device.

Step 2: Select a Slot

In the lower half of the window, click a Macro entry (e.g., Macro 001).

Step 3: Assign a Command

Set Device to Command. Set Channel/Category to the desired category (e.g., Process Project Logical Editor). Set Value/Action to your command.

Keep Macro Names in Sync

If you rename a macro in the Generic Remote (e.g., "Macro 001" → "Repeat Record"), use the Refresh button at the top of the MetaServer → Integrations → Cubase page so MetaServer re-reads the file. The renamed macros then appear in MetaGrid Pro's Cubase action list.