Feedback loop

Live mix.

Stream your DAW to the round in real time. Clients listen in the browser through the share links they already have.

What it is

Go live on a round and anyone holding that round's share link hears your master bus as you work — no installs on their side, just a listen in button. You see who's listening; they hear the mix the moment you touch it.

Live mix is an addon — flip it on under addons. The stream runs Opus at 510 kbps stereo with every piece of voice-call processing disabled. A lossless tier is on the roadmap.

Route your DAW into the browser (one-time)

The browser can't hear your DAW directly — it listens to an audio input. The trick is a virtual audio device that shows up as both an output (for your DAW) and an input (for Cue).

macOS:

Install BlackHole (free, 2ch build) or Rogue Amoeba's Loopback (paid, nicer routing).
In your DAW, set the master output — or a post-fader send — to the virtual device.
If you also want to hear yourself, make a Multi-Output Device in Audio MIDI Setup (your interface + the virtual device) and output to that.
In Cue's live console, pick the virtual device as the input.

Windows:

Install VB-Cable (free) or VoiceMeeter (free, adds monitoring control).
Set the DAW master output to CABLE Input; pick CABLE Output as the input in Cue.
VoiceMeeter users: route the DAW to a virtual strip and keep your headphones on the hardware out.

48 kHz everywhere saves headaches — set the virtual device and your session to the same rate so nothing resamples behind your back.

Going live

Open the round → go live.
Allow audio access once (that's how the browser lists inputs — there's no microphone involved unless you pick one).
Pick the virtual device, watch the meter move, hit start streaming.
Send nothing new: listeners use the round's existing share links.

While you're live the console shows the level meter, the listener count, the elapsed clock, and a capture check — confirmation that the browser honored stereo and kept echo cancellation, noise suppression and auto-gain off. If a browser quietly re-enables any of them, the console says so instead of letting it eat your mix.

Troubleshooting

Meter not moving → the DAW isn't reaching the virtual device. Check the master output routing and that the session is playing.
Sounds thin or pumping → the capture check will show which processing got re-enabled; restart the stream after re-picking the device.
Listener hears nothing → they need one tap on listen in (browsers require a gesture before audio).
It asked for "microphone" permission → expected; the virtual device is just another input to the browser.