Auto-Bounce Crashing? Here’s How to Troubleshoot It

Last updated: May 2025

Experiencing a Crash in Auto-Bounce?

Crashes are rare, but when they do occur, they’re almost always the result of how Logic Pro is set up immediately before Auto-Bounce runs. Auto-Bounce relies entirely on Logic being stable, visible, and responsive — it doesn’t alter your session, routing, or plugins. If Logic fails to respond during the scan or bounce process, Auto-Bounce may crash or hang.

This guide walks you through the best steps to prevent crashes and outlines exactly what to send us if one occurs.

✅ Step 1: Use the Latest Version

We’re constantly improving Auto-Bounce to handle edge cases and timing issues.

Download the latest version here:

https://www.auto-bounce.com/forum/downloads

Step 2: Follow the Pre-Flight Checklist

Before every bounce, please review the READ ME FIRST document, the Pre-Flight Checklist, and the User Manual — especially the Power User Tips section on page 27. These resources include best practices that help Auto-Bounce run more smoothly and efficiently.

You’ll find all documentation inside the Auto-Bounce folder in your Applications.

Step 3: Still Crashing? Send Us the Right Info

If Auto-Bounce is still crashing after you’ve followed the setup instructions, please send us the following items so we can help:

1. Crash Report (.ips file) – Required

How to find it:

1. Open the Console app on your Mac

2. Click Crash Reports in the sidebar

3. Locate the most recent report for AutoBounce

4. Control-click it and select Reveal in Finder

5. Drag the .ips file into your reply

2. Screen Recording – Required

Please record your screen from before launching Auto-Bounce all the way through the crash.

To record:

• Press Shift + Command + 5

• Choose Record Entire Screen

• Reproduce the crash

• Attach the video to your support message

3. Logic Project File – Optional but helpful

If the crash only occurs in a specific project, sending us a version that still reproduces the issue can be extremely helpful.

We understand many users work on confidential or NDA-protected material — we regularly support professionals in exactly that situation. Rest assured, we treat all project files with the utmost confidentiality and never share, store, or disclose any content beyond what’s necessary to resolve your issue.

✅ Tips:

• You can remove audio regions, plugins, or sensitive material — we mainly need the track list and project structure.

• Just make sure the problem still occurs in the trimmed version before you send it.

4. .autobounce File

This file contains your full Auto-Bounce job setup and is essential for reproducing your issue.

To save it:

• In Auto-Bounce, click on the "save job" button (the icon with the down arrow right above the jobs list)

• Include the .autobounce file in your message.

Submitting Your Info

Once you’ve gathered the materials above, please submit them through our support system. If your files are large, include a link to a shared folder (Dropbox, Google Drive, etc.) rather than attaching them directly.

We’re Here to Help

Auto-Bounce is built to streamline your workflow and save you time. If something isn’t working, we want to fix it — fast! Providing the details above gives us the best shot at diagnosing and resolving the issue efficiently so you can get back to creating.