Want to use your macOS or Windows computer as a plug‑in host for live performance? StageBox aims to let you do just that, with minimal fuss.

StageBox is a cross‑platform macOS and Windows plug‑in host application, a collaboration between the Grammy‑nominated composer and musical director Matt Robertson and music software developer extraordinaire Julian Storer. It’s available from tracktion.com but actually is a completely separate, independently developed product.

StageBox’s raison d’être is to support the use of software instruments and effects in live performance. In that, it also stands as a purposely simpler, leaner alternative to the likes of Gig Performer and the macOS‑only MainStage: its feature set is unquestionably smaller, but it’s also potentially quicker and easier to use.

Principles

The window you’re presented with, on starting StageBox, is the heart of the user interface. There are very few additional elements to discover: there’s no mixer, for example, and just a single file menu with a handful of familiar open and save options, and undo/redo. Elsewhere there are just a few additional drop‑down menus and overlays for general settings and MIDI mappings.

StageBox’s essential internal structures, then, are these: single instrument plug‑ins, with potentially many effects, are instantiated to form what is called a ‘sound’ (that’s done in the central, slightly lighter grey section of the user interface, in plug‑in slots), and if you’ve used any DAW it’ll feel like second nature. You can have as many of these sound layers running concurrently as you wish (supporting keyboard splits or textural stacks, for example), and to view and edit one you click on its tab to the left. The tabs are provided with mute and solo buttons for the audio output, a level meter, and also a MIDI input mute.

One or more sound layers are what constitute a Song, and multiple Songs can be assembled into a Setlist. A single StageBox window can thus take care of the sound hosting and running order for an entire musical set or show, with the whole shebang saved as a Project.

As you might expect, there’s considerably more nuance along the way. For one thing, it’s possible to break a single Song down into multiple sections, to support differing sound requirements for verse and chorus, say. Audio processing is highly configurable too, with plug‑in slots offered in both insert and send/return structures, per layer, and with further slots at the Song level (so to speak) that all layers feed into. Layers can be transposed (up to four octaves up or down!), limited to specific pitch ranges and hardware MIDI controllers (in case you have more than one), and their MIDI input filtered by channel and event type. You can also direct individual layers to use separate outputs of a multi‑channel audio interface, perhaps to drive a different amp, or for on‑stage guide/cue feeds.

There’s also good potential for controlling StageBox knobs and plug‑in parameters from a hardware MIDI controller. Every Song has its own MIDI map for this, and setup is a cinch: working in the dedicated editor overlay, just move your hardware control, click on a software parameter, and the link is established. Global‑level MIDI mappings are available to step backwards and forwards through Songs in a Setlist, and for tap tempo (which can sync synth arpeggiators, effect delay times and so on).

What StageBox notably doesn’t do is handle audio inputs. It’s purely an instrument and effects host, to which you direct MIDI. Equally, it doesn’t by itself address any hardware or USB MIDI outputs on your system, so you can’t use it to integrate a hardware synth rig. I understand these abilities, which would of course be very desirable, have at least been considered for a development road map, but they’re not part of StageBox yet.

Showtime

In use, with one or many Songs in a Setlist, all instruments and effects are instantiated at the same time. Switching songs is then effectively instantaneous, and pulls off the ‘seamless transition’ trick coveted in high‑end stage keyboards, letting you start playing a new song while sounds from the previous one are still decaying, or even sustaining. Memory usage is potentially an issue here — you’ll ideally want a lot of physical RAM for ambitious sets — although StageBox will in fact start to use disk‑based virtual memory if required. CPU use accrues as well of course, confirmed by the numerical CPU indicator at top right of the main window. Instruments and effects seem to be hosted very efficiently, but you’ll still need a potent computer to allow low‑latency responsiveness.

StageBox offers a dedicated Perform Mode for live use, which hides the sound/layer infrastructure, and gives the option of displaying some editable text notes for each Song. There’s a nice touch as you enter this performance‑specific mode: a pop‑up overlay appears that suggests some basic pre‑performance checks such as disabling Wi‑Fi and notifications, checking power supplies and so on. You can turn this off, or edit the text to adapt it to your own needs.

Where it’s obvious that StageBox has been developed really thoughtfully, with a practical mindset, is in concepts like Shared Instances. This allows you to create Song duplicates that do not require their own independent RAM and CPU resources. They’re ideal if you have a Setlist of 20 Songs, say, of which 10 use the same piano sound. Make those shared instances and you can still name them independently, and put them in the right Setlist order, but the piano they use only gets loaded once.

Another neat concept is virtual MIDI inputs. They provide a symbolic alternative to directly specifying the hardware MIDI controller used to control a sound layer; the idea being that if you ever need to swap your controller for a different model, mid‑tour perhaps, a single click in the main Settings overlay makes the change, saving you from laboriously doing it for every layer of every Song.

Robustness

I tested StageBox over a period of a month or so, and threw everything I could at it: big piano and orchestral sample libraries, dozens of soft synths, and many effects plug‑ins. I couldn’t catch it out. It proved rock solid, and I wouldn’t hesitate to use it on stage. Actually, I ended up using it in my studio quite a bit too, when I wanted a quick hit or to do some programming with favourite software synths: it’s a lot quicker and more responsive than using a DAW for the same thing. Both conventional and MPE controllers (and MPE‑enabled plug‑ins) seemed to work straight off, with no configuration. Really hefty sample‑heavy Projects would sometimes take 15‑20 seconds to open from scratch, as everything loaded up, but they always did so reliably.

I have no serious criticisms of StageBox at all — I love it when that happens — but there are a handful of additions that I think would enhance the already strong feature set. Text‑based filtering and searching in plug‑in pop‑up menus would be really welcome: the two‑column Developer/Name hierarchy in pop‑up menus used currently, though neat and sensible, is cumbersome with really long lists. And whilst I didn’t miss a vertical‑format mixer, I could see the value of duplicating the layer volume knob setting as a small fader in Sound layer tabs, near the mute and solo buttons, for rapid balance changes. Layers don’t currently have stereo pan/width controls either. That functionality can be duplicated with certain third‑party plug‑ins, but it’d be better if it was built in.

StageBox is a super app that has the potential to do some really heavy lifting in a live situation.

Even as it stands, though, StageBox is a super app that has the potential to do some really heavy lifting in a live situation. It can’t match Gig Performer or MainStage feature for feature, but it makes up for that in speed of deployment and ease of use. If you’re on the look‑out for this type of software, you might just find it already ticks all your boxes.