livepilot-core

分类: 工具与效率 | 上传者: dreamrec | 下载: 0 | 版本: v1.0（最新）
LivePilot 的核心规则 — Ableton Live 12 的代理生产系统。跨 17 个领域的 178 个工具。设备图集（280+ 设备）、M4L 分析器（频谱/RMS/调检测）、技术内存、自动化智能（16 种曲线类型、15 种配方）、音乐理论（Krumhansl-Schmuckler、物种对位法）、生成算法（欧几里德节奏、tintinnabuli、相移）、新黎曼和声（PRL 变换、Tonnetz）、MIDI 文件 I/O。通过 MCP 工具使用 Ableton Live 时使用。
更新日志: Source: GitHub https://github.com/dreamrec/LivePilot
目录结构

当前层级: tree/main/livepilot/skills/livepilot-core/
📁 references/
- 📁 device-atlas/
  - 📄 00-index.md 6.3 KB
  - 📄 distortion-and-character.md 57.7 KB
  - 📄 drums-and-percussion.md 45.7 KB
  - 📄 dynamics-and-punch.md 49.9 KB
  - 📄 eq-and-filtering.md 37.3 KB
  - 📄 midi-tools.md 60.1 KB
  - 📄 movement-and-modulation.md 39.4 KB
  - 📄 space-and-depth.md 48.1 KB
  - 📄 spectral-and-weird.md 52.0 KB
  - 📄 synths-native.md 50.3 KB
- 📄 ableton-workflow-patterns.md 27.2 KB
- 📄 automation-atlas.md 12.8 KB
- 📄 m4l-devices.md 14.6 KB
- 📄 memory-guide.md 4.4 KB
- 📄 midi-recipes.md 15.0 KB
- 📄 mixing-patterns.md 20.6 KB
- 📄 overview.md 19.1 KB
- 📄 sound-design.md 14.2 KB
📄 SKILL.md 27.8 KB
SKILL.md

---
name: livepilot-core
description: Core discipline for LivePilot — agentic production system for Ableton Live 12. 178 tools across 17 domains. Device atlas (280+ devices), M4L analyzer (spectrum/RMS/key detection), technique memory, automation intelligence (16 curve types, 15 recipes), music theory (Krumhansl-Schmuckler, species counterpoint), generative algorithms (Euclidean rhythm, tintinnabuli, phase shift), neo-Riemannian harmony (PRL transforms, Tonnetz), MIDI file I/O. Use whenever working with Ableton Live through MCP tools.
---

# LivePilot Core — Ableton Live 12

Agentic production system for Ableton Live 12. 178 tools across 17 domains, three layers:

- **Device Atlas** — A structured knowledge corpus of 280+ instruments, 139 drum kits, and 350+ impulse responses. Consult the atlas before loading any device. It contains real browser URIs, preset names, and sonic descriptions. Never guess a device name — look it up.
- **M4L Analyzer** — Real-time audio analysis on the master bus (8-band spectrum, RMS/peak, key detection). Use it to verify mixing decisions, detect frequency problems, and find the key before writing harmonic content.
- **Technique Memory** — Persistent storage for production decisions. Consult `memory_recall` before creative tasks to understand the user's taste. Save techniques when the user likes something. The memory shapes future decisions without constraining them.

These layers sit on top of 178 deterministic tools across 17 domains: transport, tracks, clips, notes, devices, scenes, mixing, browser, arrangement, memory, analyzer, automation, theory, generative, harmony, MIDI I/O, and perception.

## Golden Rules

