Journal·8 September 2026·11 min read
Ubiquity
Can an analog mastering engineer exist everywhere?
Continue reading Close
I. When the website started working
There is a particular kind of bad luck that only happens when something finally goes right.
I had spent parts of the summer on that site. Moving it off a platform that was overcharging me and rebuilding it as something I actually liked. Rewriting every single page. Reading it out loud trying not to sound like an idiot or an arrogant nerd: "Send me any mix you have, I'll make it good." Building it in English, French and Brazilian Portuguese, because after my fourth trip there I had convinced myself that it just made sense. Wiring up the booking flow. Browsing through years of past masters, referencing others from famous engineers I respect, publishing five years of notes, edited and rewritten, all in one place where people could actually read it.
Three days after it went live I got on a plane, and while I was in the air the thing started working. Three enquiries in four days, from the United States and from Europe. A fourth soon arrived, someone wanting an old reel digitised, which I mention only because it is the one request a mastering rack in Brussels cannot help with either.
Here is the detail that turned out to matter. They did not mention the analog chain, but it's actually one of my unique selling points. They had listened to the studio playlist and written to me about the sound that they heard and liked. It was nice. They wanted what they had heard in those tracks. Nobody asked what it was made on. I found that interesting, because I am the opposite: a musician by trade who has since discovered a passion for classic analog studio gear, and who cannot hear a record he likes without asking what the sound went through.
I did not notice how important that analog thing was until much later. At the time all I could see was that every piece of equipment I had just spent my summer advertising was sitting in a rack nine thousand kilometres behind me. And my own site promises a first master within three days.
II. The dilemma
The easy read on this is that it was a logistics problem. It was not. Logistics have solutions: you wait, you reschedule, you tell people you are back on the fifteenth.
What made it uncomfortable is that it was a question about honesty.
I could say no. Tell them I am travelling, ask them to wait three weeks, and protect the promise exactly as written. That is the defensible answer, and it is the one most engineers I respect would give. Except that I am new in the business and I would have lost these clients had I told them I was travelling.
Or I could take the work and do it in the box, on a laptop, in a rented flat, on consumer market headphones. Which would mean that the thing I had spent years putting together, and just spent an entire summer promising in three languages was, on this particular record, not strictly true.
I sat with that for longer than I want to admit, and eventually noticed that I had framed it wrong.
I had been treating "analog mastering" as a description of my equipment. But no client has ever asked me for a Neve or a vari-mu compressor. They wanted "that" sound. They ask for warmth, for glue, for the mix to stop sounding like a session and start sounding like a record. The hardware is how I have learned to get there. It is not the thing itself. The people writing to me that week had just demonstrated that, without meaning to.
That distinction sounds like a convenient piece of self-justification, and I was suspicious of it for exactly that reason. So I decided to test it rather than believe it.
III. Rebuilding the studio in a laptop
The first two days went entirely on the laptop itself.
I had assumed this part would be trivial. It was not. My DAW does not behave, out of the box, the way I have made it behave over years of daily use, and I had genuinely forgotten how much of that was mine rather than default. How plugin windows behave. Being able to see just the control I need, one at a time. All the small things you stop seeing because you know your workflows and your hands know them by heart. Two full days disappeared into making a computer feel like my room.
Then I spent two more days actually testing.
For the past year I have kept my mastering method in a repository. Not just session files: a running log of the chain, every stage in order, what each unit is doing and why, what the calibration reference is, what changed and on what date. So many versions, so many tweaks. I started keeping it because I was tired of losing settings, and because my mentor had made it very clear, and I agreed with him, that a decision you cannot reproduce is not really a decision. I thought I was documenting for consistency. But not only.
I was also documenting for portability, and I did not find that out until I actually needed it.
So I rebuilt it stage by stage, and where a hardware stage had no software equivalent I had to be inventive rather than 100% faithful. Some of my hardware simply has no plugin standing in for it. The vari-mu was the easy one, because the software version was chosen years ago precisely for how closely it tracks the unit. Others were approximations I had to arrive at by ear. I printed alternative chains side by side and listened. I went through presets I thought might suit these particular songs, which is not something I ever do at home, because at home I do not need to.
And then I ran the records through it, and here is the honest result.
They came out well. The masters were right for the tracks and the clients were happy. What they were not was "the same". Not the exact same character I would have had in five minutes at home by simply running the track through the rack with my good old default settings. Similar in intent, slightly different in colour, and I am not going to pretend otherwise in an article about honesty. It also did not help that I was working without my usual headphones, without my converters, in a rented flat with no acoustic treatment, jet-lagged, on the wrong side of the Atlantic.
The useful part is what I did once I accepted that. I stopped trying to make the plugins impersonate my hardware, which is a game you cannot win in four days, and went back to asking the only question that actually matters: what does this track need? Then I chose the tools that got it there.
A developer friend once told me that everything starts to look like a nail when the only thing you own is a hammer. My rack is a very good hammer. It is so good that I had stopped noticing how often I was reaching for it before I had finished listening.
So the gear was doing more than I had hoped, and less than I feared. The thing that made those masters good was still the method. The order of operations, the calibration, the decision about where the record needed to end up. The chain executes that beautifully and I would still rather have it. It was not the part generating the decisions.
Years of buying gear, and the most valuable thing I owned turned out to be a text file.
IV. The 60-second sample
That left one honest problem. I thought the laptop version was good. Thinking so is not the same as the client hearing it, and the client had booked a promise I was quietly modifying.
So I did the only thing that seemed fair. Before any money changed hands, I offered to master sixty seconds of the track and sent it over.
No commitment, no invoice, nothing to decline politely. Just: here is what I would do to your record. If this is right, we continue. If it is not, we shake hands and you have lost nothing. Or we talk again when I get home.
It came back positive. On one of them, an EDM track with a great deal of energy in it, it came back with more than I had asked for: a reference track, and a request to remix from stems on top of the mastering I had quoted for. The sample had not just protected the job. It had opened it up.
I expected the whole thing to feel like an apology. It did not. It solved something I had been getting wrong for years.
Mastering is bought almost entirely on trust, trust that you understand the artist's vision and respect it truthfully, and trust is the hardest thing to establish remotely with someone who has never heard your room. Every mechanism the industry uses to bridge that gap is a proxy. Credits are a proxy. A portfolio is a proxy: it proves I made those records sound good, not that I will make yours sound good. Even the analog chain is a proxy, a shorthand for quality the client takes on faith, because not everybody can hear a transformer. They can only hear the result.
Sixty seconds of their own music is not a proxy. It is the actual thing, in miniature. It's a promise. One that has to be respected.
The 60-second test master has since become a permanent part of how I work, and it is on the website now. I did not add it to my services because I was travelling, but because it turned out to be a better way to start any new project, whether I am in Brussels or anywhere else.
V. Ubiquity is not geography
I left thinking the question was whether I could work from anywhere. That is a boring question and the answer is obviously yes, everyone can, that is what laptops are.
The real question was whether I could be the same engineer from anywhere. Not whether I could reproduce the same colour, because in four days on a laptop I could not. Whether the judgment behind the sound travels, or whether it stays in the rack in Brussels with the power off.
The judgment travels. The character is a longer job, and I now think it is a solvable one. Not by finding better impersonations of my hardware, but by learning these tools properly, on their own terms, until I can get where a record needs to go with them as directly as I do with the rack. There are things they will do that my chain cannot. Those are two different claims and only the second one is about equipment.
The signal path is available to anyone with the budget. What is not available is the specific set of decisions I make about where a record needs to end up, and those live in my ears, in a decade of listening, in the incredible training my mentor gave me and, when I am honest about it, in a documented method I can carry in a repository. That is the part clients were writing to me about, even though none of them put it that way.
So this is what ubiquity actually means to me now, in a job I learn a bit more about every day. Not being able to work from anywhere. Being able to deliver the same artistic judgment wherever you are, and being straight with people about what does not come with you.
The analog chain is my signature. My ritual and my ears are my instruments.
And I keep coming back to this, which is the closest thing I have to a working definition of the job:
To me, great mastering isn't just defined by where the signal travels. It's defined by how faithfully the artist's intention survives the journey, regardless of how good your gear or your reputation is.
I found that out because a website started working three days into a three-week trip I had never planned to work through, on the wrong continent. I would not have found it out any other way.
Thanks for reading.
K.