Nobody explains the revision cycle before a composer's first real project. Music school teaches writing. It doesn't teach that a "final" cue might come back four more times, that file names will multiply into a small crisis if there's no system, or that notes can keep arriving even after everyone agreed a cue was locked. Composers learn this the hard way, usually on a deadline, usually more than once.

The problem isn't that revisions happen — they always do. The problem is treating revision as an open-ended obligation instead of a scoped phase of the job with its own structure, like tracking or mixing. An unscoped process expands to fill whatever time is left, and then some.

Versioning: The Small Discipline That Saves the Big One

The most common failure is invisible until it isn't: a folder full of files named cue_final.wav, cue_final_v2.wav, cue_final_FINAL.wav, cue_final_FINAL_notes.wav, and no way to tell which one is actually in the cut without opening each one. A simple sequential system — cue_v01, cue_v02, with a one-line changelog for what changed between them — costs almost nothing to maintain and eliminates the single most common source of delivery errors: the wrong version making it to picture.

Stems make this stricter, not looser. Every stem in a revision needs to move together — if the melody stem gets a new take, every other stem locked to it needs the same version number, or a mix engineer downstream will combine mismatched versions without knowing it. Version discipline on one instrument is a habit. Version discipline across a full stem stack is a system, and it has to be built before the first revision arrives, not during it.

Scoping the Cycle Itself

The other half of the discipline is upstream of the notes altogether: agreeing, before writing begins, on how many revision rounds are included in the scope of the project, and what counts as a revision versus a new request. Two rounds of notes on an existing cue is revision. A request for a completely different approach after the cue was approved is a new cue, and it deserves a conversation about scope and timeline, not a silent absorption into unpaid overtime.

This isn't about being difficult — directors and editors generally respect a composer who's clear about process, because it means the composer is thinking about the project as a whole, not just the next email. The composers who protect their revision phase with real structure are, paradoxically, often easier to work with, because everyone knows what to expect and when.

None of this makes the notes stop coming. It just makes each round faster to survive — and having source material flexible enough to reshape quickly, rather than rebuilt from scratch, is what makes a fast revision possible in the first place.

Presets For Continua - NOIR vol. 2 is a collection of dark, unresolved tones — built for the scenes that keep coming back for one more pass, and flexible enough to reshape fast when they do. Explore it at sonalsystem.com

More on composition, sound design, and the business of music in the Frequencies archive.