fMusic Studio & Suite are here · rebuilt for Pro Tools  The new generation of fMusic, in two tiers. From €9/month, every trial is full Suite.Explore fMusic →

How to manage presets

An fPreset captures your whole Import configuration in a single .fbus file: the categories with their colors and element vocabularies, their routes, and the naming settings. Load one when you start a new project, switch studios, or set up a second machine.

Importing and exporting

The fPreset row in Settings > Import & Organize has two buttons: Export… saves the current Import settings as an .fbus file to reuse on another project or machine; Import… loads one. Loading is instant and never touches Pro Tools: it replaces your Import configuration and regenerates the Export categories to match.

What travels, and what doesn't

An fPreset carries categories, routes, colors, and naming. It does not carry the other machine's template: the template link, its routes and its tracks stay local, so if the preset's routes should resolve against a template, load that template separately in Settings.

Legacy .forte files

Preset files saved by earlier versions of fMusic (.forte) are translated automatically on import: categories, strip silence settings applied per category with their threshold and duration, and naming styles all come across; the placement mode is always read as Routing. If a file can't be read, fMusic says so plainly ("Unrecognised preset file (neither .fbus nor .forte)."). Picking a .ptxt in the preset panel is redirected to the template reader, since a Pro Tools template is not a preset.

Export has its own presets

The Export wizard carries a separate Presets and prints menu for the export configuration and for print files; none of that travels in an fPreset. It is covered in the Export Module pages.

Build an fPreset for each genre or client you work with regularly. Switching presets transforms your entire import configuration (categories, colors, routing, naming) for the new context in one step.