Live Passes the API, Fails the Fit

"A real API is necessary, not sufficient. Live opens the door — into the wrong room."

Live Clears the Bar Logic Couldn't

Ableton Live is the interesting case because it passes the condition that killed Logic. Live has the Live Object Model, reachable through projects like ableton-js and AbletonOSC — a genuine, documented way for an outside program to read and drive a Live set. Condition 2: passed. If the three-condition test were just 'does it have an API,' Live would be the host. It isn't, and the reasons are conditions 3 and the value test.

Two Failures Behind the Open Door

Ableton Live            condition          verdict
------------            ---------          -------
LOM (ableton-js)        (2) API            PASS  -- MIDI/session R/W
Dad lives in Live?      (3) residency      FAIL  -- Dad uses Logic
value: audio analysis   (core fit)         FAIL  -- LOM gives MIDI, not
                                                   audio -> chords/key

Condition 3 fails: Dad works in Logic and only reinstalled Live to evaluate the idea — a sidecar to a host you don't live in is a sidecar to nobody. And the value test fails independently: the LOM exposes MIDI notes and session structure, but not audio analysis. Bonfire's core need — audio → chords/key/tempo — still requires Python MIR no matter what. Live's API gives you the wrong things very well. A DAW does production chores; it doesn't do analysis chores.

The Lesson: API Is Necessary, Not Sufficient

Live is the proof that clearing the API gate doesn't win the game. You also need the user to actually live there, and you need the API to expose the thing your product is about. Live misses both: wrong room (production, not analysis) and wrong building (Logic is where Dad works). So even the DAW that can be extended turns out not to be the host Bonfire wants — which points, again, at independence.

Code

Live's scorecard — passes the API, fails the fit·text

Ableton Live            condition          verdict
------------            ---------          -------
LOM (ableton-js)        (2) API            PASS  -- MIDI/session R/W
Dad lives in Live?      (3) residency      FAIL  -- Dad uses Logic
value: audio analysis   (core fit)         FAIL  -- LOM gives MIDI, not
                                                   audio -> chords/key

# Passing (2) is necessary, not sufficient.
# Wrong room (production, not analysis) + wrong building (Logic).

Exercise

Find a tool with a real, documented API and ask the two questions beyond 'does the API exist?': do your users actually live in this host, and does the API expose the thing your product is about (not just adjacent things)? A 'yes' to API plus a 'no' to either of these is the Live situation — an open door into the wrong room.

Hint

The value-test trap is subtle: an API can be rich and well-documented while exposing everything EXCEPT the one capability you need. Rich-but-adjacent is still a miss.