Most descriptions of a mix template treat it as a time saver. Build the session once, save it, and skip the setup next time.
That undersells it by a wide margin. A mix template is the thing that decides whether the last stage of a project is a single export pass or an evening of manual ones, because everything downstream of the mix selects its content by routing. Get the structure right and a stem delivery is a button. Get it wrong and every delivery is a fresh act of archaeology, no matter how good the mix was.
What a Mix Template Actually Is
A template is not a collection of tracks. It is a set of decisions about where audio flows, encoded once so you never make those decisions under time pressure again.
Four things live inside it.
The bus hierarchy. How individual tracks collect into groups, and how groups collect into the mix.
The routing assignments. What puts each track into its correct place in that hierarchy, on arrival rather than later.
The naming convention. What makes the session readable to someone who is not you, including you in six months.
The colour scheme. What makes it readable at a glance rather than by reading.
What a template is not is a preference about plugins. A template that arrives with a compressor on every bus is a starting mix, not a structure, and it will fight you on every song that does not want that compressor. The structure should be neutral about the sound and opinionated about the flow.
The Bus Hierarchy, From the Bottom Up
The mechanic itself is two moves. Create a stereo aux input, set its input to an internal bus, then change the output of every track that belongs to that group from the master to the same bus. The aux is now the group, and its fader moves all of them. New tracks come from Track > New or Shift+Cmd+N, and buses can be created straight from the mixer without opening I/O Setup at all.
That part is well covered everywhere. The part that separates a professional session from a tidy one is that the hierarchy has more than one level. A session where forty tracks all output to the mix bus is technically routed and practically unusable, because there is no stage at which you can grab the drums as one thing.
| Stage | What collects into it | Why it exists as its own stage |
|---|---|---|
| Source tracks | Individual recorded or delivered files | The only place edits and clip gain happen |
| Instrument sub buses | Kicks, snares, toms, overheads, room mics | Balance inside one instrument without touching anything else |
| Section buses | Drum shells, cymbals, backing vocals, guitar layers | The level at which most mix moves actually happen |
| Department buses | Drums, bass, guitars, keys, synths, vocals, effects | This is what a stem is, and where the delivery gets defined |
| Group buses | Rhythm section, instruments, lead and backing vocals | Broad balance decisions in one move rather than twelve |
| Master instrument bus | Everything that is not vocals | Instrumental deliverable exists without rebuilding anything |
| Mix bus | The full mix | Master processing applies once, to everything, in a known place |
A published review by London mixing and mastering engineer Ed Thorne walks through this shape on a real session: kicks and snares into a shells bus, shells into a drum bus, drums into a bus that also takes bass and percussion, and that into a master instrument bus alongside acoustics, guitars, pianos, strings and effects, with vocals running a parallel hierarchy of leads, doubles, harmonies, backing vocals and adlibs. His full review is worth reading for how the structure behaves in practice rather than in theory.
A Bus Map You Can Rebuild in Ten Minutes
Most searches for a mix template are looking for a file to open. A file cannot explain itself, so here is the map instead, which is the part worth copying. Names are illustrative and the convention matters more than the specific words: buses in capitals, source tracks in mixed case, so you can tell what something is from its name alone.
| Bus | What routes into it |
|---|---|
| KICK, SNARE, TOMS, OH, ROOM | The individual mics for each drum element |
| SHELLS | KICK, SNARE, TOMS |
| DRUMS | SHELLS, OH, ROOM, plus loops and samples |
| BASS, GUITARS, KEYS, SYNTHS, FX | Their own source tracks and sub buses, with FX collecting the effect returns |
| LEAD VOX, BVOX, ADLIBS | The individual vocal takes and doubles |
| VOCALS | LEAD VOX, BVOX, ADLIBS |
| INSTRUMENTS | DRUMS, BASS, GUITARS, KEYS, SYNTHS, FX |
| MIX | INSTRUMENTS, VOCALS |
Read the right hand column upwards and you have the deliverables. INSTRUMENTS is the instrumental, VOCALS is the a cappella, and the six buses feeding INSTRUMENTS are the stem set most clients ask for, which is why a typical stem delivery lands at somewhere between six and ten files rather than forty, a figure Sound on Sound's guide to creating stems in Pro Tools also gives as the working norm, checked August 2026.
Colour follows the same logic. A per element convention, so kick and snare are always the same colour in every session and buses are always distinct from source tracks, is what makes a forty track session readable at a glance. Pro Tools also colour codes the bus paths themselves, from version 2023.12 onward and assignable from the track I/O plate since 2024.10, which makes the routing itself visible rather than something you have to click into. Those version details are documented in Production Expert's guide to buses in Pro Tools, checked August 2026.
The department bus row is the one to build carefully, because that row is your stem list. If your clients ask for drums, bass, instruments and vocals, then those four buses have to exist as buses, not as a group of tracks you select by hand on delivery day. Every stem you might ever be asked for should already be a summing point in the template.
Folder Tracks Are Not Buses, and the Difference Matters
Pro Tools folder tracks make sessions dramatically easier to navigate, and they get confused with routing constantly. A basic folder is organisational only: it collapses tracks out of sight and does nothing to the audio. A routing folder is a folder with a bus in it, so it collapses tracks and sums them exactly as an aux input would. They arrived in Pro Tools 2020.3, they nest up to eight layers deep, and send behaviour differs between the two folder types, all documented in Production Expert's reference on folder tracks, checked August 2026.
VCAs sit in the same category of thing that looks like summing and is not. A VCA controls the faders of the tracks assigned to it; no audio passes through it. That makes it excellent for riding a group and useless as a stem, because there is no signal at a VCA to bounce. The rule that resolves all three: a VCA moves faders, a bus carries audio, and only a bus can become a deliverable.
The practical rule is that folders are for your eyes and buses are for the audio. Use folders to make a forty track session look like eight things. Use buses to make those eight things exist as summing points that a stem export can find. When the two align, so each visible folder corresponds to a real bus, the session becomes legible and exportable at the same time, which is the state worth aiming at.
The failure case is a session where the folders are beautifully organised and the routing underneath them is flat. It looks professional and behaves like a pile.
Colour and Naming Are Structure, Not Decoration
Colour coding earns its place because reading is slower than seeing. In a session where drums are always one colour and vocals are always another, you find the thing you want with your eyes rather than by scanning names. The requirement is not that the scheme is pretty, it is that it is the same in every session you open, which is exactly what putting it in the template guarantees.
Naming does the same job for anything that leaves the session. A track called Audio 07 is a file called Audio 07 in a client's download folder, and a client who cannot tell what a file is will ask, which costs more time than naming it would have. Consistent naming also matters for the export categories described below, because a name that follows a pattern is a name a tool can act on.
The deeper reason to fix both in the template is that consistency is what makes a studio's sessions interchangeable. Anyone can open anyone's session and navigate it, which stops being a nice idea and starts being necessary the first time someone is on holiday during a revision round. Our mixing workflow guide covers more of the habits that come out of this.
Where the Structure Breaks: Forty Unnamed Stems at 9pm
The template holds up perfectly until the material arriving does not match it, which is most of the time.
A producer sends a folder of forty files. The names are a mix of Kick_1_v2_final, Audio 7 and bounce_3. Three of the mono files were exported as stereo because that is what their DAW does by default, so they will silently double your track count. Several are full length files with two minutes of silence at the top. Nothing is routed, nothing is coloured, and you can only tell what any of them is by listening.
At that point the template is not the problem, the gap between the delivery and the template is the problem. Every file has to be identified, renamed, coloured, folded to mono where it is fake stereo, stripped of silence where that helps, and routed to the correct bus. That is clerical work that requires professional judgement, which is the worst combination: too skilled to hand off, too repetitive to be worth an engineer's afternoon. The strip silence workflow and the mechanics of batch processing each cover one slice of it.
And it recurs on every session, unchanged, which is the tell that it is a structural problem rather than a bad week.
Where a Stem Quietly Goes Wrong
The failures that reach clients are almost never dramatic. They are one element missing or one element counted twice, and both come from the same source: something in the session reaches the mix bus by a path that no stem bus sees.
A track routed straight to the master. It is in the mix, so the mix sounds right, and it is in no stem, because it never passed through a department bus. Sum the stems and that element is simply gone. This is the single most common reason a stem set does not reconstruct the approved mix.
A shared effects return feeding two departments. One reverb bus fed by both drums and vocals, returning to the master, appears in neither stem if it goes direct, or in both if it is routed into both departments. The fix is a decision rather than a technique: either each department gets its own return, or the shared return goes to one nominated department and everybody knows which.
A sidechain source that is not part of the mix. A ducking trigger or a key input that exists only to control something else will be printed as content if it happens to sit inside a stem bus, and it should not be.
The check that catches all three takes two minutes. Print the stems, import them back onto new tracks, invert the polarity of one and play it against the approved mix. If they cancel to silence, the set is correct. If anything is audible, something is either missing or doubled, and you now know before the client does.
Why the Export Depends Entirely on the Routing
This is the part that makes the template worth building properly, and it is the part most template articles never reach.
A stem export has to decide which tracks belong to each deliverable. There are two ways to make that decision. Select the tracks by hand or by name, which works on this session and breaks on the next one because the next song has thirteen drum tracks instead of twenty and one of them is called Kick Sub rather than Kick. Or select them by routing, which asks a different question: give me everything flowing into the drum bus. That answer is correct on every session, regardless of track count, naming or arrangement.
Routing is the only definition of a stem that transfers between projects. Which means the reliability of your delivery is not a property of your export tool, it is a property of your routing discipline. A studio with consistent buses can define a delivery spec once and run it on everything. A studio without one redefines the spec every time, and the errors that reach clients are almost always from that second group: a missing backing vocal, a stem that does not sum back to the mix, a version printed from the wrong source.
Which is why putting a track into the right bus at the start is not tidiness. It is the thing that makes the delivery stage mechanical rather than manual. The mechanics of that final stage are in our guides to stem export automation and to batch bouncing multiple mixes.
How fMusic Uses the Template You Already Built
fMusic sits on both sides of the structure described above. It populates your template on the way in and reads your routing on the way out.
On import, its on device AI-R engine identifies what each file contains by analysing the audio rather than trusting the file name, alongside a name engine that reads the name where the name is informative. A kick drum saved as Audio 3 is identified as a kick drum. A file called Perc that actually holds a guide vocal is identified as vocals, which is the case name based automation gets wrong silently. From that classification it applies your routing preset, your naming style, your colour scheme and your track heights, folds fake stereo and hard panned files to mono under rules you set, and optionally strips silence. Studios that use their own taxonomy can define custom instrument types, so the tool maps onto your vocabulary rather than imposing one.
On export, categories are defined by routing source rather than by a list of tracks. A category called Drums points at your drum bus, and it selects whatever is flowing into that bus on this particular song. That is what makes a saved delivery spec reusable: build your favourite prints once from your categories and they work on every project, because the category finds the drums wherever they are. The precondition, again, is routing consistency, which is precisely what the import step just applied.
Accuracy is not absolute and Forte does not claim it is. In Ed Thorne's published review of a 27 file session, 25 files were routed correctly with no intervention and two needed fixing: one fill landed in the drum folder rather than the toms bus, and one impact went to strings instead of effects. Two corrections against twenty five is the shape of the trade, and it is the number worth knowing before you buy.
One thing fMusic does not do is design your bus structure. It has no opinion about how your session should be organised and it will not invent a hierarchy for you. It applies the template you built, which means a vague template produces a vague session, faster. The structure is still your work.
fMusic runs on macOS 11 or later with Pro Tools 2024.3 or later or Logic Pro 11 or later, and one licence covers both DAWs.
Frequently Asked Questions
What should a Pro Tools mix template contain?
A bus hierarchy with more than one level, routing assignments that put every track into it, a naming convention, and a colour scheme. Every stem you might be asked to deliver should already exist as a bus. Plugins are optional and usually better left out, because a template is a structure rather than a starting mix.
What is the difference between a bus and a folder track in Pro Tools?
A basic folder track is organisational: it hides and reveals tracks without affecting the audio. A routing folder contains a bus, so it also sums what is inside it. Folders make a session readable, buses make it exportable, and the clearest sessions are the ones where each visible folder corresponds to a real bus.
How many buses does a mix session need?
Enough that every deliverable is a summing point, which for most music work means one bus per instrument department plus a small number of group buses above them. The test is not the count, it is whether you can grab any stem your client might request without selecting tracks by hand.
Why do my stems not add back up to the mix?
Usually because something is reaching the mix bus without passing through any stem bus, so it is present in the mix and absent from every stem. A parallel compression return, a reverb bus routed straight to the master and a print track are the three usual suspects. A hierarchy where everything passes through a department bus before the mix bus makes this failure impossible rather than unlikely.
Should the same template be used for every song?
Yes for the structure, no for the size. Keep the hierarchy, the naming and the colours identical across projects, since that is what makes sessions interchangeable and delivery specs reusable. Track counts and instrument sub buses will vary song to song, and that is what the hierarchy is designed to absorb.
Does a mix template move between machines and studios?
The tracks and plugins travel with the session, but the bus names and path definitions live in I/O Setup, which is machine level rather than session level. Export your I/O Settings and keep them with the template, otherwise a session opened on another rig can arrive with correct routing pointing at paths that have different names, which is a confusing failure because everything looks connected. Doing this once is what makes a template genuinely portable rather than portable in theory.
Does a template work the same way in Logic Pro?
The principles do. The bus hierarchy, the naming and the routing based approach to stems all apply, though the terminology and the mechanics of setting them up differ. Our guide to exporting stems in Logic Pro covers the Logic side of the delivery stage.
Do routing folders need to be open before an automated import runs?
With fMusic, yes. Aux routing folders need to be open in the Edit window before the import runs, otherwise tracks cannot be placed into the correct buses automatically. Ed Thorne flags this in his review as the practical setup note worth knowing in advance.
fMusic identifies incoming files by their audio content, applies your template on import, and prints deliverables by routing on export. Details and pricing at forte-ai.com/fmusic.
.jpg)
