Video summary

Understanding Disk Allocation In Pro Tools

Main summary

Key takeaways

Technology

Summary: Understanding Disk Allocation in Pro Tools (and why files go missing)

Key concept: where Pro Tools keeps session audio

  • For most sessions, imported/recorded audio is stored inside the session’s Audio Files folder.
  • However, where files go depends heavily on import preferences and disk allocation settings, which is why files can seem to “go missing” when moving sessions between computers or drives.

Import behavior (important for preventing missing files)

Preference: Processing → “Automatically copy files on import”

  • Enabled: Audio dragged into the session is copied into the session’s Audio Files folder.
  • Disabled: Compatible audio is typically referenced from its original location instead of being copied into the session.
    • Example behavior described:
      • If the sample rate matches, Pro Tools references it.
      • If it doesn’t (or if conversion is required, such as with MP3), the import behavior changes (e.g., “Add” may be greyed out because conversion is required).
  • It’s also noted that importing via File → Import Audio offers options to either reference or copy, depending on whether matching/conversion is needed.

Disk Allocation window (Setup → Disk Allocation)

  • Located under Setup → Disk Allocation.
  • Shows, per track, where the media for that track should go:
    • Left: track list
    • Right: Route Media Folder (where recorded audio for that track goes)
  • Changing a track’s route media folder redirects newly recorded audio to a different drive.
    • Example result described:
      • Tracks left on the original location write into the normal session Audio Files structure.
      • Tracks changed to a different drive create a folder named after the session on that drive, containing the newly recorded audio.

When changes take effect (no retroactive moving)

  • Changing disk allocation does not move files that are already recorded.
  • It only affects subsequent recordings:
    • Previously recorded audio stays where it originally went.
    • Only content recorded after the change uses the new destination.

Use cases for disk allocation

  • Splitting recording workload across drives
    • Assign different tracks to different drives (custom per-track routing).
  • Emergency capacity management
    • If a drive is near full mid-session, redirect future recordings to another drive instead of moving existing data.

“Custom Allocation Options” for newly created tracks

  • After changing routing, creating new tracks normally defaults them to the original location.
  • A workaround is described:
    • Enable custom allocation options
    • Set a default destination so that new tracks created from that point onward automatically use the chosen recording location.

File/folder structure option

  • Option mentioned: Create subfolders for audio/video/fade files
  • Result described:
    • Each selected destination location gets a Pro Tools-like folder structure (e.g., an Audio Files folder) rather than scattering files flatly.

Round-robin allocation (legacy/avoid)

  • Option: Use round-robin allocation for new tracks
    • Distributes newly recorded content across all available record drives.
  • Recommendation:
    • Avoid it, since it increases the likelihood of missing files when moving sessions (many tracks spread across many drives).

Why missing files happen when moving sessions

Main failure mode described:

  • If session audio is spread across multiple drives due to:
    • disk allocation changes,
    • round-robin allocation,
    • importing without “copy files on import,” or
    • importing via “reference” rather than “copy”
  • Then moving/copying only the session folder contents (especially only what’s inside the session’s Audio Files folder) will omit media located on other drives.

How to verify locations

  • Use the Clip List and show full path (disk locations).
  • This reveals that media files may live on:
    • an SSD,
    • another drive,
    • or even a different system’s drive (e.g., Macintosh).

Recommended fix: “Save Copy In…”

File → Save Copy In…

  • Creates a self-contained duplicate session.
  • Can copy:
    • audio files,
    • and optionally video files (if present).
  • Ensures Pro Tools knows where assets are at save time, then packages everything into a new folder location so media isn’t stranded across external drives.

Additional “Save Copy In…” options mentioned

  • Convert file format (e.g., WAVE ↔ AIF/AIFC)
    • Guidance: prefer Broadcast WAV (BWF) for metadata support.
  • Change sample rate
    • Example: convert a 96k-like session to 48k.
  • Change bit depth
    • If reducing bit depth, Pro Tools applies dither automatically.
  • Save in older Pro Tools session formats if needed
    • Notes PTX is the current format (since Pro Tools 10), but older versions may require conversion.

Main speaker(s) / sources

  • Primary speaker: The video’s instructor/presenter (no named person provided in the subtitles).
  • Source discussed: Pro Tools features (Preferences, Disk Allocation window, Save Copy In, Clip List full path).

Original video