LivePilot

Test runner is not in requirements.txt (runtime-only deps) — install it explicitly:

.venv/bin/pip install pytest pytest-asyncio .venv/bin/pytest tests/ -v ```

See CONTRIBUTING.md for architecture details, code guidelines, and how to add tools.

<br>

---

Install

Quick: One Command Setup

npx livepilot --setup

Runs the full setup wizard: checks Python, installs the Remote Script, creates the Python environment, copies the M4L Analyzer, and tests the Ableton connection.

Sample Engine — 23 tools

Three-source sample intelligence with critic-driven fitness scoring, plus deep Splice integration (catalog search, preview, collections, preset downloads).

SOURCES ─────────── BrowserSource  (Ableton's built-in library)
                    SpliceSource   (local Splice catalog via SQLite)
                    FilesystemSource (user-specified directories)
                    Splice LIVE    (gRPC + GraphQL for the full catalog)

CRITICS ─────────── key fitness · tempo fitness · spectral match
                    genre alignment · mood alignment · technical quality

TECHNIQUES ─────── 29 processing recipes:
                    Surgeon (precise, transparent) vs.
                    Alchemist (experimental, transformative)

PLAN-AWARE ─────── Ableton Live plan   100 samples/day (no credit drain)
                    Sounds+/Creator     CREDIT_HARD_FLOOR=5 safety gate
                    Free samples        bypass both gates

Sample analysis & planning
  analyze_sample            Build complete SampleProfile (material, key, BPM, spectral)
  search_samples            Multi-source search with critic scoring
  evaluate_sample_fit       Score a candidate sample against session context
  suggest_sample_technique  Recommend processing technique for a sample
  plan_sample_workflow      Full processing pipeline: warp + slice + effects
  plan_slice_workflow       Slice-specific workflow for breaks / drum loops
  get_sample_opportunities  Surface sample-friendly spots in the session

Splice LIVE (catalog, collections, presets)
  get_splice_credits        Plan + remaining credits + daily quota state
  splice_catalog_hunt       Query the full Splice catalog (gRPC)
  splice_download_sample    Plan-aware download (credit floor + quota check)
  splice_preview_sample     Zero-cost audition via PreviewURL
  splice_describe_sound     Natural-language search via Splice GraphQL
  splice_generate_variation Find catalog samples similar to a given UUID
  splice_list_collections   Enumerate user's Likes / bass / keys folders
  splice_search_in_collection / add_to_collection / remove_from_collection / create_collection
  splice_list_presets       Purchased instrument presets
  splice_preset_info · splice_download_preset
  splice_pack_info          Per-pack metadata
  splice_http_diagnose      Debug the Splice HTTPS bridge

<br>

M4L Bridge — 38 analyzer tools `[optional]`, 32 bridge commands

The M4L Analyzer sits on the master track. UDP 9880 carries spectral data to the server. OSC 9881 sends commands back. The ensure_analyzer_on_master pre-flight (v1.20.3) loads the analyzer idempotently on first use — call it once at session start and forget about it.

[!TIP] Most tools work without the analyzer — it adds 38 spectral/analyzer tools (frequency, loudness, perception, Simpler, warp) and closes the feedback loop.

SPECTRAL ─────── 9-band frequency decomposition (sub_low → air)
                 sub_low (20-60 Hz) split off so kick fundamentals don't hide inside sub
                 true RMS / peak metering
                 Krumhansl-Schmuckler key detection

DEEP LOM ─────── hidden parameters beyond ControlSurface API
                 automation state per parameter
                 recursive device tree (6 levels into nested racks)
                 human-readable display values as shown in Live's UI

SIMPLER ──────── replace / load samples
                 get slice points, crop, reverse
                 warp to N beats, get audio file paths

WARP ─────────── get / add / move / remove markers
                 tempo manipulation at the sample level

<br>

Wonder Mode — Stuck-Rescue Workflow

When a session is stuck — repeated undos, overpolished loops, no structural progress — Wonder Mode activates:

1. Diagnose — classify the stuckness (loop trap? missing contrast? identity unclear?)
2. Generate — find semantic moves that address the diagnosis, enforcing real distinctness
3. Preview — apply each variant, capture, undo. Hear before committing
4. Commit or Reject — choice recorded into taste and session continuity

Splice Integration

LivePilot reads Splice's local SQLite database to search your downloaded samples with full metadata. No API key needed — it reads the database file directly.

What it does: - Searches your downloaded Splice samples with key, BPM, genre, and tag metadata - Integrates as a third source alongside Ableton's browser and filesystem scanning - Works without a Splice subscription — any previously downloaded samples are searchable

How it works: The Sample Engine's SpliceSource reads ~/Library/Application Support/com.splice.Splice/users/default/*/sounds.db — Splice's local SQLite catalog of downloaded samples. Read-only, no network calls.

Requirements: Splice desktop app running (the MCP server talks to it over gRPC at a dynamic port advertised via port.conf, with self-signed TLS). For fully offline search, previously-downloaded samples are always searchable via the local SQLite fallback even if the Splice app isn't running.

<br>

Easiest: Claude Desktop Extension (1 click)

Download the latest livepilot-<version>.mcpb from the Releases page and double-click it. Claude Desktop installs everything automatically. Then:

1. Open Ableton Live 12
2. Preferences → Link, Tempo & MIDI → Control Surface → LivePilot
3. Start chatting

[!TIP] The Desktop Extension auto-installs the Remote Script and M4L Analyzer on first launch.

Or the full plugin (MCP server + skills + slash commands):

claude plugin marketplace add github:dreamrec/LivePilot claude plugin install livepilot@dreamrec-LivePilot

**Codex App:**

**Claude Desktop (macOS)** — `~/Library/Application Support/Claude/claude_desktop_config.json`:

**Claude Desktop (Windows):**

`%APPDATA%\Claude\claude_desktop_config.json`:

**Cursor** — `.cursor/mcp.json`:

**VS Code** — `.vscode/mcp.json`:

</details>

<details> <summary><strong>3. M4L Analyzer (optional — adds 38 tools)</strong></summary>

Drag LivePilot_Analyzer.amxd onto the master track for real-time spectral analysis. The --setup wizard and Desktop Extension do this automatically. From v1.20.3, your AI client can also call ensure_analyzer_on_master — an idempotent pre-flight that loads the device if missing and no-ops otherwise. The Creative Director skill does this on every session's Phase 1 ground read so you can't forget.

Important: The Analyzer must be the LAST device on the master track — after all effects (EQ, Compressor, Utility) so it reads the final output signal. The pre-flight tool reports is_last_on_master: bool and warns if the invariant is broken.

</details>

<details> <summary><strong>4. Splice (optional — adds sample catalog)</strong></summary>

If you have Splice installed with downloaded samples, the Sample Engine can search them with full metadata (key, BPM, genre, tags) via the local SQLite database.

No API key, no configuration — the Sample Engine reads Splice's sounds.db file directly.

Without Splice, the Sample Engine still searches Ableton's browser and your filesystem.

</details>

Plugin

Codex App

npx livepilot --install-codex-plugin

Claude Code

claude plugin marketplace add github:dreamrec/LivePilot
claude plugin install livepilot@dreamrec-LivePilot

Producer Agent — an orchestrated multi-step assistant for building, layering and refining sessions. Consults memory for style context, searches the atlas for instruments, searches samples, creates tracks, programs MIDI, chains effects, reads the spectrum to verify, and arranges sections. The agent proposes plans; the user confirms and listens. LivePilot is a high- trust operator, not an autonomous producer.

Core Skill — operational discipline connecting all layers. Consult atlas before loading. Read analyzer after mixing. Check memory before creative decisions. Verify every mutation.

<br>

---