Headlink puts gain and 48V for your WING onto LV1's own
channel strip — where your hand already is. No mapping, no overlay window,
nothing to configure.
64
channels
0.1 s
repatch follow
0
to configure
The controls — LV1's channel stripThe device — LV1's System Inventory
Both of these are eMotion LV1. The WING is listed in
LV1's own inventory as an I/O device, and its preamps appear on LV1's own strip.
Headlink is what makes them appear.
The difference
An overlay makes you go and find the channel.
Both approaches end up changing the same preamp. Only one of them fits
what you are doing during a soundcheck.
Overlay app
Map every channel to a preamp, by hand, before you start
Notice a channel needs gain
Bring the overlay window forward
Find that channel in the overlay
Adjust it there
Go back to the mixer
Six steps, and a mapping table to maintain.
Headlink
Turn the gain knob on the strip
One. The mapping is read from the desk.
On the rig
Mix on the strip. Check the patch when you need it.
Day to day you never open Headlink — you turn the gain knob where it already
is. The window is there for the question LV1 can't answer: which preamp is
actually behind this input.
A working session — LV1 behind, Headlink over it. Both showing the same desk.
What it does
It asks the console, instead of asking you.
The card cannot tell LV1 which preamp feeds which input, so most tools make that
your problem. Headlink reads it from the WING directly — and keeps reading it.
Controls on the strip
Gain and 48V appear on LV1's own channel strip, drawn by LV1. Nothing floats
over the mixer and nothing has to be brought forward.
LV1 channel strip · gain · 48V
Finds the desk itself
Broadcasts for the console on every network it can see, and takes its address,
model and firmware from the reply. No IP to type.
autodiscovery · no address to enter
Follows repatching
Reads which physical input feeds each card channel and re-reads it when you
change the routing mid-session. The strip follows.
~0.1 s · no restart
Every input its own range
A local XLR and an AES50 stagebox have different ranges and different detents.
Both are read from the console, per channel.
−2.5…45.0 / 2.50 dB
−3.0…45.5 / 0.50 dB
Works both ways
Turn it on the strip and the preamp moves. Turn it on the desk and the strip
follows, quantised to whatever the console actually applied.
LV1 → desk · desk → LV1
Names, not numbers
Shows what the console calls each input — Kick, Amb L, Lead Vox — read off
the desk, not typed in again. Unnamed inputs keep their connector label.
read from the desk · never renumbered
Knows a stereo pair
A linked pair shares one head amp, so both legs move together. Headlink marks
which leg owns it — so two channels showing one figure reads as correct, not broken.
L / R marked · follows the desk instantly
Reversible, and honest
The stock Waves module is kept beside ours and put back with one click. If the
desk stops answering, Headlink says so instead of showing a stale number.
one-click uninstall · fails to pass-through
Read from the console: the desk's own name for every input, which leg of a stereo
pair owns the head amp, and the range that source actually has.
Gain structure
See the preamp clip, not just hear it.
LV1's channel strip has nowhere to put an input meter — there is no
metering in the interface a device gets to fill in. So the level you are
setting the gain against is the one number you cannot see.
Read from the desk's own meters, at the physical input
— ahead of everything LV1 does.
Measured where it matters
At the input itself, not after the mix. That is the difference between
“this channel is loud” and “this preamp is running out of
room” — and nothing downstream can undo a clipped converter.
The peak is held
Meter frames arrive about twenty times a second and a window repaints
slower than that. A transient short enough to fall between two repaints is
exactly the one that clips, so the peak is caught and held.
Clip latches
A flag stays up after the fact, so you can look up at the end of a song
and see which inputs were in trouble — instead of needing to have been
watching that channel at the moment it happened.
Setup
Three steps, and it finds the desk itself.
No installer to run, no drivers, nothing to unpack. One application that sets
itself up and can put everything back exactly as it was.
At a glance
It tells you when it can't help.
The tray mark carries one job: whether Headlink is actually working right now.
Colour only — the shape never changes, so you read it without looking.
Searching
Looking for the desk
Linked
Gain and 48V are live
Attention
Running, without preamp control
Link lost
The desk stopped answering
Item
Detail
Console
Behringer WING · WING Rack · WING Compact
Host
Waves eMotion LV1 17.x (Windows 10 / 11)
Connection
WSG card + network to the desk — autodiscovered
Controls
Gain, 48V — both directions
Channels
64
Sources
Local XLR, AES50 A/B/C, StageConnect
On the desk
nothing installed — OSC over your existing network
Uninstall
one click; the stock Waves module is kept beside it
Coming soon
In final testing, on real rigs.
Headlink is running today on a WING Rack
driving eMotion LV1 through a WSG card — all 64 channels, both directions.
Pricing and a download will be posted here once it ships.
Headlink is an independent product. It is not made by, endorsed by,
or affiliated with Waves Audio or Music Tribe. WING and eMotion LV1 are the trademarks
of their respective owners.
