Choose the right trigger

Goal: Pick where your command appears in Live’s right-click menu so it always targets the right object.

Time: ~5 minutes

Steps

  1. Open your graph in Patchwright and find the trigger node for your target scope — labeled On [Scope] (e.g., On MIDI Clip, On Audio Clip) — or add one from the palette under Triggers.
  2. Open the trigger’s settings and choose a scope — for example On MIDI Clip, On MIDI Track, On Scene, On Audio Track, or On Sample.
  3. Match the scope to what you want to change:
    • Clip name, color, or notes → On MIDI Clip (for MIDI) or On Audio Clip (for audio only).
    • New track, device, or track volume → On MIDI Track or On Audio Track as appropriate.
    • Scene-wide actions → On Scene.
  4. Wire the trigger’s target output to the nodes that need the clicked object (clip, track, device, etc.).
  5. Wire Run from the trigger into the first step of your tool (dialog, transaction, or action).
  6. Set Extension name on the toolbar and Build & Run to register the command in Live.
  7. In Live, right-click the same kind of object you chose in step 2 and look under Extensions for your command.

Expected result

Your command shows up only on the menu where you expect it (for example, only when you right-click a MIDI clip). The target wire carries the object you clicked, so setters and getters work without asking the user to pick a clip again.

If something goes wrong

Problem What to do
Command missing from menu Confirm Developer Mode and Extensions are enabled in Live; rebuild after changing the trigger
Command on wrong menu Change trigger scope to match what you right-click (clip vs track vs scene)
“Unwired obj” build error Wire target (or context) into every node that needs a clip, track, or song
Two tools, one menu item Add a second trigger node — each trigger becomes its own menu command
Audio clip tool on MIDI clip Use On Audio Clip for audio-only; On MIDI Clip for note editing

See also