Ableton/File

• Ableton File Types – Conceptual Overview

  • Overview

    • Ableton Live uses a variety of proprietary file types to represent sets, clips, presets, and metadata. Some are human-readable (XML or JSON), others are binary. Understanding these formats is essential for workflows involving version control (e.g., Git).

  • Context

    • Many Ableton users want to store projects in Git for collaboration, history, and diffs. The challenge is that some file types are opaque binaries, while others can be normalized for text-based diffs. Knowing which is which helps decide what to commit, ignore, or preprocess.

  • Key Principles

    • Textual formats (XML/JSON) are git-friendly with proper filters.
    • Binary formats (analysis files, waveforms, grooves) are not useful to version and can be regenerated.
    • Archive formats (packs) should be treated as immutable binaries.
    • Programmatically generated files (e.g., .asd) should be excluded since Live will recreate them.

  • File Types & Internal Structure

    • Ableton/File/.als

      • Purpose: Live Set (entire project/arrangement).
      • Format: gzipped XML.
      • Speculation: Unzipping yields structured XML with tracks, devices, automation.
      • Git: Store in repo. Use a textconv filter to decompress for diffs.
      • See-Also:
        • GitHub/codekiln/ableton-live-git-hooks
    • Ableton/File/.alc

      • Purpose: Live Clip (saved audio or MIDI clip + device chain).
      • Format: gzipped XML.
      • Git: Same as .als. Useful to store; enables clip reuse and diffs.
      • See Also:
        • GitHub/codekiln/ableton-live-git-hooks
    • Ableton/File/.adg

      • Purpose: Device Group (Rack preset).
      • Format: gzipped XML.
      • Git: Store; use gzip -cd filter for text diffs.
    • Ableton/File/.adv

      • Purpose: Device Preset (single Instrument/Effect preset).
      • Format: likely gzipped XML (similar to .adg).
      • Git: Store; verify format. Use same filter strategy as .adg.
    • Ableton/File/.amxd

      • Purpose: Max for Live Device (custom patch).
      • Format: JSON with a non-JSON binary header.
      • Git: Store; configure Git diff driver to skip header (e.g. awk '(NR>1)'). This exposes JSON for readable diffs.
      • See Also: Person/Zack Steinkamp/blog/posts/2022-02-15-git-diff-amxd-max
    • Ableton/File/.ask

      • Purpose: Live Skin (UI color theme).
      • Format: XML.
      • Git: Store; Git can diff directly.
    • Ableton/File/.alp

      • Purpose: Live Pack (compressed bundle of sets, samples, presets).
      • Format: zipped archive.
      • Git: Treat as binary. Store only released versions; not suitable for diffs.
    • Ableton/File/.asd

      • Purpose: Sample Analysis File (tempo, warp markers, waveform cache).
      • Format: binary metadata.
      • Git: Do not store; regenerated by Live.
    • Ableton/File/.ams

      • Purpose: Ableton Meta Sound (Operator waveforms for Sampler/Simpler).
      • Format: binary.
      • Git: Store only if custom waveforms are part of creative assets; otherwise ignore.
    • Ableton/File/.agr

      • Purpose: Groove File (timing/humanization template).
      • Format: binary.
      • Git: Store if custom grooves are central to project; diffs not possible.

  • Misconceptions

    • Myth: All Ableton files are binary and unsuitable for Git.

      Reality: Many are gzipped XML or JSON and can be made git-friendly with filters.
      

    • Myth: .asd files must be backed up.

      Reality: They’re metadata caches and should be ignored in source control.
      

  • Recommendations for Git

    • Store with filters: .als, .alc, .adg, .adv, .amxd, .ask.
    • Ignore: .asd (auto-regenerated).
    • Store as binary: .alp, .ams, .agr (no useful diffs).
    • Use custom diff drivers:
      • .als/.alc/.adg/.adv: gzip -cd.
      • .amxd: strip header, parse JSON.
      • .ask: plain XML diff.

  • See Also

    • Person/Zack Steinkamp/blog/posts/2022-02-15-git-diff-amxd-max
    • GitHub/codekiln/ableton-live-git-hooks