Integration

Pibox for Cubase & Nuendo

Review inside the project, drive the transport from a comment, and take the notes out as markers when it is time to work.

VST3 · macOS & Windows · included with Pibox

What you get

The transport answers to Pibox

A MIDI Remote driver script bound to notes drives transport, locate, cycle range, loop, markers and bounce — so clicking a comment moves the project, not just the plugin window.

Comments sit at their timecode

Reviewer notes arrive where they were written. Jump to one and the cursor follows; reply and resolve without switching to a browser.

Export notes as markers

Take the thread out as a marker CSV at exact timecode, where range comments become cycle markers. A MIDI file works too if that fits your template better.

Bounce through the native dialog

Bounce is driven from Pibox but opens the standard Cubase export dialog, so your own render settings and naming stay in charge.

Installing it

  1. 01

    Download the Pibox desktop app for macOS or Windows — the VST3 build is bundled with it.

  2. 02

    Run the installer, then restart Cubase or Nuendo so it rescans plugins.

  3. 03

    Enable the Pibox MIDI Remote script in Studio Setup to give it transport control.

Questions

Which plugin format does Pibox use for Cubase and Nuendo?

VST3, on macOS and Windows. The same installer also ships the AAX build used by Pro Tools.

Can comments become markers in Cubase?

Yes, as an export rather than a one-click drop. Pibox produces a marker CSV at exact timecode — range comments become cycle markers — or a MIDI file. The one-click Memory Location import is specific to Pro Tools.

What does the MIDI Remote script control?

Transport, locate, cycle range, loop, markers and bounce. It is bound to notes, so Pibox can move the project rather than only its own window.

Is Nuendo supported separately from Cubase?

Both run the same VST3 build and the same MIDI Remote script — there is nothing extra to install for Nuendo.

Also in Pro Tools or Resolve?

One installer covers all of them — the marker import differs per host.

All integrations →