6 min read
What does a sound designer do, day by day?
The credit sounds glamorous. The week is spotting sessions, library searches, layer building and stem exports.
A sound designer builds the non dialogue, non music side of a soundtrack and makes it fit picture. On a large film the role is narrow and specialised. On a short or a documentary it usually absorbs dialogue editing and the mix as well.
A typical week
- Spotting: watch the cut with the director, note every place sound has a job.
- Sourcing: search libraries, pull production sound, book a recording session for what is missing.
- Building: layer and process elements until each moment reads.
- Editing to picture: place, trim and automate everything against the timeline.
- Delivering: hand over organised tracks or stems, correctly labelled.
The part nobody films
File management. A designer spends real hours splitting multitrack recordings into named mono stems, renaming files so they can be found in six months, checking sample rates and building session templates. Getting this wrong costs more time than any creative decision.
Skills that matter
Editing precision, a large mental library of sounds, restraint, and the ability to describe an idea to a director in words. Technical fluency in a DAW is assumed. Knowing how to record your own material is what separates a designer from a librarian.
What gets delivered
Usually organised tracks in the mixer's session, plus effects and ambience stems at the delivery specification: 48 kHz, 24 bit, mono or the required layout, named to the studio's convention. Deliverables that arrive in the wrong sample rate or as interleaved poly files when mono stems were requested get sent back.
The tools on this site handle that last mile in the browser: split a poly recording into named mono stems, merge monos into a multichannel file, remap channels, or convert sample rate before delivery.