Troubleshooting

Symptom → Cause → Solution → Prevention.

For first-time setup see Getting Started. For build rule names see How to read build errors.

Live connection

Patchwright says host not connected

Cause: Extension Host path wrong, Live not running, or unsupported Live version.

Solution:

  1. Open Host… on the toolbar.
  2. Point to Live 12 Suite beta Extension Host module (see Getting Started).
  3. Start Live with Developer Mode on.
  4. Click Build & Run again.

Prevention: Save a working host path after first success.

Build & Run succeeds but Live never shows “connected”

Cause: Bridge or Live Extensions not enabled.

Solution: Confirm Developer Mode; restart Live; rebuild.

Prevention: Follow Getting Started checklist once per machine.

Command missing in Live

My command is not in the Extensions menu

Cause: Wrong object type, extension not installed, or Live needs refresh.

Solution:

  1. Right-click the object type matching your trigger (MIDI clip vs track, etc.).
  2. Re Build & Run after edits.
  3. Restart Live if the command is new.
  4. Check menu label: ExtensionName: MIDI Clip — the On prefix is stripped from the trigger label before it appears in the menu (find command).

Prevention: Choose the right trigger.

Command appears but does nothing

Cause: Run chain broken, async error, or wrong target wired.

Solution: Check Run log (tab in the right-side panel); verify Run wires from trigger through setters; test on empty clip first.

Prevention: Use a template, then change one thing at a time.

Build failures

Build failed — unwired object input

Cause: A setter or action needs obj wired to a clip/track/etc.

Solution: Wire trigger target or upstream result to obj.

Prevention: Core Concepts — params vs wires.

Build failed — dialog or progress inside undo group

Cause: Show Dialog or Progress Dialog inside Transaction body.

Solution: Move dialog before Transaction; wire answers into body chain.

Prevention: Dialogs and progress.

Build failed — wire type mismatch

Cause: Incompatible port types (e.g. Audio clip into MIDI notes).

Solution: Change trigger or use correct getter (MidiClip.notes for MIDI).

Prevention: Node Reference — Compatibility.

Build failed — HTTP not HTTPS

Cause: Literal URL in HTTP Fetch uses http://.

Solution: Use https:// only.

Prevention: Core Concepts — sandbox.

PatchAI

AI panel will not connect

Cause: API key or local endpoint not set in AI Assistant panel.

Solution: Set up AI providers — not Settings.

Prevention: Test provider with a one-line prompt before complex graphs.

AI graph fails to build

Cause: Invalid node ids or constraint violations.

Solution: Ask PatchAI to fix; or read build errors.

Prevention: Write a good prompt naming trigger and undo needs.

Canvas and editing

Cannot connect two ports

Cause: Type mismatch or exec vs data.

Solution: Check port types; use subclass direction (MidiClip → Clip OK, not reverse).

Prevention: Core Concepts — matching types.

Delete key does nothing

Cause: Canvas focus or nothing selected.

Solution: Click canvas background, select node(s), Delete / Backspace or context menu.

Prevention: Delete nodes.

Export and install

`.ablx` installs but command missing on other Mac

Cause: Different Live version or Developer Mode off.

Solution: Match Live 12.4.5+ Suite beta; enable Developer Mode; reinstall package.

Prevention: Tutorial 7 — Export.

Still stuck?

  1. Getting Started
  2. How-To index
  3. Node Reference
  4. Early access / contact for private alpha support