Skip to content

Owen Iraoya· Mastering Engineer

I See Music.

Building rooms you can feel.

measuring device

Chapter I

Sound

Mastering is not making things louder. It is deciding what a room will do to a record before the room ever hears it.

The mastering engineer moves around. From studio monitors through a speaker on the bus through an open-window car to £12 earbuds and to club equipment with more headroom than brains. Each of these is a different room, each of these will argue with your mix

And the work prepares for the argument. In which part of the spectrum your bass line will be disappearing, in which part of the frequency range your sibilant sounds will become knives, which of the reverbs' tails will survive 96kbps and which will turn into sludge. You're not working on some polishing tool. You're arguing with the rooms you will never see

That's why a head becomes the emblem of the site rather than the console or the wave form display. The last room any sound track will find itself is inside someone's head, and this is the only room which wasn't included in the specs.

Chapter II

Systems

Behind every immersive piece is a queue, a cache, and something that has to not fall over at three in the morning.

The other, less glamorous side of interactive audio consists of transcoding assets and delivering them, handling a disconnection during the performance of a piece, preserving state while opening the same installation on two separate devices from the same user. Budgets for latency are in single-digit milliseconds and then spent carelessly with a single, unindexed query.

All of this I do as well. The backend infrastructure, the streaming pipeline, the dependable and solid technology that allows the front-end to take risks. Why a generative ambient loop could be played for forty minutes non-stop, no clicks involved, is not because of the synthesis – that is the easy part. It is everything upstream not interrupting the flow.

Engineering and mastering are the same craft applied to a different medium.

Chapter III

Signal

Built for blind, deaf and neurodivergent minds — which means built to hold attention through repetition and change, not through spectacle.

An audio-reactive piece that only works if you can hear it is not an audio-reactive piece. It is a light show with a soundtrack. So the reactivity here runs both ways: the visuals are driven by real analysis of the audio, and they keep moving to a generative curve when the audio is off, so the form is never dead and never dependent.

For deaf visitors every non-speech cue is described in text, because atmosphere is content. For blind visitors the sequence has a narrated alternative that carries the same story rather than an alt attribute that apologises for it. For visitors who need less motion, the acts become held states — the same three moments, cross-faded instead of travelled.

Attention is kept by rhythm: something repeats, something changes, the brain stays awake. That is a mastering instinct and an accessibility principle at the same time, and I have never been able to tell them apart. The craft is a gift from God; the least I can do is not waste it on people who were never going to be let in.

Where next

Does this make someone feel the sound?

It is the only question worth asking of any of it. If a feature does not serve the listener — literal or figurative — it gets cut. What follows is the work that survived.