Keep the original project folder intact. Work with a separate copy for troubleshooting, and make sure you know which .als version you are testing. A folder full of revisions can make an apparent recovery misleading if you accidentally open yesterday’s simpler version instead of the Set that failed.
Decide whether Live quit or stayed running
A crash means Live exits unexpectedly. You may see the Mac’s unexpected-quit message or Live’s crash-report pane on a later launch. A hang means the process remains alive but cannot respond: the loading message stays put, the interface locks, or the Mac lists Live as not responding. Do not use the same diagnosis for both.
A busy load is not automatically a hang. Large sample libraries, first-time plugin scans, and slow storage can delay startup. Look for progress and compare with what this project normally needs. Give a genuinely large load time to work, but note when the same stage repeatedly stops advancing. More double-clicks are unlikely to clarify the problem.
Also test whether Live can open without the affected Set. If an empty startup works but one project fails, focus on that project’s devices, saved states, and files. If Live itself never opens, broaden the investigation to startup scanning, hardware, drivers, and preferences. Ableton’s crash checklist organizes those cases.
Try Ableton’s plugin-disabled launch method
People often call this “safe mode,” but describe the mechanism accurately: it disables third-party plugin scanning for that launch. Quit Live first. Hold Option on Mac, or Alt on Windows, while launching Live until it opens fully and the splash pane closes. Then try the problem Set. Follow Ableton’s official instructions.
Scanning returns on the next restart. If the Set opens with plugins disabled, troubleshoot a copy before restarting normally. Windows Alt-launch is an Ableton troubleshooting method; it does not imply that DAW Defrost supports Windows. Nor does a successful plugin-disabled opening repair or update any device.
Do not save a stripped-down version over your only original. Keep the intact project, a diagnostic copy, and a short note about what was changed. If the session belongs to a collaborator, ask for the plugin versions and formats they used before replacing devices merely because their names look similar.
If it opens, isolate the saved device state
Remove or replace a suspected plugin in the diagnostic copy, then test a normal relaunch. Start with devices recently added or changed, or a device implicated by available evidence. Try the suspect by itself in an empty Set as a separate comparison. A loading problem may depend on restoring a particular preset or saved instance rather than playing notes.
If the empty instance works, try the relevant preset or smallest reproducible setup. If the full Set fails only with multiple instances, record that difference. Avoid rebuilding every track immediately; a minimal example gives the vendor a clearer problem and reduces the chance of unrelated edits masking the result.
Check compatible plugin updates and test them deliberately. Use a separate copy if comparing AU, VST2, and VST3 versions, since presets and automation may not transfer exactly. Ableton’s plugin guide covers these checks. Our Ableton plugin-hang isolation article expands the controlled-testing workflow.
If Live quits immediately, preserve the crash evidence
Use Ableton’s crash-report locations if the report pane is unavailable. On Mac, Live’s activity log is at /Users/[username]/Library/Preferences/Ableton/Live x.x.x/Log.txt, with the version folder matching the installed Live version. Read or copy it rather than editing the evidence during troubleshooting.
System reports can also be viewed in Console. Ableton explains reading crash reports and Log.txt, including the distinction between an informative entry and a harmless logged error. The last plugin mentioned is a lead to test, not sufficient proof by itself that the device caused the quit.
Keep the event time, Live version, macOS version, and the exact Set that failed with the report. If you contact support, describe whether startup itself worked and whether the plugin-disabled test changed the outcome. DAW Defrost cannot analyze this event after Live has quit; it does not read crash reports or Log.txt.
If Live stays running but hangs during loading
This is where DAW Defrost can help on an Apple silicon Mac with macOS 13 or newer. It monitors the running DAW every 15 seconds and snapshots it after 30 seconds of not responding. It reads which plugin’s code the threads are stuck in, names the third-party plugin in a popup, and writes a technical report to Documents ▸ DAW Defrost Reports.
Capture before force-quitting, because ending Live removes the running evidence. Defrost does not fix the hang or open the Set for you. The usual follow-up is a vendor update or bypassing the named device once you can edit a diagnostic copy. It runs locally without internet or uploads and never touches the audio path. It requires M1 or later hardware, not Intel.
Rule out unavailable files and startup hardware
A project in iCloud-synced Desktop or Documents may contain cloud-only files rather than complete local data. Verify that the Set and required media have downloaded before testing. Ableton’s cloud-storage guidance recommends local availability. A visible filename is not enough to establish that its contents are ready on disk.
If Live hangs at application launch, follow Ableton’s startup-hang guide to test with external devices disconnected after shutdown. Do not unplug working storage in the middle of a write. If a preferences reset becomes necessary, use Ableton’s documented procedure and preserve your settings rather than casually deleting configuration files.
Keep the loading diagnosis separate from later playback performance. Once the Set opens, verify the relevant instruments, automation, and a listening bounce before calling the recovery complete. The existing general plugin guide and why Ableton freezes cover broader cases. Return to the studio blog for related workflows.