Omnisphere, Massive X and Auto-Tune in a Browser DAW: the Bridge Workflow

Running Omnisphere online sounds like a contradiction. It's a giant desktop instrument, and a browser tab can't execute native plugin code. But with the free ClipCraft Bridge installed, Omnisphere, Massive X and Auto-Tune Pro all work inside SoundCraft, our browser DAW, and using Auto-Tune's VST online turns out to feel almost normal. Our intro post on the Bridge covers what it is and how the local WebSocket connection works. This one is the day-to-day workflow: what a session with real plugins actually looks like, from the first patch you audition to the state blob that saves with your project.

Building an Omnisphere channel

With the Bridge running in your tray, open SoundCraft's ☰ rack and click the Plugins tab. Your scanned instruments show as violet cards under a Bridge connected badge. Click the Omnisphere card and it becomes a channel, sitting next to the built-in Sampler and Grand Piano. Drag works too, if you'd rather drop it onto an existing channel.

Then hit Open plugin. The real Omnisphere window opens on your desktop, and this is the part that still surprises me: patch browsing is audible. Click through the library and each patch previews out loud, exactly like it would in a desktop DAW. One quirk worth knowing up front: Omnisphere's default patch is silent by design, so a freshly created channel makes no sound until you actually pick something in its browser. That's Spectrasonics being Spectrasonics, not a broken connection.

Spectrasonics engines also want a warm-up, roughly 10 seconds after loading before they're ready to process, and the Bridge allows one Spectrasonics instance at a time. Massive X, Kontakt and most other synths load without either restriction.

Playing live from a MIDI keyboard

Arm the plugin channel and your hardware keyboard passes straight through to the plugin. You press a key in the browser tab, Omnisphere sounds on your desktop. Clicking keys in the piano roll auditions the same way. The one catch: live auditions bypass the channel's effect chain, so you hear the raw plugin while you play. Your reverb and EQ get applied when the clip renders, which happens moments after you stop.

What happens when you draw notes

This is the clever part of the design. Rather than streaming live audio to the browser, the Bridge renders every MIDI clip offline through the real plugin and sends back a cached audio buffer, which SoundCraft schedules like any other clip. Edit a note and a re-render kicks off about 300 ms after you stop editing. Until the fresh render lands, the old audio keeps playing, and then playback swaps to the new version without stopping. In practice you tweak a melody during playback and the change just shows up a beat later.

The renders are fast because they're offline: a short Massive X clip came back as a 776 KB WAV in about 140 ms in our test logs. The Bridge fakes a moving playhead during the render, so arpeggiators and tempo-synced LFOs follow your project BPM correctly, and it keeps rolling past the end of your notes until the reverb tail falls silent. Results are cached by content (notes, tempo, plugin state), so nothing re-renders unless something actually changed.

While a plugin window is open, SoundCraft polls its state every 3 seconds. Change a preset, and within a few seconds your clips re-render with the new sound. Close the window and it does a final pull. You never press a render button.

Auto-Tune VST online: processing a vocal clip

Instruments are half the story. The Bridge also hosts effect plugins, and the entry point is the clip itself: right-click any audio clip and pick Process with plugin.

A modal lists your effect plugins. Pick Auto-Tune Pro and its native window opens so you can set the key, scale and retune speed by hand. From there you get two buttons that do very different things:

• Apply bounces exactly the clip's audible span through the plugin and swaps the audio in place. It's a normal undoable edit; Ctrl+Z brings the dry take back.
• Analyze streams the clip through the plugin without changing anything. That exists for listeners like Antares Auto-Key: it hears your song and shows the detected key in its own window, and its Send to Auto-Tune button pushes that key into any loaded Antares plugin. If you don't own Auto-Key, SoundCraft has a built-in Auto Key effect that does the same job for free.

The whole flow was verified against real iLok-licensed Antares plugins, and iLok needs no special handling. Licensing happens on your machine, where the license already lives, so a plugin that runs in Ableton runs here.

Don't own Auto-Tune? SoundCraft ships an Antares-style built-in Auto-Tune effect with 11 scales and a humanize control, free on every plan. The Bridge route is for when you own the real thing and want that exact algorithm on your vocal.

Keeping Auto-Tune on the channel

A one-shot bounce is fine for a finished take, but tuning is usually iterative. For that, a Bridge effect can live in the channel's effects rack as a persistent entry, like a built-in effect with an enable toggle, a remove button and an Open plugin button. Add one from the rack's Plugins tab, or from the processing modal's Keep on this channel button, which carries over the settings you just dialed in.

Once it's there, the channel's clips render through the chain automatically. Open the Auto-Tune window, drag the retune speed, and the audio re-processes within a few seconds while you listen. Bypass the entry and the dry original plays instantly, since the untouched source is always kept. If the Bridge isn't running at all, the channel falls back to the original audio rather than going silent.

What saves with the project

Every save pulls each plugin's full state, the same blob a desktop DAW would store, and writes it into the project. Blobs typically run 40 to 600 KB (Omnisphere's came out at 624 KB in our tests, and it round-tripped intact). Reopen a song next week and the Bridge reloads each plugin with its saved state, same patch, same tweaks; we verified the cold-reopen path end to end with a Massive X arrangement. Persistent chain entries save their state too.

Sessions are also owned by your browser tab. Close or refresh the tab and the Bridge frees your plugins automatically (a crashed tab gets caught by a 15-second ping), so you don't end up with a ghost Omnisphere instance blocking the one-at-a-time slot.

The honest fine print

Windows only for now, and VST3 only (Steinberg closed VST2 licensing, so that one is permanent). The installer isn't code-signed yet, so SmartScreen may ask you to click More info, then Run anyway. There's no live low-latency monitoring either: you can't sing through Auto-Tune while recording yet, so the workflow is record dry, then process. And since your machine does the synthesis, a heavy Omnisphere patch costs the same CPU it would in any DAW.

The Bridge is free while in early access, on every plan including Free. A free account plus the installer is the whole setup; the paid tiersare about storage and AI compute, not plugin access. If you're new to the editor itself, the SoundCraft overview covers the DAW around all of this.

My take after weeks of using it: the render-and-cache design is the right call. You give up live monitoring, and in exchange every export is sample-accurate, nothing glitches when the browser hiccups, and the synths you paid real money for finally follow you into a browser tab.