Stems

Stems are submixes of the soundtrack grouped by category, most commonly dialogue, music, and effects.

What this is about

A finished stereo mix is a sealed box; stems keep the lid open. With DME stems — dialogue, music, effects — a broadcaster can build a dubbed version, a cutdown can swap the music, and a trailer house can pull clean effects. Stems are printed at the end of the mix session through the same processing as the master, so summing them reproduces the mix. Delivery specs for broadcast and streaming routinely require them, and even small productions benefit: the client recut next year will ask for exactly this.

A term only helps when everyone on set means the same thing by it — so what follows is how it is used, not a dictionary definition.

What runs differently here

Where this differs from the general case:

  • DME — dialogue, music, effects — is the minimum useful split
  • Print stems through the master chain so their sum equals the mix
  • Archive stems with the project; recuts and versions depend on them

With TillyGen

Listing stems as a deliverable in TillyGen's plan means the mix session prints them on the day, not as a paid re-open two months later.

Change one constraint and the consequences travel through the whole plan: affected shots are flagged, the call sheet is regenerated, and nobody keeps working from yesterday's version.

Frequently asked

Why deliver stems if the mix is approved?

Because the next version is coming. Dubs, cutdowns, and social edits all start from stems; without them, someone pays to reopen the full session.

How long does it take to get started with TillyGen?

A first project takes under an hour to set up. There is no configuration phase in which templates and fields have to be defined before the tool produces anything.

Can the results be exported?

Yes — as PDF for the crew, CSV for downstream systems and through the API for anything automated. The plan stays the source; the exports are views of it.