Ableton Bounce Automator

1 What is Ableton Bounce Automator?

Ableton Bounce Automator (ABA) is a Windows desktop app that automatically batch-exports all your Ableton Live projects as MP3 files — while you sleep, while you work, or while you do anything else.

You point it at a folder, click Start, and walk away. ABA opens each .als project in Ableton, configures the export settings, bounces the first 90 seconds as an MP3, saves the file next to the project, and moves on to the next one — completely unattended.

💡

Why would I need this? If you have dozens or hundreds of old projects and can't remember what half of them sound like, ABA gives you a quick audio preview of every single one without ever opening Ableton manually. Browse your entire library in any file manager or music player in minutes.

Key Features

Batch export — processes entire folder trees, including all subfolders
Smart skip — never re-exports a project that already has an MP3
Reads actual project duration — extracts clip end time directly from the .als file, caps at 3 minutes
Handles unexpected dialogs — "samples not loaded", save prompts, and others — dismissed automatically, up to 15 retries per project
Crash watchdog — detects if Ableton freezes, kills it, restarts it, and picks up from where it left off
Failure tracking — projects that couldn't be exported are logged and can be reviewed or cleared
Full session control — Pause, Resume, and Stop at any time
Real-time log — color-coded, timestamped, project-by-project
Works with Ableton Live 10, 11, and 12 — any edition (Intro, Standard, Suite)

2 Requirements

Operating System — Windows 10 or Windows 11 (64-bit only)
Ableton Live — version 10, 11, or 12 — any edition (Intro, Standard, Suite)
Screen must stay unlocked — ABA controls Ableton's UI directly; the desktop must be visible while it runs
License key — delivered by email after purchase

ℹ️

No extra software needed ABA ships as a single .exe installer. No Python, no Node.js, no command line. The AbletonMCP bridge (required for communication with Ableton) is included and installed automatically.

3 Installation

Installing ABA takes about two minutes and requires no technical knowledge.

Download the installer
After purchasing, you'll receive a download link by email. Save the file AbletonBounceAutomator_Setup_v2.0.exe anywhere on your computer.
Close Ableton Live before running the installer
The installer needs to copy files into Ableton's user folder. If Ableton is open, the installer will detect it and ask you to close it before continuing.
Run the installer
Double-click the .exe. Windows may show a SmartScreen prompt ("Windows protected your PC") — click More info → Run anyway. This is normal for indie software that isn't yet widely distributed.
Read the EULA and proceed
The installer displays the End User License Agreement. Click I accept the agreement and then Next.
Review the AbletonMCP information page
The installer shows you exactly where AbletonMCP will be installed (inside your Ableton user folder). This step is automatic — just click Next.
Choose install location and shortcuts
The default location (C:\Program Files\Ableton Bounce Automator) works for most users. Optionally check Create a Desktop shortcut. Click Install.
Installation completes
The installer copies all files and installs the AbletonMCP Remote Script automatically. Click Finish.

⚠️

Windows Defender / Antivirus Because ABA is a new, independently published tool, some antivirus software may flag the installer as suspicious. This is a false positive. ABA does not access the internet, does not read personal files, and does not modify system files. If your antivirus blocks it, add an exception for the installer or the install folder.

4 Setting Up AbletonMCP in Ableton Live

This is a one-time manual step you do once after installation. AbletonMCP is a small Remote Script that lets ABA communicate with Ableton over a local socket. It needs to be enabled in Ableton's settings.

Open Ableton Live
Open Ableton's Preferences
Press Ctrl + , — or go to Options → Preferences.
Go to the "Link, Tempo & MIDI" tab
Click the tab at the top of the Preferences window.
Find an available Control Surface slot
Scroll down to the Control Surfaces section. You'll see a list of slots (Control Surface 1, 2, 3…). Pick any empty slot.
Set Control Surface → AbletonMCP
Click the dropdown under Control Surface for that slot and select AbletonMCP from the list.
Set Input and Output → None
For the same slot, set both Input and Output dropdowns to None.
Close Preferences
AbletonMCP is now active. It will remain enabled every time you open Ableton.

✅

How to confirm it's working After selecting AbletonMCP, Ableton may briefly show a notification at the bottom of the screen. You don't need to do anything else — it runs silently in the background. You only need to do this setup once per Ableton installation.

5 License Activation

ABA requires a one-time license activation. Your license key is delivered instantly to your email after purchase from Gumroad.

Activating for the first time