1. **Always call `get_session_info` first** — know what you're working with before changing anything
2. **Verify after every write** — re-read state to confirm your change took effect
3. **Use `undo` liberally** — it's your safety net. Mention it to users when doing destructive ops
4. **One operation at a time** — don't batch unrelated changes. Verify between steps
5. **Track indices are 0-based** — track 0 is the first track. Use negative indices for return tracks (-1=A, -2=B). Use -1000 for master track.
6. **NEVER invent device/preset names** — always `search_browser` first, then use the exact `uri` from results with `load_browser_item`. Hallucinated names like "echomorph-hpf" will crash. The only exception is `find_and_load_device` for simple built-in effects ("Reverb", "Delay", "Compressor", "EQ Eight", "Saturator", "Utility").
7. **Color indices 0-69** — Ableton's fixed palette. Don't guess — use the index
8. **Volume is 0.0-1.0, pan is -1.0 to 1.0** — these are normalized, not dB
9. **Tempo range 20-999 BPM** — validated before sending to Ableton
10. **Always name your tracks and clips** — organization is part of the creative process
11. **Respect tool speed tiers** — see below. Never call heavy tools without user consent.
12. **ALWAYS report tool errors to the user** — if any tool call returns an error, immediately tell the user what failed, why, and what workaround you're using. Never silently swallow errors or switch strategies without explaining. Include: the tool name, the error message, and your fallback plan. This applies to all tool errors including missing M4L analyzer, dead plugins (`parameter_count` <= 1 on AU/VST), connection timeouts, and invalid parameter responses.
13. **Verify AU/VST plugin health after loading** — after `find_and_load_device` or `load_device_by_uri` for any AU/VST plugin, call `get_device_info`. If `parameter_count` <= 1 and `class_name` contains "PluginDevice", the plugin is dead. Delete it with `delete_device` and replace with a native Ableton alternative. Report the failure to the user.

## Tool Speed Tiers

Not all tools respond instantly. Know the tiers and act accordingly.

### Instant (<1s) — Use freely, no warning needed
All 178 core tools (transport, tracks, clips, notes, devices, scenes, mixing, browser, arrangement, memory, automation, theory, generative, harmony, midi_io, perception) plus Layer A perception tools (spectral shape, timbral profile, mel spectrum, chroma, onsets, harmonic/percussive, novelty, momentary loudness). These are the reflex tools — call them anytime without hesitation.

### Fast (1-5s) — Use freely, barely noticeable
`analyze_loudness` · `analyze_dynamic_range` · `compare_loudness`

File-based analysis that reads audio from disk. Fast enough to use mid-conversation. No warning needed for files under 2 minutes.

### Slow (5-15s) — Tell the user before calling
`analyze_spectral_evolution` · `compare_to_reference` · `transcribe_to_midi`

These run multi-pass analysis or load AI models. Always tell the user what you're about to do and roughly how long it takes. Never chain multiple slow tools back-to-back without checking in.

### Heavy (30-120s) — ALWAYS ask the user first
`separate_stems` · `diagnose_mix`

These run GPU-intensive processes (Demucs stem separation). Processing time: 15-25s on GPU, 60-90s on CPU/MPS. `diagnose_mix` chains stem separation with per-stem analysis and can take 2+ minutes.

**CRITICAL: Heavy Tool Protocol**
- NEVER call `separate_stems` or `diagnose_mix` unless the user explicitly requests it
- NEVER call them speculatively or "just to check"
- NEVER call them during creative flow (beat-making, sound design, mixing) — they break momentum
- ALWAYS warn the user with an estimated time before calling
- ALWAYS prefer fast tools first: if the user says "check my mix", use `analyze_loudness` + `analyze_dynamic_range` (2 seconds total), report findings, THEN offer to escalate: "I could separate stems to investigate further, but that takes about a minute. Want me to?"

**Wrong:** User says "how does my track sound?" → call `diagnose_mix` (120s surprise)
**Right:** User says "how does my track sound?" → call `analyze_loudness` + `get_master_spectrum` (1s) → report findings → offer heavy analysis only if needed

### Escalation Pattern for Analysis

Always follow this ladder — start fast, escalate only with consent:

```
Level 1 (instant):  get_master_spectrum + get_track_meters
                    → frequency balance + levels. Enough for 80% of questions.

Level 2 (fast):     analyze_loudness + analyze_dynamic_range
                    → LUFS, true peak, LRA, crest factor. For mastering prep.

Level 3 (slow):     analyze_spectral_evolution + compare_to_reference
                    → timbral trends, reference matching. Ask first.

Level 4 (heavy):    separate_stems → per-stem analysis → diagnose_mix
                    → full diagnostic. Explicit user consent required.
```

Never skip levels. The user's question determines the entry point, but always start at the lowest appropriate level and offer to go deeper.

## Track Health Checks — MANDATORY

**Every track must be verified before you consider it "done".** A track with notes but no sound is a silent failure. Run these checks after building each track.

