Consolidate a Logic Pro Session for a Remote Mix

For a remote Logic Pro mix, rent a Figment M-series Mac from $95/month (the exact chip, RAM and disk are confirmed when the quote is prepared) if the session leans on heavy third-party sample libraries, 96 kHz+ sample rates, Dolby Atmos, or an external audio interface. For a legacy, Intel-compatible Logic version that you can lawfully install, the i3 Mac at $49/month is a cheaper candidate. The current Logic release requires Apple silicon; match the exact version before selecting hardware. Both physical plans are request-based, so ask for current availability in the same message. The $29 virtual Intel macOS plan (2 vCPU, 8 GiB RAM, 80 GiB disk, Linux/KVM, no GPU acceleration, no audio pass-through, browser-console access) can inspect filenames and transferred files with command-line tools; Logic Pro operation and audio processing have not been verified on this VM. Request a Mac for remote mixing →

A Logic Pro project is not necessarily a self-contained archive. Logic stores audio you recorded or imported into the project inside the .logicx package, but third-party sample content, Space Designer impulse responses from the Sound Library, bounced stems saved outside the project, and video references usually live elsewhere on the originating Mac. Zip the folder, hand it to a mix engineer on a rented Mac, and those paths resolve to nothing. The fix is to run Logic's own consolidation, handle the few asset classes it cannot bundle, and verify the result before upload.

Primary references used here: Apple's Consolidate project assets in Logic Pro and the Logic Pro user guide landing page.

Why Logic sessions break when moved

Inside a .logicx package Logic keeps audio you recorded or bounced directly into the project. Almost everything else is a path reference:

• Third-party sample content (Kontakt, Omnisphere, Spire, Serum and similar) lives on the plug-in's own library path — often a multi-gigabyte install the rental Mac does not have.
• Apple Loops and Sound Library content are available once the recipient downloads the relevant Sound Library Packs on their Mac. A fresh Logic install is usually missing specific Packs.
• Space Designer impulse responses are referenced from the Sound Library and may be absent on a minimal install.
• Video files are rarely bundled and typically referenced from an external location.

When any of these references break, Logic can substitute silence, fail to load a channel strip, or open the track greyed out with a missing-plug-in warning. The engineer cannot mix what they cannot hear.

Run Consolidate in File > Project Management

Logic's Consolidate command copies referenced assets into the project's Media folder. According to Apple's user guide, you choose File > Project Management > Consolidate (or the Consolidate Project key command), then tick the asset classes you want copied in. The dialog covers:

• Audio files — recorded and imported audio
• Audio data from Sampler, Alchemy, and Ultrabeat
• Space Designer impulse responses
• Video files
• Sound Library content (Apple Loops)

Click OK and Logic copies the selected assets into the Media folder inside the project package. After consolidation, check that the project size has grown to roughly match the referenced media you expected to pull in. If the size is unchanged, revisit which paths were originally external — consolidation can only gather files Logic can still resolve on your Mac.

Handling third-party sample libraries

Consolidation does not embed a 50–300 GB Kontakt or Omnisphere library; those instruments stay referenced through the plug-in itself. Two practical options:

Option A — Bounce instrument tracks to audio. For a mix engineer who does not need to re-edit MIDI:

1. Select the track in the Tracks area.
2. Choose File > Bounce > Track in Place (or Regions in Place for a single region).
3. Set the bounce options to include effects if you want to lock in the current plug-in processing. Leave them off if the engineer should shape tone from a dry print.
4. Mute or archive the original MIDI/instrument track.
5. The bounced audio lands inside the project and consolidates with everything else.

Option B — Ship stems instead of the editable session. Bounce every track to individual mono/stereo files at the session's sample rate and bit depth, export a MIDI file of the tempo track as a reference, and send that set. Many mix engineers prefer stems: they rebuild a session in the tools they already own and never touch your plug-in chain.

Freeze tracks to substitute missing plug-ins

