Collect All and Save, Freeze, Consolidation and Project Dependencies.

A project looks perfect on your drive and breaks as soon as it leaves: silent tracks because samples stayed in another folder, synths that cannot load because the other machine lacks the plugin, and a struggling computer because nothing was frozen or consolidated. All three failures share one root: the project works only where and when it was created.

This guide covers their solutions: Collect All and Save so media travel, freeze/bounce and consolidation so equipment copes, and an inventory of sample dependencies, plugin dependencies and used plugins so recipients know what to install before listening.

Collect All and Save

Collect All and Save is a command, not a habit: it saves the project and copies all referenced external media into its folder. In Ableton it is a save option; other DAWs offer equivalents such as “copy used samples,” “collect media” or packaging the project in a compressed file.

The effect is specific: the project stops depending on where you stored samples. It can move to an external drive, go to a collaborator or open on another computer without silent tracks. The cost is equally specific: duplicated media increase folder size, and referencing an entire library for a single sample can make collection disproportionate.

Use a sensible cadence: do it at the end of every session that will leave your machine, not only when the project is complete. Sharing unfinished work with broken dependencies makes the other person guess, and guessing in audio loses the thread.

Know that it does not collect everything. Referenced audio travels; synth and effect settings, banks and licences do not. Neither do your machine’s paths or interface preferences. A properly collected project still needs the plugin list below to sound the same.

For very large or frequently moved projects, the natural next step is packaging everything in a single compressed file. DAWs provide that option, the easiest way to send or archive it. In the reverse situation, most programs can locate and repair missing files when a project opens incomplete. That rescues rather than prevents: if media never travelled, repair only returns an incomplete project.

Freeze/Bounce

Freeze/bounce addresses CPU load. Freezing makes the DAW record a temporary audio copy of a track with its effects, playing that audio instead of recalculating it. The track stays editable but stops costing processing. It is the fastest lever when a pad track with three synths consumes half the computer.

Bounce—apply or print—goes further, fixing the result permanently. Distinguish it from freezing: freezing is reversible and provisional; bouncing is final and also releases the processing chain behind it.

Practical rules: freeze while exploring and while changes remain; bounce only when the sound is decided and the chain will not change again. Save a version before any irreversible operation: freeze, flatten and bounce work much better with versioning than undo. The same principle, with each DAW’s nuances, appears in Production Workflow: Templates, Versioning and Bounce.

Two freezing details are discovered late. First, generated audio uses high resolution to avoid sounding worse than playback, but is still a new file, increasing project size while frozen. Second, rendering captures what sounds at that moment, including reverb tails, delay repeats and automation; random-character effects stop changing because their value is written into the file. Freeze to work; unfreeze when something needs to move again.

Consolidation

Consolidation operates on a region rather than a track: it joins a track’s audio fragments into a new file within that track. It closes an edit: if you have cut forty drum tracks into twenty pieces, consolidation leaves one clean track that can move, trim and export without surprises.

It also avoids recalculation: a consolidated region no longer passes through clip processes on every playback, and its duration is exactly what the timeline shows, removing export length mismatches.

Consolidation is not transparent: Ableton creates the new file at the project’s sample rate and bit depth and normalises it, so it may differ from the original if the region came from another format. Consolidate with an already-decided rate rather than as a patch for files from different places. For irreplaceable source material, save a version first and retain the original while checking the result.

One question distinguishes consolidation from freeze and bounce: do I want to keep editing the chain? If so, freeze. If not, consolidate or bounce. Because consolidation replaces media, always save a version first; the same discipline applies to archiving and is covered in Organising a Project: Naming, Folders and Versions.

Sample Dependencies

Sample dependencies include every external audio file referenced by the project: one-shots, loops, library stems and individual recordings. While the path exists, nobody notices; moving the file or opening on another machine leaves the track silent, sometimes without a clear DAW warning.

To control them:

• Collect before moving. Collect All and Save exists for this purpose.
• Check suspect tracks. Download folders and external-drive sources break first.
• Distinguish original recordings from library material. Licensed library media can be downloaded again; that session’s recordings cannot.
• Copy, do not move. Moving the original breaks every other reference pointing to it.

Collecting licensed media into a project folder does not change its licence: it is the same use, now better documented.

Plugin Dependencies

Plugin dependencies are the instruments and effects needed for the project to sound as it did. A project may open and play with missing plugins, but devices appear disabled, settings disappear and the mix changes without an obvious explanation.

Three checks before sharing:

1. List what it uses. Walk through tracks, noting instruments, insert effects and send effects.
2. Check availability and format. The same plugin is not enough: the other machine needs the same format—VST2, VST3, AU or AAX—and an active licence. Details of formats and authorisation appear in Plugin Formats: VST2, VST3, Audio Units and AAX.
3. Define plan B. Either the collaborator installs what is missing or you export tracks depending on unavailable plugins to audio. Half of collaborations fail because this was not decided before sending.

List of Used Plugins

The list of used plugins makes an invisible dependency into a document. Save it in the project’s Docs/ folder, including at least plugin, version, format, licence (account or dongle) and whether it is essential or optional.

It matters in two situations. At delivery, the recipient knows within a minute what to install and what to ignore. Six months later, after a plugin changes version or publisher, the list records exactly what the original session contained instead of forcing reconstruction from memory.

Add the rest of the environment: DAW and version, operating system, project sample rate and relevant audio-interface settings. Buffer, device and sample rate are not cosmetic; they are covered in Installing a DAW: Drivers, Audio Device, Buffer and Sample Rate.

Before Opening or Sending a Project

A sixty-second check prevents most surprises:

• Save a version with date and status.
• Run Collect All and Save or its equivalent.
• Freeze or consolidate processing-heavy material.
• Update the used-plugin list and project notes.
• Check by opening from another path, with the original drive disconnected if possible.
• Copy to another medium: Backups with the 3-2-1 Rule.

If the project opens complete under those conditions, it can travel.

Next Step

The project is now portable within your ecosystem. Next, share it with another person: agree formats, move between DAWs and deliver stems sounding the same on the other machine, all covered in Remote Collaboration: Transferring DAW Projects and Delivering Stems.