Bringing Windows audio within reach

01 / WINDOWS AUDIO

Turning scattered desktop sound into clear channels

We built two independent connections. The EUCON edition serves environments such as Avid S3 and Avid Control. The Mackie Control edition connects over MIDI to controllers in MCU mode. Both turn the Windows main output, input devices and active applications into stable logical channels.

Faders control level, encoders control pan, and mute, solo, selection and meters remain synchronized in both directions. The list changes as applications come and go, but a fader under your hand cannot suddenly inherit another app. All of those internal rules should add up to one uncomplicated feeling: the tool always knows what you are controlling.

02 / UAD CONSOLE × EUCON

A workflow I had waited years to use

UAD Console has long been central to my studio, yet its documented parameter workflow still centres on mouse and keyboard control, without a direct EUCON control path into Console. Every on-screen fader and encoder was familiar, but always separated from my hands by a mouse. Bringing the Apollo software mixer onto a physical surface was more than a feature request. It had been a personal ambition for years.

UAD Console Bridge for EUCON finally makes it tangible. Channel faders, mono and stereo pan, mute, solo, sends, input preamps, UNISON and Inserts plug-ins, the control room and meters are arranged as structures EUCON can understand. Parameters retain real units such as dB and Hz, while touch, turning, banking and state feedback correspond as closely as possible to Console.

Apollo DSP and UAD Console continue to process the audio; the bridge handles control and feedback. The goal is not merely to remote-control an app. It is to bring hardware into the existing recording and mixing flow: move a fader and hear the result, turn an encoder and see its value, with hands, eyes and ears receiving the same answer.

03 / THE MAKING

The hard part was not making it move once

Early prototypes could change volume quickly. The real work was turning one successful gesture into something dependable every day. A fader cannot wait until release before sending. A meter cannot be deliberately slowed for convenience. Software feedback cannot force a touched motor fader back to an older value. Reconnection, application changes, driver updates and startup order should not demand a ritual of restarts.

We separated continuous control from structural change. Volume, pan and plug-in parameters take an immediate path and retain only the newest pending position, so stale commands cannot chase a gesture. Plug-in loading and configuration keep deliberate selection, confirmation and state checks. Stable channel identity, touch protection, reconnection and control scopes guard the target and its boundaries.

This engineering is not there to make the interface look complicated. Its purpose is precisely the opposite: to let the bridge disappear so that attention can remain on the sound.