### After loading any instrument:
1. **`get_track_info`** — confirm the device loaded (`devices` array is not empty, `class_name` is correct)
2. **For Drum Racks: `get_rack_chains`** — confirm chains exist (an empty Drum Rack = silence). You need named chains like "Bass Drum", "Snare", etc.
3. **For synths: `get_device_parameters`** — confirm `Volume`/`Gain` parameter is not 0. Check oscillators are on.
4. **For effects: check `Dry/Wet` and `Drive`/key params** — a Saturator with Drive=0 or a Reverb with Dry/Wet=0 does nothing.
5. **For AU/VST plugins: `get_device_info`** — if `parameter_count` <= 1 and `class_name` contains "PluginDevice", the plugin is dead. Delete and replace with native alternative. Report the failure.
6. **CRITICAL — Sample-dependent instruments produce silence without source material.** These plugins load "successfully" (many parameters) but output nothing until a sample/audio source is provided. Since MCP tools CANNOT load samples into third-party plugin UIs, **NEVER use these as standalone instruments**:
   - **Granular synths:** iDensity, Tardigrain, Koala Sampler, Burns Audio Granular
   - **Samplers without presets:** bare Simpler, bare Sampler (always load a preset, never the empty shell)
   - **Sample players:** AudioLayer, sEGments (need user to load samples via plugin GUI)
   - **Instead use:** Wavetable, Operator, Drift, Analog, Meld, Collision, Tension — these are self-contained synthesizers that produce sound immediately from MIDI input alone.
   - **If granular textures are needed:** Use Wavetable with aggressive wavetable position modulation, or Operator with FM feedback and short envelopes, or load a Simpler/Sampler **preset** (not the bare instrument) from the Sounds browser.

### After programming notes:
1. **`fire_clip` or `fire_scene`** — always listen. If the track has notes but the instrument has no samples/chains, you're playing silence.
2. **Check volume is audible** — `get_track_info` → `mixer.volume` should be > 0.5 for a primary track. Master volume should be > 0.5.

### Device loading rules:
- **NEVER load a bare "Drum Rack"** — it's empty. Always load a **kit preset** like "909 Core Kit", "808 Core Kit", "Boom Bap Kit", etc. Use `search_browser` with path "Drums" and `name_filter` containing "Kit" to find real kits with samples.
- **For synths, prefer `search_browser` → `load_browser_item`** over `find_and_load_device` when the name could match samples (e.g., "Drift" matches "Synth Bass Drift Pad Wonk Bass.wav" before the actual Drift synth).
- **After loading any effect**, verify its key parameters aren't at defaults that make it a pass-through. Set `Drive`, `Dry/Wet`, `Amount` etc. to meaningful values.

### Quick health check pattern:
```
1. get_device_info(track, device)       → class_name? parameter_count?
   - PluginDevice with param_count<=1?  → DEAD PLUGIN. Delete + replace.
   - Is it a sample-dependent plugin?   → SILENT. Replace with self-contained synth.
2. get_track_info(track_index)          → has devices? has clips?
3. get_rack_chains (if Drum Rack)       → has chains with samples?
4. get_device_parameters                → volume > 0? key params set?
5. Check mixer.volume > 0              → track is audible?
6. fire_clip / fire_scene              → sound comes out?
7. REPORT any issues to the user        → never silently work around failures.
```

### Red flags (things that produce silence):
- Empty Drum Rack (no chains)
- Synth with Volume/Gain at 0 or -inf dB
- Effect with Dry/Wet at 0%
- Track volume at 0
- Track muted
- Master volume at 0
- MIDI track with no instrument loaded
- Notes programmed but clip not fired
- **Dead AU/VST plugin** — `parameter_count` <= 1 on a PluginDevice (plugin shell loaded, DSP engine crashed)
- **Sample-dependent plugin with no sample** — granular synths, bare samplers, and sample players load "successfully" with many parameters but produce zero audio without source material. The sneakiest silent failure because `get_device_info` looks healthy.

## Tool Domains (178 total)

### Transport (12)
`get_session_info` · `set_tempo` · `set_time_signature` · `start_playback` · `stop_playback` · `continue_playback` · `toggle_metronome` · `set_session_loop` · `undo` · `redo` · `get_recent_actions` · `get_session_diagnostics`

