Export Module

How to bounce your stems

Select the prints a delivery needs and run them. fMusic drives the Pro Tools bounce for every selected print, moves the rendered files to your destination, and restores the session state when it is done. This page covers what actually happens during that run.

Selecting what renders

Only the prints you select are rendered. Every row in the print list carries a selection checkbox: click to toggle one print, shift-click to paint the same state across the whole span from the last click, or use Select all in the toolbar as a toggle. A print you have just created or imported arrives already selected, and the bottom bar keeps count with N prints selected.

The run needs at least one selected print and at least one audio format in Print settings; otherwise the action is disabled with Select at least one print. or Add at least one audio format. A missing mix source does not block the run: the print is skipped or falls back at execution time, as described below.

Print now or add to the queue

Print starts the run immediately and takes you to the processing view. If the queue already holds waiting jobs, fMusic asks Run this print? and offers Print this only, Process all (N+1), or Cancel, so an export never silently jumps ahead of parked work. Add to Queue parks the job instead, confirmed by a toast, to run later alongside other sessions. Both paths execute identically: an immediate run and a queued one can never behave differently.

What Pro Tools does for each print

For every selected print, in list order, fMusic isolates the print's tracks according to its mode: a Solo print solos its tracks, a Mute print mutes every other track. It then runs one bounce per format row in your Print settings, so a WAV plus MP3 configuration produces two passes per print. Progress is reported per unit, for example Rendering {print} — WAV 48k/24b.

Where your files land

Pro Tools always writes each bounce into the session's own Bounced Files folder first. fMusic waits for the file to finish writing, then moves it to the destination set in Print settings. If no destination folder is chosen, the files simply stay next to the session in Bounced Files.

The outcome summary

When the run finishes, the job reports N files rendered, plus N failed, N skipped, and N warning(s) when they apply, with a checklist row per bounce. Reveal in Finder opens the destination folder so you can check the delivery immediately. A run counts as fully complete only with zero failures, zero skips, and every requested bounce delivered.

Why a print is skipped, and what only warns

A print is skipped, and nothing renders for it, when the job cannot honor what the print asks for:

• Its marker range cannot be resolved: a boundary marker is no longer in the session, a marker name matches more than one marker, or the range ends before it starts
• Its own mix source is not assigned in the session: a print with an explicit source is never silently repointed at another mix
• None of its tracks exist in the open session

Other problems produce a warning but the bounce still runs: if some of a print's tracks are missing, it is bounced without them and the report says so; if an inherited mix source is unavailable, the print falls back to Pro Tools' default mix source or the main mix. The distinction is deliberate: an inherited source is a project default, so a fallback is acceptable, while a source you set on the print itself is a decision fMusic will not override.

Failures and cancelling

One failed print never kills the batch: the remaining prints still render, and the failure shows up in the summary. Cancelling takes effect at the clean stop point between bounces, so a print is never left half-written. Whatever ends the run, completion, failure, or a cancel, fMusic restores the session's solo and mute states, so your session comes back exactly as you left it.

Add prints to session

With Add prints to session enabled in Print settings, each rendered file is imported back into the Pro Tools session as a new audio track, placed at Session Start or at the current Selection. That is the classic print-stems-into-the-session workflow, without a manual import round trip after the bounce.

To build and manage the prints themselves, see Favorite and custom prints. For sources, ranges, and formats, see Print parameters.