Move a Live project with its dependencies
- Audit the sets you intend to share and select their complete project folder.
- Review project-root assumptions, case mismatches, unresolved paths and Max device references.
- In the creating version of Live, use Collect All and Save for the media and devices you may redistribute.
- Install matching plug-ins, Packs and vendor sample libraries on the destination, then reopen the set there.
- Export this report as a handoff checklist; resolve missing files in Live’s File Manager.
Ableton’s Collect All and Save guide explains which media and Max devices are collected. Its project transfer guide covers the receiving computer and separate plug-in requirements.
Supported reader and limits
This is a bounded reader for commonly seen Live 9–12 Ableton/LiveSet XML layouts, including modern value paths and older RelativePathElement plus Name references. ALS is a proprietary evolving format, not a published compatibility contract. Other creator versions and unresolved path-root types receive review findings.
It inventories recognized audio, MIDI, group, return and main/master tracks, stored clip/device counts, VST2/VST3/AU descriptors, sample FileRefs, Max PatchSlot references and preset history. All recorded clips and freeze references are counted; mute states, routing, instruments and playback are not simulated. Embedded plug-in state, MIDI notes, audio content, Max patch contents, license status, installed plug-ins and full library-root resolution are not inspected. No ALS files are rewritten.
File matches use only your selected inventory and supplied root. An empty or partial selection cannot establish what exists on another computer. “Found” confirms a selected path, not that the file is the correct recording. Comparison counts declared identities and usage, excluding sound, automation and plug-in parameter changes. Full CSV/JSON exports include rows beyond the screen’s display limits.
Common questions
Does Collect All and Save include plug-ins?
No. Media and Max devices can be collected, but third-party plug-ins must be installed separately. Their own libraries and external dependencies also need review.
Why does a sample work on one computer but not another?
Absolute paths, library roots, drive names and letter-case handling can differ. A portable project-relative reference is preferable, but still needs the actual file in the transferred folder.
Does a matching filename prove I found the right sample?
No. The auditor calls basename and suffix matches candidates, even when their sizes agree. Verify the recording in Live before relinking.