### Tracks (14)
`get_track_info` · `create_midi_track` · `create_audio_track` · `create_return_track` · `delete_track` · `duplicate_track` · `set_track_name` · `set_track_color` · `set_track_mute` · `set_track_solo` · `set_track_arm` · `stop_track_clips` · `set_group_fold` · `set_track_input_monitoring`

### Clips (11)
`get_clip_info` · `create_clip` · `delete_clip` · `duplicate_clip` · `fire_clip` · `stop_clip` · `set_clip_name` · `set_clip_color` · `set_clip_loop` · `set_clip_launch` · `set_clip_warp_mode`

### Notes (8)
`add_notes` · `get_notes` · `remove_notes` · `remove_notes_by_id` · `modify_notes` · `duplicate_notes` · `transpose_notes` · `quantize_clip`

### Devices (12)
`get_device_info` · `get_device_parameters` · `set_device_parameter` · `batch_set_parameters` · `toggle_device` · `delete_device` · `load_device_by_uri` · `find_and_load_device` · `set_simpler_playback_mode` · `get_rack_chains` · `set_chain_volume` · `get_device_presets`

### Scenes (8)
`get_scenes_info` · `create_scene` · `delete_scene` · `duplicate_scene` · `fire_scene` · `set_scene_name` · `set_scene_color` · `set_scene_tempo`

### Mixing (11)
`set_track_volume` · `set_track_pan` · `set_track_send` · `get_return_tracks` · `get_master_track` · `set_master_volume` · `get_track_routing` · `set_track_routing` · `get_track_meters` · `get_master_meters` · `get_mix_snapshot`

### Browser (4)
`get_browser_tree` · `get_browser_items` · `search_browser` · `load_browser_item`

### Arrangement (19)
`get_arrangement_clips` · `create_arrangement_clip` · `add_arrangement_notes` · `get_arrangement_notes` · `remove_arrangement_notes` · `remove_arrangement_notes_by_id` · `modify_arrangement_notes` · `duplicate_arrangement_notes` · `transpose_arrangement_notes` · `set_arrangement_clip_name` · `set_arrangement_automation` · `back_to_arranger` · `jump_to_time` · `capture_midi` · `start_recording` · `stop_recording` · `get_cue_points` · `jump_to_cue` · `toggle_cue_point`

### Memory (8)
`memory_learn` · `memory_recall` · `memory_get` · `memory_replay` · `memory_list` · `memory_favorite` · `memory_update` · `memory_delete`

### Analyzer (29) — requires LivePilot Analyzer M4L device on master track
`get_master_spectrum` · `get_master_rms` · `get_detected_key` · `get_hidden_parameters` · `get_automation_state` · `walk_device_tree` · `get_clip_file_path` · `replace_simpler_sample` · `load_sample_to_simpler` · `get_simpler_slices` · `crop_simpler` · `reverse_simpler` · `warp_simpler` · `get_warp_markers` · `add_warp_marker` · `move_warp_marker` · `remove_warp_marker` · `scrub_clip` · `stop_scrub` · `get_display_values` · `get_spectral_shape` · `get_mel_spectrum` · `get_chroma` · `get_onsets` · `get_novelty` · `get_momentary_loudness` · `check_flucoma` · `capture_audio` · `capture_stop`

### Automation (8)
Clip automation CRUD + intelligent curve generation with 15 built-in recipes.

**Tools:** `get_clip_automation` · `set_clip_automation` · `clear_clip_automation` · `apply_automation_shape` · `apply_automation_recipe` · `get_automation_recipes` · `generate_automation_curve` · `analyze_for_automation`

**Key discipline:**

**The Feedback Loop (MANDATORY for all automation work):**
1. PERCEIVE: `get_master_spectrum` + `get_track_meters` -> understand current state
2. DIAGNOSE: What needs to change? Use diagnostic filter technique if unsure
3. DECIDE: Which parameter, which curve, which recipe?
4. ACT: `apply_automation_shape` or `apply_automation_recipe`
5. VERIFY: `get_master_spectrum` again -> did it work?
6. ADJUST: If not right, `clear_clip_automation` -> try different curve/params
7. NEVER write automation without reading spectrum first and after

**Rules:**
- Use `analyze_for_automation` before writing — let spectral data guide decisions
- Use recipes for common patterns (filter_sweep_up, dub_throw, sidechain_pump)
- Use `apply_automation_shape` for custom curves with specific math
- Clear existing automation before rewriting: `clear_clip_automation` first
- Load `references/automation-atlas.md` for curve theory, genre recipes, diagnostic technique, and cross-track spectral mapping

