Running the queue

The queue is every checked bounce in every session you choose. Press Bounce…, confirm the order, and Fast Bounce works through it: switching sessions in Pro Tools, soloing or muting, setting the range and format, bouncing, next.

The Bounce sheet

Bounce… in the footer opens it. Every session with queued bounces is listed with its count; untick one to leave it out of this run and drag to set the order.

The Bounce sheet listing Song A, Song B and Song C in order, with the wait and email options and a Start Bouncing button.
The Bounce sheet. Which sessions, in what order, and whether to email you at the end.

Two options:

  • Wait after opening a session (a number of seconds, off by default). Gives Pro Tools time to finish loading plug-ins before the first bounce in a session starts. Turn it on if the first bounce of a heavy session ever fails.
  • Email me when it's done. A summary goes to your account email when the run ends, with an optional label such as "Song — mix revisions" so you can tell runs apart. Paid plans only.

Then Start Bouncing.

What happens to each bounce

  1. If the bounce belongs to a different session than the one open, Fast Bounce closes the current session and opens the right one, then waits if you asked it to.
  2. It solos or mutes the bounce's tracks, by name.
  3. It sets the range from the bounce's markers or timeline selection.
  4. It hands the format, folder, name and mix sources to Pro Tools' Bounce Mix and waits for it to finish.
  5. It clears the solos and mutes and moves on.

Pro Tools does the bouncing in the background, so you can keep using other apps. If you need Pro Tools itself, pause first.

While it runs

The main window while bouncing: six bounces done, Song A – Keys bouncing, the rest queued, with a progress bar and Pause and Stop buttons.
A run in progress. The footer counts, times and lets you pause or stop.
  • Each row shows Bouncing, then Done or Failed with the reason on the row. The rail counts up per session.
  • The footer shows "Bouncing 4 of 10", the elapsed time and a progress bar.
  • Pause finishes the current bounce and then waits. While paused you can edit bounces, including the ones still queued, and Resume.
  • Stop ends the run after the current bounce. The one in progress isn't marked Failed, and the ones that never started stay Queued for next time.

Adding and editing are locked while bouncing ("Pause or stop to enable editing").

The Summary

When the run ends, the Summary sheet opens: how many completed and failed, a Needs attention list with each failure's reason, and the files that were made, grouped by session with Reveal in Finder. If Fast Bounce was in the background, a system notification says "Bouncing finished", "Bouncing finished with errors" or "Bouncing stopped".

The Summary sheet with completed and failed counts, a Needs attention list and files grouped by session.
The Summary. Failures are listed, never hidden.

Bounces that finished are unchecked, so running again only bounces what's left. Fix a failed one (see When something doesn't bounce), leave it checked, and press Bounce… again.

The email report

With Email me when it's done on, the same summary arrives in your inbox: every file that was made and every bounce that failed, with your label in the subject. It's the easiest way to check on a long run from your phone.