What works with your DJ software.
The Playback Bridge does as much as your DJ software will let it. Some programs can be driven and read back in full; others accept commands but tell us nothing. Rather than claim one number for all of them, here is the honest breakdown — including what we do not support yet.
Three programs are tested and working.
These have been run against real hardware, not just written for.
VirtualDJ
The deepest integration we have. VenueCue can load an exact track, watch it land, read the decks back, fill VirtualDJ’s own Automix queue, hand over a karaoke rotation, and mark items Played from what was genuinely on air.
Mixxx
Full live control and real deck, mixer and on-air reporting, through a VenueCue mapping built into the Bridge. Mixxx cannot be handed a specific track, so you load the music and VenueCue drives and confirms it.
djay Pro
More than the usual MIDI control, because djay keeps a library the Bridge can read: match your own tracks, import your collection, load a chosen song from a playlist, and keep the night moving. djay does not report its mixer, so VenueCue shows what djay started rather than claiming to know what the room heard.
Serato, Traktor and rekordbox Not yet tested
None of these three offers a way in for an app like VenueCue, so the Bridge appears to them as an ordinary MIDI controller: you map it once in your software’s MIDI learn, and you get play, cue and the teaching speed control from your phone. That map is written and documented — but we have not yet tested it against Serato, Traktor or rekordbox on real hardware, so we are not going to tell you it is supported.
Serato is next. It is the first thing we take on after launch. We are not promising particular features there yet, because we have not finished looking at what Serato makes possible — but it is the one we are working on, and it is where the deeper work goes first.
Everything, per program.
| VirtualDJ | Mixxx | djay Pro | Serato / Traktor / rekordbox | |
|---|---|---|---|---|
| Your music | ||||
| Search and match your own library | ✓ | ✓ | ✓ | — |
| Import your library into VenueCue | ✓ | ✓ | ✓ | — |
| Load a specific chosen song | ✓ | — | ✓ from a playlist | — |
| Control from your phone | ||||
| Play | ✓ | ✓ | ✓ | ✓ |
| Pause | ✓ | ✓ | Play is a toggle | ✓ |
| Cue / back to the start | ✓ | ✓ | ✓ | ✓ |
| Teaching speed control | ✓ | ✓ | ✓ | ✓ |
| Keylock (pitch held when slowed) | ✓ | ✓ | — | — |
| What VenueCue can see | ||||
| Which deck is loaded and playing | ✓ | ✓ | ✓ | — |
| The name of the track playing | ✓ | ✓ | ✓ | — |
| Volume and crossfader | ✓ | ✓ | — | — |
| Whether the room can actually hear it | ✓ | ✓ | — | — |
| A song you loaded yourself | ✓ | ✓ | — | — |
| Keeping the night moving | ||||
| Cue the next song automatically | ✓ | — | ✓ | — |
| Fill your software’s own queue | ✓ Automix | — | — | — |
| Mark items Played automatically | ✓ | ✓ | — | — |
A few rows depend on your own setup rather than on the program: library matching needs VenueCue to be able to read your library file, djay’s chosen-song loading needs the playlist you named to exist, and the MIDI programs report a deck’s play state only if you set up a feedback port. VenueCue reports each of these from whether it is really there, never from which program you told us you run.
Two limits worth stating plainly. djay, Serato, Traktor and rekordbox cannot tell VenueCue whether a track is audible — that is a question about your mixer, and none of them expose one — so on those programs VenueCue will not mark anything Played on its own, and you stay in charge of the history. And djay has no separate play and pause: its Play button is a toggle, so VenueCue uses Cue to put a deck back to a known, stopped state.
Free, for Windows and macOS. The Bridge runs on your own computer and talks to VenueCue there — never over the internet.