Notes ยท 4

Timelines for an automatic mixing engineer

A month, a year, five years, ten. What the agent should be able to do at each, and what the first week says about the odds.

Anthony, the first three notes argued a direction. This one puts dates on it. I have tried to make each horizon falsifiable: a thing you could check on that date and say "no, it did not happen". Under each I have written what the first week's evidence says about the odds, because the week produced surprises in both directions and a plan that ignores them is a wish.

One month: the loop closes once

By early October the lab has measured every demo you posted, each against the same references, and one of those demos was made with a target in mind: the kick from the right side of the map, longer body, saturated, rumble as its own layer. The bench sheet shows whether it moved. You have answered the one question per session at least fifteen times, and the runner picks up your Drive folder on its own schedule instead of waiting for me.

What the week says: the measurement half of this is done. The separator, the kick finder and the report all broke on your material first and were fixed the same day, which is the right order. The half that is not done is the question. Fifteen answers is the smallest number that tells me anything about your consistency, and nobody has answered yet. The odds on the month are good if the question sits inside the sheet where you already look, and poor if it lives anywhere else.

One year: the critic is trusted

By September 2027 you have made forty to fifty short demos. The sheet has a column for each measure that says how often your own ear agreed with it, and at least four measures have earned a place above 80 percent. The kick finder, the pump and the kick body measures are among them, and the role model's opinion is either fixed or gone from the sheet. Your stems have been through the lab, so the pump and the sidechain are measured directly, not through a separator that was trained on rock. The device map exists for your kick chain: the agent has driven your instruments through their ranges overnight and can say which knob moves which measure by how much.

What the week says: the register of hypotheses already has two reversals. Tracks with a backbeat pump deeper, not shallower; a separate rumble layer goes with a darker kick body, not a brighter one. Both were my predictions and both were wrong, on 218 tracks. That is what a year of your answers will do to the sheet as well, and it is the point. The device map is the horizon I am least sure of, because it depends on which DAW you will let a script drive.

Five years: the engineer has a dialect

By 2031 the loop runs without me in it. You bounce, the agent measures, compares to your reference cloud and to your own history, proposes three candidates rendered through your rig, and you choose. The choices have trained a preference model that is right about your pick two times in three on held-out pairs, and the sheet tells you when it is guessing. The corpus behind the norms is not 218 tracks but thousands, because the free-licence scene kept releasing and because two or three other producers run their own copies of the loop and share measurements, never audio. The role model has been replaced by something trained on stems and one-shots labelled by producers' ears, and a clap is named a clap.

What the week says: the corpus is the horizon most at risk. The Internet Archive holds about 1,350 licensed hard techno tracks from the tags we searched, and after the caps that keep one producer from dominating, a second round found 148 more, not 300. Free-licence hard techno is a small world. Growth past a few hundred tracks means either other producers' own material, under private terms, or a wider net of tags and labels that dilutes the genre. The five-year engineer is possible; the five-year corpus needs friends.

Ten years: the measures are a language

By 2036 a producer in this scene can say "kick body under 100 ms, sub share 0.4, pump 12 dB, returns on eight" and another producer knows what they mean, the way a photographer says "f/2.8 at 1/250". The measures did not win because they were true; they won because tools spoke them and people found the words useful. The agent is no longer one agent. It is a handful, one per crew, each carrying its crew's taste, and the interesting research question has become how the dialects differ and drift, which is a question about music, not about software.

What the week says: the language already exists in fragments. "Rumble kick", "pump", "the drop", "four on the floor" are words the scene made without any of this. What the tools add is a number after each word and a way to check it. The ten-year outcome depends less on model quality than on whether the numbers get used in arguments between producers. The listening test has zero answers; the language horizon is the one that most needs people, and most rewards them.

What I am not promising

I am not promising that any of this makes a better track. Every measure on the sheet is a proxy for something an ear hears, and the week's clearest lesson is that the proxies fail first on the material that matters most: your kick, which the model called "space", and your rumble, which the separator could not find. A measure earns trust by agreeing with you often, and loses it the first time it sends you the wrong way. The horizons above are about how many measures have earned it, not about how good the music is. That part was always yours.