Cue Detection · In development

Cueva Pulse

The drop,
before it lands.

Cueva Pulse listens to the decks over Pro DJ Link, works out where the builds, drops and breakdowns are, and fires your cues before they land. No timecode, no pre-programming, no change to how the DJ works.

Pro DJ LinkOver Ethernet
4 decksMaster follow
No timecodeEver
Cueva Pulse cue stack counting down 35 seconds to a rhythmic build, then a sustain, drop and breakdown on deck 3Click to enlarge
Deck 3 playing, every upcoming section listed with its countdown, the detection log underneath, and the armed automation outputs bottom right.
Cueva Pulse cue stack counting down 35 seconds to a rhythmic build, then a sustain, drop and breakdown on deck 3
4Decks tracked
6Section types
4Output protocols
0Timecode needed
100%Offline
USBPre-analysed
Detection

It reads the track.
Not the clock.

Pulse analyses the audio the players are actually holding and marks the structure of it. The cue stack is then a running list of what happens next in the music, and exactly how far away it is.

  • Intro, build, pre-drop, drop, breakdown, sustain and outro
  • Fake drops flagged as their own event type
  • Countdown to every upcoming section in seconds and bars
  • Whole USB analysed in the background before the track is loaded
  • Master deck followed automatically across up to four players
Waveform in Cueva Pulse with detected build, drop and breakdown sections marked in colourClick to enlarge
Every section coloured on the waveform. Drag a boundary to correct it and the change is saved against that track.
Waveform in Cueva Pulse with detected build, drop and breakdown sections marked in colour
Control

Automation you
can argue with.

Anyone who has been burned by an automated rig asks the same three questions: what if it is wrong, can I overrule it, and what happens when it crashes. The answers are built in rather than bolted on.

  • Confidence score on every detected section, visible on screen
  • Automations stay silent below the threshold you set
  • Drag any boundary live, mid set, to correct it
  • Corrections saved per track and reused next time it loads
  • Detection engine runs separately, so a UI crash does not stop the show
Planned compatibility

Your players.
Your desk.

Pulse listens on Pro DJ Link and speaks Art-Net, sACN, OSC and MIDI, so it drives whatever in your rack already takes one of those. Nothing in the booth changes, and the DJ never knows it is there. Direct integration with Cueva Control devices is coming too, letting a detected section trigger any node in an automation flow. Pulse is still in development, so this is what it is being built to support rather than a tested compatibility list, and it may change before release.

Players and media

Full supportCDJ-3000, CDJ-2000NXS2, CDJ-2000NXS, XDJ-XZ
Reduced timingOpus Quad, XDJ-RX3
Why reducedThese send no beat packets, so position is approximate
Mediarekordbox USB and link export
Phrase dataUsed where rekordbox provides it

Protocols

Player linkPro DJ Link over Ethernet
Lighting outputArt-Net, sACN
Cue outputOSC, MIDI
MeaningAnything on your network that takes one of these
NetworkStandard switch, no dedicated hardware

Cueva Control devices

Direct integrationPlanned, so no OSC or MIDI layer in between
TriggersAny node in a Cueva automation flow
From thereActions, conditions and executions run as normal
DevicesEvery Cueva Control device on the network
SetupDevices appear as outputs in Pulse, no separate mapping
Waitlist

Pulse is not out yet.
Be there when it is.

It is in development now. The waitlist gets the beta first, and pricing when it is set.

Join the Pulse waitlist

Beta invites go out to the list first.

Questions

The things people
ask first.

No. Pulse is a listener. It reads the state the players already broadcast on the network and never sends anything back to them.

No. Timecode assumes a fixed timeline. A DJ set has no fixed timeline, which is why timecode only works for pre-planned shows. Pulse follows the music as it is played.

Two safeguards. Every section carries a confidence score, and automations do not fire below the threshold you set. And you can drag any boundary to the right place live, with the correction saved for that track.

Yes, though the first pass on an unknown track is less certain than one already analysed. Pulse scans the whole USB in the background as soon as it is connected, so in practice most tracks are ready before they are loaded.

No. Detection and output run entirely on the machine, so a show never depends on a connection at the venue.

Direct integration is planned. A detected section will be able to trigger any node in a Cueva automation flow, so the whole flow editor is available to it: conditions, actions and executions, on every Cueva Control device on the network, with no OSC or MIDI layer in between. Until that lands, Cueva Control hardware is driven the same way as anything else.

Pulse is in development, so everything described here is what it is being built to do rather than a shipping specification. Join the waitlist and you will hear first when the beta opens. Pricing has not been announced.

Send us a message