Small decisions. Interesting possibilities.Submit contentSubmit

live-jev

Control Ableton Live with one short sentence (Japanese / English). Summon with ⌘⇧Space, type or dictate, done.

Added to Jevfast

How it uses Jev

A typed or dictated command and the relevant names from the open Ableton set go to Jev when local phrase rules cannot resolve the request. Jev selects from code-built choices; the service validates targets and sends allow-listed operations through Live’s Remote Script.

What Jev decides

Illustrative Jev requestExample answers · not a recorded Jev response · Source ↗
Question 1 · track stated
YOUR APP
INSTRUCTION

Does the utterance name the track, instrument, or part that receives the action?

STATE

Spoken utterance and current Live tracks/returns/master with track names and settings.

JEV · CHOICE
  1. named
  2. reference
  3. absent

App workflow

  1. Enter a command

    The user summons the overlay and types or dictates a short English or Japanese request.

  2. Resolve intent

    Local phrase handling covers fixed commands; otherwise Jev picks among typed choices using the sentence and relevant set names.

  3. Validate the operation

    The service checks the requested target and operation against current Live state and the allow-list; each part of a command chain must pass first.

  4. Apply and retain a receipt

    The Python Remote Script changes Live. Supported value edits retain a prior-value receipt for a guarded one-step undo.

Why it is interesting

The command bar gets out of the way after entry, and complex commands are validated as a whole before any edit. Supported edits keep receipts for guarded undo; unsupported changes are left to Live’s own undo.