Import Module

Using your mix templates

fMusic imports directly into your own Pro Tools mix template: every track lands routed to your template's buses, and the import can even create the new session from the template file for you. You don't have to change your workflow; fMusic adapts to it. Routing into your template is base behavior, included in Studio.

Loading your template in Settings

Point fMusic at your template once: the Pro Tools session template row in Settings > Import & Organize accepts a Pro Tools session template or session file (.ptxt or .ptx) via Select template…. fMusic reads the template inside Pro Tools itself, so two dialogs guard the operation:

1. "Read this template in Pro Tools?" warns that your open session closes and reopens, with Read template and Cancel. fMusic opens the template as a session, reads its routing folders, tracks and routing, then restores your session.
2. "Generate categories from…?", named after your template, appears only if the categories read from it differ from your current table, with Generate N Categories and Keep My M Categories. The template is loaded either way: its routing sources and its tracks stay available, and this choice is only about the category table.

The factory template

Out of the box, fMusic ships with its own template, Forte_Template_26, already connected: its 31 routing folders are read as 31 categories, one folder per category, with the folder's input bus as the route, its color as the category color, and its first track as the template track. Loading your own template replaces that reading with yours; customizing the categories works the same either way.

Where destinations come from

The destination pickers offer real routes only: the catalog of the session open in Pro Tools, or the routes of the loaded template. That is what lets you configure everything with Pro Tools closed. A status row in Settings tells you which source is in use ("N destinations from the open session." / "N destinations from the loaded template.").

Workflow

1. Load your template in Settings, as above, and give each category the destination that matches your template's bus structure: Drums to the drum bus, Vocals to the vocal bus, and so on. If you generated the categories from the template, this is already done.
2. Drag your audio files into fMusic. AI-R recognizes the tracks, and each one picks up its category's destination automatically; individual tracks can be overridden on the import setup page.
3. Pick the destination session. To start fresh from your template, choose Template: its Template from picker offers Installed (templates in Pro Tools' Session Templates folder, chosen by Group and Template) or From settings (the template loaded in Settings); you then set a Session Filename and a Save In folder, and fMusic creates the session from the template, launching Pro Tools if needed. You can equally import into the current session or an existing one already built on your template.
4. Run the import: every track lands in your template routed to the correct bus, no manual patching.

Because the template and the destinations live in Settings, this is a one-time configuration: every future import into that template arrives pre-routed.

Keep destinations matching your template

The category destinations must exist in the session that receives the import. If a route doesn't, the import setup page warns you at prefill and offers that session's real routes, and the preflight blocks destinations that provably don't exist before anything is created.

Not the same as Match template mode

The template link is local to your machine. To carry your categories, routes, colors and naming to another computer, export an fPreset; note that loading an fPreset does not adopt the other machine's template.