Launch Ableton Bounce Automator
From the Desktop shortcut or the Start Menu.
The activation window appears automatically
On first launch (or if no valid license is found), the app shows a dark activation dialog.
Enter your license key
Type or paste your key. It is formatted as XXXX-XXXX-XXXX-XXXX. The app auto-inserts the dashes as you type — you can paste the full key at once too.
Click Activate
If the key is valid, a confirmation message appears and the main window opens.

ℹ️

Activation is stored locally The license is saved in the Windows Registry under your user profile. It is machine-bound and does not require an internet connection. If you reinstall Windows or move to a new computer, contact support for a transfer.

⚠️

License key not working? Make sure you are copying the full key from your email, including all characters. Keys are case-insensitive. If the problem persists, contact robledosilva@gmail.com.

6 First Run

Before starting your first batch export, make sure:

Ableton Live is open — ABA controls it directly; it must be running
AbletonMCP is enabled in Ableton's Preferences (done once, stays active)
Your screen is unlocked — ABA drives Ableton's UI via mouse and keyboard automation
You are not actively clicking around in Ableton — let ABA take control

⚠️

Do not move the mouse to screen corners while ABA is running ABA uses PyAutoGUI for keyboard automation. Screen corners are safe — the failsafe is disabled — but avoid dragging windows or clicking inside Ableton while a batch is in progress.

Quick start

Open Ableton Live and leave it on the main screen.
Launch Ableton Bounce Automator from your Desktop or Start Menu.
Click Browse and select the root folder that contains your Ableton projects. ABA scans all subfolders automatically.
Click ▶ Start and walk away. ABA handles everything from here.

7 Controls Reference

Button	When available	What it does
▶ Start	Idle	Begins the batch export. Scans the selected folder for projects without an MP3 and starts processing them one by one.
⏸ Pause	Running	Pauses processing after the current project finishes its current step. Ableton keeps running; ABA simply waits.
▶ Resume	Paused	Resumes from exactly where it paused. No project is skipped or re-processed.
■ Stop	Running or Paused	Signals ABA to stop after the current project finishes. Projects already exported are not affected. The progress is preserved — run again to continue from where you stopped.
List Failures	Always	Prints to the log all projects that failed to export in previous sessions. The failure list is stored in a file inside your projects folder.
Clear Failures	Always	Removes all entries from the failure list. After clearing, those projects will be retried on the next run.

Status bar

The status bar below the folder path shows the current state in real time: Ready. → Exporting: [project name] → Done! or Stopped.

The counter on the right side of the status bar shows progress as current / total (e.g., 12 / 87).

8 Reading the Execution Log

The log panel shows a real-time, color-coded, timestamped record of everything ABA is doing. Here is what each color means:

Color	Meaning
White	Section headers — folder path, project count
Cyan-green	Normal info — file names, durations, export confirmation
Blue	Steps in progress — "Opening project...", "Waiting for Ableton..."
Purple	Project start and final completion messages
Yellow	Warnings — unexpected dialogs dismissed, unknown durations, paused state
Red	Errors — timeouts, failed exports, watchdog events, stop signal
Gray	Dim info — already-skipped projects, separators, timestamps

Example log output

[09:14:22] Folder: D:\My Projects

[09:14:22] 3 already have MP3:

[09:14:22] ok SynthLoop - session1.mp3

[09:14:22] 84 project(s) to process:

[09:14:22] ────────────────────────────────────────────────────

[09:14:23] [1/84] HouseTrack Feb

[09:14:23] file : session1.als

[09:14:23] duration : 142.3s -> 142.3s

[09:14:23] -> Opening project...

[09:14:27] -> Waiting for Ableton to load...

[09:14:41] Project ready.

[09:14:41] -> Export Audio/Video (attempt 1/15)...

[09:14:44] Dialog open. Configuring...

[09:14:46] Rendering: HouseTrack Feb - session1.mp3

[09:15:08] Done: HouseTrack Feb - session1.mp3 (3274 KB)

9 Managing Failures

Sometimes a project cannot be exported — corrupted .als files, missing critical samples that prevent loading, or repeated Ableton crashes on the same project. ABA marks these as failed and skips them on future runs.

Where failures are stored

ABA creates a file called _bouncer_failed.json directly inside your selected projects folder. This file lists all the .als paths that failed. You can open it in any text editor if you want to inspect or manually edit the list.

Listing failures

Click List Failures at any time. ABA prints every failed project to the log, organized by folder. Use this to identify which projects need attention.

Clearing failures