### Perception (4) — offline audio analysis, no Ableton connection required
`analyze_loudness` · `analyze_spectrum_offline` · `compare_to_reference` · `read_audio_metadata`

**Key discipline:**
- These work on any local audio file — no Ableton connection needed
- Use `compare_to_reference` for A/B mix comparisons against reference tracks
- Use `analyze_loudness` to check streaming compliance (Spotify, Apple Music, YouTube targets)

### Theory (7)
Music theory analysis — built-in pure Python engine, zero external dependencies.

**Tools:** `analyze_harmony` · `suggest_next_chord` · `detect_theory_issues` · `identify_scale` · `harmonize_melody` · `generate_countermelody` · `transpose_smart`

**Key discipline:**
- These tools read MIDI notes directly from session clips — no file export needed
- Auto-detects key via Krumhansl-Schmuckler if not provided; pass `key` hint for better accuracy
- `analyze_harmony` and `detect_theory_issues` are analysis-only; `harmonize_melody`, `generate_countermelody`, and `transpose_smart` return note data ready for `add_notes`
- Use your own musical knowledge alongside these tools — the engine provides data, you provide interpretation
- Processing time: 2-5s for generative tools (harmonize, countermelody)

### Generative (5)
Algorithmic composition tools — Euclidean rhythms, minimalist techniques.

**Tools:** `generate_euclidean_rhythm` · `layer_euclidean_rhythms` · `generate_tintinnabuli` · `generate_phase_shift` · `generate_additive_process`

**Key discipline:**
- All generative tools return note arrays — use `add_notes` to place them in clips
- `generate_euclidean_rhythm` uses the Bjorklund algorithm and identifies named rhythms (e.g., "tresillo", "cinquillo")
- `layer_euclidean_rhythms` stacks multiple patterns for polyrhythmic textures across tracks
- `generate_tintinnabuli` implements Arvo Pärt's technique: a T-voice (triad arpeggio) against a M-voice (melody)
- `generate_phase_shift` implements Steve Reich's phasing: two identical patterns drifting apart over time
- `generate_additive_process` implements Philip Glass's technique: melody expanded by adding one note per iteration

### Harmony (4)
Neo-Riemannian harmony tools — Tonnetz navigation, voice leading, chromatic mediants.

**Tools:** `navigate_tonnetz` · `find_voice_leading_path` · `classify_progression` · `suggest_chromatic_mediants`

**Key discipline:**
- These tools work with chord names and return harmonic relationships — no clip MIDI required
- `navigate_tonnetz` returns PRL (Parallel, Relative, Leading-tone) neighbors for any chord
- `find_voice_leading_path` finds the shortest harmonic path between two chords through Tonnetz space
- `classify_progression` identifies the neo-Riemannian transform pattern in a chord sequence
- `suggest_chromatic_mediants` returns all chromatic mediant relations with film score usage notes
- Opycleid library provides full Tonnetz; falls back to pure Python PRL if not installed

### MIDI I/O (4)
MIDI file import/export — works with standard .mid files on disk.

**Tools:** `export_clip_midi` · `import_midi_to_clip` · `analyze_midi_file` · `extract_piano_roll`

**Key discipline:**
- `export_clip_midi` exports a session clip's notes to a .mid file at the specified path
- `import_midi_to_clip` loads a .mid file into a clip, replacing existing notes
- `analyze_midi_file` performs offline analysis of any .mid file (tempo, notes, structure) — does not require Ableton connection
- `extract_piano_roll` returns a 2D velocity matrix (pitch × time) from a .mid file for visualization or processing
- Dependencies: midiutil (export), pretty-midi (import/analysis) — lazy-loaded, ~5 MB total

## Workflow: Building a Beat

1. `get_session_info` — check current state
2. `set_tempo` — set your target BPM
3. `create_midi_track` — create tracks for drums, bass, chords, melody
4. Name and color each track with `set_track_name` / `set_track_color`
5. **Load instruments with PRESETS, not empty shells:**
   - **Drums:** `search_browser` path="Drums" name_filter="Kit" → pick a kit → `load_browser_item`. NEVER load bare "Drum Rack".
   - **Synths:** `search_browser` path="Instruments" name_filter="Drift" → `load_browser_item` with exact URI. Avoids sample name collisions.
   - **VERIFY:** `get_rack_chains` for drums (must have chains), `get_device_parameters` for synths (Volume > 0)
