LivePilot

v1.23.4 — Pack-Atlas Phases C/D/E/F:Six new corpus-driven orchestration tools turn the 3,917 parsed pack sidecars + 104 demo.alsparses into actionable artifacts — find similar presets, transplant aesthetics across BPM/scale/genre, narrate a demo, extract a track's chain as a runnable plan, bootstrap pack-coherent compositions, run any of 15 cross-pack workflow recipes. All execution is dry-run by default — returns plans, doesn't auto-mutate the session.

Why this exists.The factory atlas (5264 devices, 33 packs) is whatAbleton ships. Your real library is bigger — your VST/AU plugins, your Max for Live devices, your.adgracks, your custom presets, your Splice packs. Without the corpus builder, all of that is invisible to LivePilot. With it, the same query that previously routed to Operator + Saturator can route toyourValhalla Supermassive,yourCHOWTapeModel,yourMoog Model D — because LivePilot now knows what you have, what each tool sounds like, and which producer aesthetics it supports.

The corpus builder is a 4-phase pipeline that turns "what's installed on this Mac" into AI-queryable knowledge:

Phase 1 — DETECT Walk plugin folders + run auval -a for AUv3 / Mac Catalyst coverage. Captures format (VST3/AU/AAX/CLAP/LV2), vendor, version, bundle ID. ~40-200 plugins typical. Phase 2 — CANONICALIZE Dedupe by vendor+name, prefer VST3 over AU, strip vendor suffix variants ("Valhalla DSP, LLC" = "Valhalladsp" = "Valhalla DSP"). Cluster by vendor for batch research. Phase 3 — RESEARCH Discover local manual files (PDFs, READMEs) per plugin. Emit WebSearch task packets for plugin+technique research. Phase 4 — SYNTHESIZE Sonnet subagent dispatch — write per-plugin identity.yaml with sonic_fingerprint / reach_for / avoid / key_techniques / parameter_glossary / comparable_plugins / genre_affinity / producer_anchors. EXACTLY ONE primary format tag (no dual-indexing across formats).

The result lives at~/.livepilot/atlas-overlays/user/plugins/<plugin_id>/identity.yamland is loaded by every reasoning tool —atlas_search,atlas_chain_suggest,atlas_macro_fingerprint,atlas_describe_chain— alongside the factory atlas. Each result is tagged with its source (factory_atlasvsuser_overlay:user), so the agent always knows whether it's recommending Ableton stock or your own gear.

corpus_setup_wizard One-shot orchestration — runs the full pipeline corpus_init Initialize ~/.livepilot/corpus/ + manifest.yaml corpus_status Inspect manifest, sources, scan history corpus_list_scanners Enumerate registered scanner types corpus_add_source Register a new scan source (project / racks / Max / samples) corpus_remove_source Remove a scan source from manifest corpus_scan Run scanners on configured sources corpus_detect_plugins Phase 1 — VST3 / AU / AUv3 / VST2 / AAX / LV2 detection corpus_canonicalize_plugins Phase 2 — dedupe + VST3-preferred + suffix strip corpus_cluster_plugins Phase 2.5 — group by vendor for efficient research dispatch corpus_trim_plugin_identity Slim a yaml to the overlay-required minimum corpus_discover_manuals Phase 3 — locate local PDFs / READMEs per plugin corpus_research_targets Phase 3 — emit WebSearch task packet for the agent corpus_emit_synthesis_briefs Phase 4 — emit sonnet-subagent briefs per plugin

Why versatility outside Ableton matters.A static knowledge base ages out the day you install a new plugin. The corpus builder makes LivePilot's knowledge boundary equal toyour library, notAbleton's library. Every plugin you add can be re-scanned and synthesized in minutes; every saved.adgrack you build can be indexed alongside Ableton's factory chains. The brain becomes specifically yours.

# In your MCP client (Claude Code / Desktop / Cursor): corpus_setup_wizard # one-shot orchestration # OR fine-grained control: corpus_detect_plugins use_auval=true # finds AUv3 / Mac Catalyst plugins corpus_canonicalize_plugins # VST3 preference + vendor dedup corpus_cluster_plugins # vendor-grouped clusters corpus_research_targets # → agent runs WebSearch corpus_emit_synthesis_briefs # → sonnet writes identity.yamls

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

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.

- 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'sSpliceSourcereads~/Library/Application Support/com.splice.Splice/users/default//sounds.db— Splice's local SQLite catalog of downloaded samples. Read-only, no network calls.

"dark minimal techno 128bpm with industrial textures and ghostly vocals" │ ▼ ┌─────────────────┐ │ Prompt Parser │ → CompositionIntent (genre, mood, tempo, key) └────────┬────────┘ ▼ ┌─────────────────┐ │ Layer Planner │ → role templates (kick, bass, perc, texture, lead, pad, fx) └────────┬────────┘ ▼ ┌─────────────────┐ │ Plan Compiler │ → executable tool sequences └────────┬────────┘ ▼ ┌─────────────────┐ │ Execution Router │ → dispatches: create tracks, search samples, load devices, │ │ program notes, set volumes, build arrangement └─────────────────┘