How itdecides.
Six measures crossed over your library, and three moments to act on. Everything is computed on your machine, even offline.
The track,
and the moment.
Liaison reads the structure of both tracks (intro, breaks, outro, 32-beat phrases) and puts three markers on what's playing.
- Start B
The next track starts on the phrase, so its drums land as A's drums leave.
- Bass
You swap the bass right there. The two kicks never fight.
- Out A
Where the current track leaves. Never a gap without drums: that's what empties a floor.
How it finds these markers
- It finds where the drums come in. A 180 Hz low-pass, bar by bar: the intro ends at the first of four full bars in a row.
- It finds where they leave. Same measure, starting from the end. In between, any dip longer than two bars becomes a break.
- It lays the grid. Beat phase from onset alignment, downbeat from the kick, 32-beat phrases.
- It fits everything to the tempo you play. An intro pitched from 119 to 119.2 BPM no longer lasts quite as long: the start point is recomputed, then snapped to the phrase.
About two seconds of work per track, on a separate thread: the widget never freezes. The result stays on disk as long as the file doesn't change.
Six signals,
one score.
Every track in your library is scored against the one playing. The top five rise into the widget, with the reason why.
- Harmony100
- Tempo98
- Timbre84
- Energy88
- Room76
- Trend61
Harmony
Same Camelot code, neighbour or relative: the basslines don't clash.
Tempo
Half and double time understood: a 128 and a 64 mix fine. The gap is given as pitch.
Energy
The step between the two tracks, set against the night's energy curve.
The shape of a night ›Timbre
Brightness, density, warmth. Two tracks at the same BPM can still sound wrong together.
Room
The country, the kind of night and what the guests ask for.
Guest requests by QR ›Trend
Where the night is heading right now.
And it learns: the transitions you play or skip shift its criteria towards yours.
It all runs
on your machine.
No analysis server. That's a choice, with what it gives you and what it costs.
What it gives you
- No network needed. A basement, a marquee, a wedding's overloaded wifi: the engine can't tell.
- No waiting. No queue, no outage on someone else's server in the middle of a set.
- Your library stays home. No file, no listening history is sent. One exception, if you open a guest session: the titles guests can search, deleted 48 h later.
- Suggestions that are yours. They come from your library and follow your choices, not the average of other DJs.
What it costs
- The first read takes time. One to two hours for twenty thousand raw files, once.
- Your processor does the work. In the background, at low priority, and it stops while you mix.
- No crowd wisdom. Liaison doesn't know what other DJs play. For many, that's exactly the point.
Better to say it here than during your second set.
It reads
your software.
The playing track is detected on its own, and your library is read where it lives. Nothing to import.
- Detects
- the loaded track
- Delay
- instant
- Setup
- none with a CDJ, XDJ or DJM on the network
- Detects
- the playing track
- Delay
- about 1.5 s
- Setup
- none
- Detects
- the playing track
- Delay
- instant
- Setup
- Broadcasting on 127.0.0.1:8000
- Detects
- the playing track
- Delay
- about 1.5 s
- Setup
- none
Otherwise, the magnifier
You pick the playing track by hand. It even works with vinyl.