6. `create_clip` — create clips on each track (4 beats = 1 bar at 4/4)
7. `add_notes` — program MIDI patterns. Each note needs `pitch`, `start_time`, `duration`
8. **HEALTH CHECK per track:** `get_track_info` → confirm device loaded, mixer volume > 0, not muted
9. **PITCH & TUNING AUDIT (MANDATORY before firing):**
   - `identify_scale` on every melodic track — verify all tracks share the same tonal center
   - `analyze_harmony` on chordal tracks — verify chord quality (no accidental augmented/diminished)
   - `detect_theory_issues` with `strict=true` — check out-of-key notes, parallel fifths, voice crossing
   - **Interpret against intended scale:** The analyzer only knows 7 standard modes. Exotic scales (Hijaz, Hungarian minor, whole tone, etc.) produce false "out of key" warnings. Cross-reference flagged pitches against the intended scale manually.
   - Report a clear tuning table to the user before proceeding
   - Fix wrong notes with `modify_notes` before firing
10. `fire_scene` or `fire_clip` — listen to your work
11. Iterate: `get_notes` → `modify_notes` / `transpose_notes` → listen again

## Workflow: Sound Design

1. Load a synth: `search_browser` path="Instruments" → `load_browser_item` with exact URI
2. **VERIFY:** `get_device_parameters` — confirm Volume/Gain > 0, oscillators on, filter not fully closed
3. `set_device_parameter` — tweak individual params by name or index
4. `batch_set_parameters` — set multiple params at once for a preset
5. Load effects: `find_and_load_device` with "Reverb", "Delay", "Compressor", etc.
6. **VERIFY each effect:** `get_device_parameters` — confirm Dry/Wet > 0, Drive/Amount set to meaningful values. An effect at default may be a pass-through.
7. Chain devices: they stack in order on the track's device chain
8. Use `get_device_info` to inspect rack devices, `get_rack_chains` for racks

## Workflow: Mixing

1. `get_session_info` — see all tracks and current levels
2. `get_mix_snapshot` — one-call overview of all levels, panning, routing, mute/solo
3. `set_track_volume` / `set_track_pan` — set levels and stereo position
4. `set_track_send` — route to return tracks for shared effects
5. `get_return_tracks` — check return track setup
6. `set_master_volume` — final output level
7. `set_track_routing` — configure input/output routing
8. `get_track_meters` / `get_master_meters` — check real-time output levels

### With LivePilot Analyzer (M4L device on master):
9. `get_master_spectrum` — check frequency balance across 8 bands (sub → air)
10. `get_master_rms` — true RMS and peak levels
11. `get_detected_key` — detect musical key before writing harmonies/bass
12. `get_hidden_parameters` — see ALL device params including hidden ones
13. `get_automation_state` — check which params have automation before overwriting
14. `walk_device_tree` — inspect nested racks and drum pads
15. `get_display_values` — human-readable parameter values ("440 Hz", "-6 dB")

## Workflow: Sample Chopping

1. Resample your beat to an audio track (set input to Resampling, arm, record)
2. `get_clip_file_path` — get the audio file path of the recorded clip
3. Load Simpler on a new MIDI track (with any sample pre-loaded)
4. `replace_simpler_sample` — load the resampled audio into Simpler
5. `set_simpler_playback_mode` — set to Slice mode
6. `get_simpler_slices` — see all auto-detected slice points
7. Program MIDI patterns targeting slice indices
8. Use `reverse_simpler` / `crop_simpler` / `warp_simpler` for transformations
9. `get_master_spectrum` — verify the result through the analyzer

## Workflow: Time Manipulation

1. `get_warp_markers` — see current timing map of an audio clip
2. `add_warp_marker` — pin key beats (downbeats, snare hits)
3. `move_warp_marker` — stretch/compress specific segments for tempo effects
4. `scrub_clip` / `stop_scrub` — preview specific positions
5. `get_master_spectrum` — verify the result sounds right
6. `remove_warp_marker` — clean up if needed

