Session prep, as most tools define it, ends at routing: every track named, colored and sent to the right bus. Then you open the first channel and it is empty, because routing says where audio goes, not what your studio does to it.
Routing is half the setup
The other half is the chain. The EQ and compressor that every vocal in your room starts from. The sends already feeding the shared reverbs at the right levels. The baseline automation every vocal starts from, identical on every song. A template holds all of it, which is why template driven studios exist in the first place: the template is not a convenience, it is how the room sounds before anyone touches a fader. Our guide to mix template bus routing covers building that structure on the Pro Tools side.
Importing into that world by hand means recreating it per track: route, then open the template, find the matching track, duplicate the chain, copy the sends, check the levels. It is exactly the kind of work that is trivial once and corrosive at forty tracks, and it is why imported sessions so often live one notch below the studio's own standard. The alternative most rooms land on is channel strip archaeology at the start of every mix, and that is the quiet tax this pair of features exists to remove.
Three destination modes, one choice
In fMusic every imported track gets a destination, and the destination mode is chosen once for the whole studio, in Settings, shown read only during import so it cannot drift between sessions by accident. Routing sends each track to an output or bus, available in fMusic Studio and Suite. Track preset applies a saved Pro Tools track configuration to the imported track. Match template copies a template track onto the imported one. The last two are part of fMusic Suite, and they are the difference between a session that is wired correctly and a session that arrives set up. The full old to new map of the rebuild is in what changed from fMusic.
How a track meets its destination
The pipeline upstream makes the destination choice informed rather than clerical. Instrument recognition has already identified what each file contains by the time Import setup opens, so the destinations you see proposed start from what the audio actually is rather than from file order. Each track shows its destination in a dropdown, Shift and Command multi select apply one choice to a whole selection, and the mode itself, Routing, Track preset or Match template, is displayed read only with an Edit in Settings link.
Nothing lands until you have seen it. The lanes, names and categories are all visible in the visualizer before Pro Tools is touched, so the destination pass is a check, not an act of faith.
Track presets: a saved starting point per kind of track
A track preset is Pro Tools' own saved track configuration, and in Track preset mode fMusic applies one to each imported track at import time. The vocal lands as your vocal track, the bass as your bass track, each carrying the channel as you saved it, and assigning thirty drum tracks to the drum preset is one multi selected gesture, not thirty.
Presets answer the question every room already asks: what does a vocal track look like here? Save the answer once in Pro Tools, point the destination at it, and the question stops being asked per session. Presets suit rooms that want consistent starting points without maintaining a full template session: lighter than match template, portable between machines, and indifferent to what the rest of the session looks like.
Match template: the setup copies itself forward
Match template goes further than a preset: each imported track points at a track in your template, and fMusic copies that template track's plugins, sends, routing, color and automation onto the imported one. The template stays the single source of truth: swap the vocal compressor in the template in March, and every session imported in April carries it, with no preset file to re save and nothing to redistribute to other machines.
The template becomes what it always wanted to be: the living definition of how the room works, rather than a starting document people drift away from.
This is the mode built for rooms where the template is the product: facilities where several engineers share one setup, mixers with a sound clients book specifically, studios where any session must be openable by anyone. The session you get is your setup with new audio in it.
Where it pays
The facility. Several engineers, one template, and sessions that move between rooms mid project. Match template means a handed over session carries the room's chains rather than one person's habits, and the handoff conversation shrinks to the creative part.
The recurring client. Their new record opens sounding like their last one, because the setup that mixed the last one is the setup every import lands in. Continuity the client can hear is continuity they book again.
The second song of the night. It starts where the first one did, not behind it. The payoff compounds with repetition, and because the destination mode is a studio setting, none of it depends on anyone remembering to do it: it is simply how material arrives.
What it does not do
It cannot copy a template you have not built. The chain it carries is exactly the one your template holds, and a template full of bypassed experiments gets copied just as faithfully as a disciplined one, so the template deserves the same maintenance as any other studio standard. The same goes for presets: a preset nobody has touched since last year faithfully reproduces last year's taste. The modes automate consistency; taste stays your job, and the template or the preset is where you keep it. It does not retrofit sessions that are already in Pro Tools and already messy: reorganizing existing sessions is Organize's job, not Import's. And the two matching modes are part of fMusic Suite: in fMusic Studio, imports land identified, named, colored and routed per your routing settings, the complete workflow fMusic has always covered, with the tier split mapped in fMusic Studio vs Suite.
Frequently asked questions
What is the difference between a track preset and match template?
A track preset is a saved Pro Tools track configuration that fMusic applies to the imported track. Match template copies a specific track from your template onto the imported one: plugins, sends, routing, color and automation. Presets are portable starting points; match template keeps the template itself as the source of truth.
Where do I choose between routing, track presets and match template?
In Settings, once, for the whole studio. The mode is shown read only during import, so it cannot change between sessions by accident.
Can I assign one destination to many tracks at once?
Yes. In Import setup each track has a destination dropdown, and Shift and Command multi select apply one choice to a whole selection.
Does match template copy automation?
Yes. Match template copies the template track's plugins, sends, routing, color and automation onto the imported track.
Are track presets and match template available in fMusic Studio?
No. Routing mode is in both tiers; track presets and match template are part of fMusic Suite.
Can this fix a session that is already disorganized?
Not at import, because it acts on incoming material. For sessions that already exist and need reorganizing, Organize reads the session track by track and rewrites it to your convention.
fMusic Suite lands every imported track inside your setup, carrying the template's plugins, sends, routing and automation instead of arriving empty. The import pipeline is at forte-ai.com/fmusic.
