Push 2 / Nuendo & Cubase Bridge — Free, Open-Source Controller Integration

Steinberg Lounge
42

Thanks for the kind words @UK.SANTS. The Push 2 is truly an amazing controller. To see how it integrates with Bitwig shows that an open software is the key. Steinberg is on a good path with the MIDI Remote API, but there’s still a lot of good stuff missing.

I’ve not yet began the development of v1.0.7 (it’s summertime, being outdoor is more tempting than in the studio!) but there’s a feature I’m sure you’ll be happy with.

43

I’m blown away! Had no idea this existed until yesterday. Once I figured out that my Push usb cable was bad it’s been smooth sailing. I’m looking forward to exploring all the features. Thanks so much. @mbourque

44

Push 2 × Nuendo Bridge v1.0.7 — plugin browsing reimagined, programmable Key Commands, and more control than ever

Hi everyone,

A big update just dropped for the Push 2 × Nuendo Bridge — the free, open-source tool that turns an Ableton Push 2 into a full control surface for Nuendo and Cubase (macOS & Windows). v1.0.7 is the most “hands-on” release yet, and I want to highlight three things.

A completely new way to browse plugins

Adding a plugin from the Push used to be a flat scroll. Now the browser mirrors how you actually organise your work:

  • Browse by folder — it reads the folder structure of your Nuendo Plugin Manager collections and lets you drill in folder by folder.
  • A clean vertical list showing each plugin’s name, type and manufacturer at a glance — no more guessing from a truncated name.
  • Group the Default collection by Type or Vendor (a Setup option) — so even the big “all plugins” collection becomes navigable by category or by maker, with an “All” (flat) view always available.
  • Instant on-disk cache — after the first load the list opens immediately, and the bridge remembers your last-used collection and reopens it next time.

Program the note-value buttons as Nuendo Key Commands

This is a big one, and it’s worth being precise about how it works because it’s fully user-configurable:

  • The eight note-value buttons (1/32t … 1/4, to the right of the pads) become 64 assignable Key Command triggers — 8 pages of 8, switched with Page Left/Right (the current page shows in the Mix footer). Each slot gets its own colour, and a long-press on any note-value button pops an on-screen legend of the current page.
  • You configure them in a web editor: open the Plugin Mapper page (menu bar / tray, or localhost:8100) and click the Key Commands link (localhost:8100/keycmd).
  • The function picker is fed from your own Nuendo Key Commands: in Nuendo, File → Key Commands → Export, then Import that file in the editor. This is what makes the command names match your version/language exactly — assign any Nuendo command, add an optional custom label, pick a colour.
  • Hit Generate & install, then reload both sides: reload the MIDI Remote script in Nuendo (so the new bindings take effect) and press Setup → ↻ Reload on the Push (so it picks up the new colours/labels/legend). After that, your commands fire straight from the hardware.

More control than ever

On top of the above, v1.0.7 adds: a proper expression-pedal mode (either jack, riding Volume / a Quick Control / a Send / a MIDI CC / the AI Knob, with on-screen calibration and the touchstrip LED following the value); long-press “expand” menus on New/Duplicate/Mute/Play/Record/Fixed Length that surface a whole set of related Nuendo commands; Backup & Restore of every setting as a single zip; lower idle CPU; and a batch of robustness fixes (DirectAccess reliability, end-of-project banking, plugin-name matching, faster plugin-list streaming).

Get it (free, GPL-3):

Requires Nuendo 14+ / Cubase 14+. The Plugin Browser, Channel Strip DirectAccess and the Key Commands installer need Nuendo 15+ (API 1.3). Feedback and issues welcome on GitHub — hope it makes your sessions more tactile!

45

Hi everyone,

I’m really enjoying the Push 2 integration with Cubase/Nuendo — huge thanks again to @mbourque for making this possible.

I wanted to ask the community something: is it currently possible for the Push pads to reflect incoming MIDI notes from the Cubase piano roll?

For example, when a MIDI clip is playing in the piano roll, the notes don’t seem to illuminate the pads on the Push. I’m not sure if there’s a specific setup required, or if this behaviour simply isn’t supported yet. If anyone has managed to get this working, I’d love to know how you configured it.

I also have a small feature request that might help workflow: the ability to hide certain tracks from the Push display, such as Mono In 1, Mono In 2, Stereo Out, etc. These take up visual space on the device, so having an option to hide or filter them would make navigation cleaner.

Curious to hear your thoughts!

46

Hi,
The short answer is no. For this to work, the Push would need the MIDI data from the track but Cubase doesn’t output it. I haven’t investigate a workaround for this but it would probably imply a manual setup for each tracks for which you want that visual feedback. It did not put effort into that because I wanted the setup to be as easy as possible. If someone want to try to find a solution, it is very welcomed!

You can’t control the visibility of the tracks with the bridge. The bridge shows whatever tracks are shown in the MixConsole. If you hide those tracks on the Push, you must hide them in the MixConsole.

47

@mbourque - Thank you for all your hard work developing the bridge to get the Push 2 working so well with Cubase. I’m not currently using the full functionality of it yet as I’m still on Cubase 14 pro, but I’m sure I’ll make fuller use of all the features once Cubase 16 is out and I’ve upgraded. I have a request for the next bridge is version (if it’s not too much of a hassle!! :folded_hands:). I have an issue with the velocity sensitivity of the pads being very low for some of my VSTi’s where I find I have to really whack the pads to get a decent midi velocity level to trigger / record on the VSTi’s (which really destroys the dynamic input feel when trying to play grooves or beats on the pads for drum VSTi’s). The sensitivity of the pads overall is great and I have tried all the different velocity curves, but, unless I set it to fixed velocity, the VSTi’s triggering / recorded velocity values are very quiet, making the hard to hear in a mix. Is it possible to either add another velocity curve option greater than logarithmic ((?) - can’t remember the ‘expanded’ velocity curve name)) or allow the user to set minimum/maximum values for transmitted velocity curve ‘ranges’. I’m sure I’ll cope if it’s not possible to implement anything like this but would be very handy if possible! :crossed_fingers: Thanks again for all your hard work.

48

Hi GDMusic,

Thanks for your feedback. I’ve put your request on the list. I don’t have time currently to work on new features, but your request will be part of the next release!

49

Just finding out about it now. Can’t wait to get it hooked into studio. Hitherto I’ve been midi mapping but it always kinda came out flaky…….looking fi’ to trying your code

50

I hope it suits your needs!

51

Ungrateful question maybe.. :slight_smile: Are there any screenshots of this in action? (even showing the Push2 screen?)

52

Hi.

I can guarantee this is fully compatible with latest version of Cubase. I’ve been using it for months now and seem cubase working with push 2 is a very pleasant experience.

@mbourque created something quite magical between Push 2 and Cubase.

Looking forward for more upcoming updates.

thanks

53

I’m working on a tutorial video to show all the features but right now I’m quite busy. I’ll try to post pictures in the next few days.