## Live 12 Note API

Notes use this format when calling `add_notes`:
```json
{
  "pitch": 60,
  "start_time": 0.0,
  "duration": 0.5,
  "velocity": 100,
  "mute": false
}
```

When reading with `get_notes`, you also get:
- `note_id` — unique ID for modify/remove operations
- `probability` — 0.0-1.0, Live 12 per-note probability
- `velocity_deviation` — -127.0 to 127.0
- `release_velocity` — 0.0-127.0

Use `modify_notes` with `note_id` to update existing notes.
Use `remove_notes_by_id` for surgical deletion.
Use `transpose_notes` for pitch shifting a region.
Use `quantize_clip` to snap notes to a grid (grid is an enum: 1=1/4, 2=1/8, 5=1/16, 8=1/32).

## Technique Memory

LivePilot has a persistent memory system for saving and recalling techniques — beats, device chains, mixing setups, browser pins, and preferences — with rich stylistic analysis.

### Three Modes of Operation

**Informed (default):** Before creative decisions, consult memory:
```
memory_recall(query relevant to the task, limit=5)
```
Read the qualities of returned techniques. Let them INFLUENCE your choices — instrument selection, parameter ranges, rhythmic density, harmonic language — but always create something new. The memory shapes your understanding of this user's taste, not a template to copy.

**Fresh (user override):** When the user signals a clean slate:
- "ignore my history" / "something completely new" / "fresh"
- "don't look at my saved stuff" / "surprise me"
→ Skip memory_recall entirely. Use only the shipped corpus and your own musical knowledge.

**Explicit Recall:** When the user references a saved technique:
- "use that boom bap beat" / "load my lo-fi chain" / "remember that thing I saved?"
→ `memory_recall` to find it → `memory_get` for full payload → `memory_replay` (adapt=false for exact, adapt=true for variation)

### Saving Techniques

When the user says "save this" / "remember this" / "I like this":

1. Collect raw data using existing tools (get_notes, get_device_parameters, etc.)
2. Write the qualities analysis — see `references/memory-guide.md` for the template
3. Call `memory_learn` with type, qualities, payload, tags
4. Confirm to the user what was saved and how it was characterized

### Memory Tools (8)

| Tool | What it does |
|------|-------------|
| `memory_learn` | Save a technique with qualities + payload |
| `memory_recall` | Search by text query, type, tags — returns summaries |
| `memory_get` | Fetch full technique by ID (with payload) |
| `memory_replay` | Get replay plan for agent to execute |
| `memory_list` | Browse library with filtering and sorting |
| `memory_favorite` | Star and/or rate (0-5) a technique |
| `memory_update` | Update name, tags, or qualities |
| `memory_delete` | Remove (creates backup first) |

## Reference Corpus

Deep production knowledge lives in `references/`. Consult these when making creative decisions — they contain specific parameter values, recipes, and patterns. Use them as starting points, not rigid rules.

| File | What's inside | When to consult |
|------|--------------|-----------------|
| `references/overview.md` | All 178 tools mapped with params, units, ranges | Quick lookup for any tool |
| `references/midi-recipes.md` | Drum patterns by genre, chord voicings, scales, hi-hat techniques, humanization, polymetrics | Programming MIDI notes, building beats |
| `references/sound-design.md` | Stock instruments/effects, parameter recipes for bass/pad/lead/pluck, device chain patterns | Loading and configuring devices |
| `references/mixing-patterns.md` | Gain staging, parallel compression, sidechain, EQ by instrument, bus processing, stereo width | Setting volumes, panning, adding effects |
| `references/ableton-workflow-patterns.md` | Session/Arrangement workflow, song structures by genre, follow actions, clip launch modes, export | Organizing sessions, structuring songs |
| `references/m4l-devices.md` | Browser organization, MIDI effects, rack systems, device loading patterns | Finding and loading devices, using racks |
| `references/memory-guide.md` | Qualities template, good/bad examples for each technique type | Saving techniques, writing qualities |
| `references/automation-atlas.md` | Curve theory, perception-action loop, genre recipes, diagnostic filter technique, spectral mapping | Writing automation, choosing curves, mixing with spectral feedback |
登录后下载/点赞/收藏 ❤ 5 | ★ 0
livepilot-core

目录结构

SKILL.md

举报内容

提示