Freeze renders a track's output — including plug-in processing — to a hidden audio file on disk. Freeze is useful within a working session, but it is not a guaranteed replacement for missing plug-ins after transfer. For a portable handoff, bounce the required tracks to ordinary audio and test the result on the destination.

1. Make sure Enable Complete Features is turned on in Logic Pro's Advanced settings; the Freeze controls do not appear without it.
2. Click the Freeze button (snowflake) in the track header. If it is not visible, right-click the header, open Track Header Components, and enable Freeze.
3. Pick the Freeze mode in the Track inspector — Source Only freezes only the instrument; Pre Fader freezes the instrument plus insert effects.
4. Start playback so Logic can render.

Frozen tracks cannot have their MIDI, instrument or plug-in parameters changed without unfreezing. If the mix engineer needs to adjust EQ, compression or reverb on a given track, do not freeze it — bounce to audio, or send the original session and confirm the plug-ins are available at the destination.

Estimate the archive size before you upload

A short disk worksheet keeps you from kicking off an upload you have to cancel. Fill in minutes of session length and multiply:

• 24-bit, 48 kHz, mono track: ~8.6 MB per minute per track
• 24-bit, 48 kHz, stereo track: ~17.3 MB per minute per track
• 24-bit, 96 kHz, stereo track: ~34.6 MB per minute per track
• Space Designer IRs pulled in: typically 1–50 MB each
• Video reference: check the actual file size; codec and bit rate determine it.

Example: a 4-minute song with 24 recorded + bounced mono tracks at 24-bit/48 kHz is roughly 24 × 4 × 8.6 ≈ 826 MB of audio, plus a handful of IRs. Zip compression on PCM audio is minimal — plan for close to the raw figure on the wire.

Pre-flight checklist

Work through this after consolidation and after freezing or bouncing third-party instrument tracks.

Assets

• Consolidate ran against audio files, sampler data, Space Designer IRs and Sound Library content as needed.
• Every required third-party instrument track has a portable audio bounce, or its exact plug-in and content are available and tested at the destination.
• Video reference track is included or removed.

Plug-ins

• A README.txt inside the project folder lists third-party plug-ins used, with versions.
• Automation tied to plug-in parameters that may differ between versions is flagged.
• Stock Logic plug-ins and required content are present in the destination version.

Audio settings

• Sample rate and bit depth are documented (for example 48 kHz / 24-bit for picture, 44.1 kHz / 24-bit for music).
• Tempo map and time signature changes are intact; a MIDI export of the tempo track is included as a backup reference.
• Markers for verse, chorus, bridge and artist notes are labelled on the Timeline.

Package

• Save a copy of the project before archiving so the working session on your Mac stays untouched.
• Project folder size matches your worksheet estimate: du -sh "/path/to/Project.logicx".
• The source backup stays intact. Do not delete unfamiliar files inside the project package.
• Archive for transfer: zip -r "Project_v2_consolidated.zip" "Project.logicx".

Destination

• Logic Pro version on the rented Mac matches or is newer than the source. A project saved in a newer Logic may not reopen in an older one.
• The destination Mac has the needed Logic Sound Library Packs installed; note which ones in the README.
• Agree how large files will reach the rented Mac. The $29 VM is reached through the browser console, so file transfer uses the engineer's chosen method (their object storage, shared link, or a pulled download inside the guest) rather than drag-and-drop into the viewer.

Picking the right Figment plan for this job

If this is a one-off handoff, consolidate, archive the .logicx package, and transfer it to whichever plan matches the session's demands. If the engineer will work on your material over several weeks, lean toward the M-series tier so plug-in headroom does not become the bottleneck halfway through the mix. Colour, loudness and timing decisions should be validated on the engineer's own monitoring — a remote preview over a browser or VNC session is not a calibrated listening environment.

Request a Mac for remote mixing →

Related guides:

• After Effects batch render on a Mac
• M-series plan for GPU creative work
• Set up a GitHub Actions self-hosted runner on a Mac