Click Clear Failures to delete the _bouncer_failed.json file. On the next run, those projects will be attempted again. Useful after you have fixed a missing sample pack or restored a corrupted project.

💡

Tip A project is only marked as failed when ABA cannot load it in Ableton at all (e.g., Ableton returns to an "Untitled" session instead of opening the project). Projects that simply couldn't export after 15 attempts are skipped for the session but not added to the permanent failure list — they will be retried next time.

10 How It Works

Understanding the internals helps you know what to expect during a run.

Project scanning

ABA scans your selected folder and all subfolders. For each subfolder, it picks the most recently modified .als file (one per folder). Folders named "Backup" are ignored. Projects that already have an MP3 are skipped silently.

Opening a project

ABA calls os.startfile() on the .als file — the same as double-clicking it in Explorer. Ableton opens the project normally.

4-phase load detection

ABA waits for Ableton to be fully ready through four phases:

Splash screen closes — watches for the loading splash to disappear.
No pending dialogs — dismisses any save prompts or confirmation dialogs.
Window title matches — confirms Ableton's title bar contains the project name.
MCP socket stable for 5 seconds — verifies the AbletonMCP bridge is responding consistently, confirming Ableton is fully loaded and not still initializing plugins.

Export configuration

ABA opens the Export Audio/Video dialog (Ctrl+Shift+R) and navigates it entirely via Tab key, without relying on fixed screen coordinates. It takes a screenshot of the dialog to detect the state of the WAV and MP3 toggle buttons (identified by their orange "ON" color), then turns WAV off and MP3 on if needed.

Render length

ABA reads the .als file (which is a gzip-compressed XML) to find the end position of the last clip across all tracks. This is converted to bars using the project's tempo. The render is capped at 3 minutes (180 seconds).

MP3 file naming

The output MP3 is named:
[FolderName] - [FileName].mp3
and saved in the same folder as the .als file.

Crash watchdog

A background thread checks Ableton's window title every 5 seconds. If it contains "(Not Responding)", the watchdog flags a crash. ABA then:

Kills the Ableton process via taskkill.
Waits for it to fully exit.
Restarts the watchdog thread.
Reopens the same project and retries the export once.
If the crash happens again on the same project, it is skipped and the next project is processed.

11 FAQ

Do I need to leave Ableton open the whole time?

Yes. ABA controls Ableton Live directly. Keep it open and running. You don't need to interact with it — just leave it in the background.

Can I use my computer while ABA is running?

Yes — with caveats. You can work in other apps (browser, text editor, etc.) as long as you don't click inside Ableton or move windows on top of the Export dialog while it's open. The screen must stay unlocked.

What if a project has missing samples?

ABA dismisses the "samples not loaded" warning dialog automatically and retries up to 15 times. If the dialog keeps appearing and the export still won't open, the project is skipped for the session (but not permanently marked as failed).

What if Ableton crashes or freezes during export?

The crash watchdog detects it within 5 seconds, kills the frozen process, waits for it to exit, and reopens the project to try again. If it crashes again on the same project, ABA skips it and moves on to the next one.

Will it overwrite MP3s I already have?

No. ABA checks for an existing MP3 before processing each project. If one is found, the project is silently skipped. Your existing files are never touched.

How long does it take per project?

It depends on Ableton's load time and the project's render length. A typical project takes 1–3 minutes total: ~30–60 seconds to load, plus the actual render time. With ~100 projects per 8-hour overnight session, you can expect to process a large library in one or two nights.

Can I pause and come back later?

Yes. Use the ■ Stop button to end the current session cleanly. Because ABA skips projects that already have an MP3, the next time you run it, it will automatically resume from where it left off — only processing the remaining projects.

Does ABA work with Ableton Intro?

Yes. ABA works with all editions: Intro, Standard, and Suite — versions 10, 11, and 12.

Is this affiliated with Ableton AG?

No. ABA is an independent tool built by a producer. Ableton® is a registered trademark of Ableton AG. ABA is not affiliated with, endorsed by, or sponsored by Ableton AG.

Can I use my license on multiple computers?

Each license is for a single installation. If you need to transfer it to a new machine, contact support at robledosilva@gmail.com.

12 Contact & Support

ABA is built and maintained by a single producer. If you have questions, bugs to report, or just want to say hi:

Email — robledosilva@gmail.com
GitHub — github.com/robledosilva/ableton-bouncer-automator

🐛

Reporting a bug? Please include: your Ableton Live version and edition, your Windows version, the project name that caused the issue, and the relevant lines from the log panel (copy-paste them from the app). This helps a lot.