Files
ep-133-project-export/docs/research/ep133-musician-audit/README.md

5.7 KiB

EP-133 musician-to-Live 10 translation audit

This research set asks a musician's question rather than a file-format question:

If a finished EP-133 project sounds and behaves a certain way in the hands of its creator, which parts of that musical work appear in the exported Ableton Live 10 set?

It deliberately does not propose code changes. It supplies a musical reference project and a diagnostic vocabulary that can be used before implementation decisions are made.

Files

The three kinds of musical truth

Kind Meaning Example What an archive-based exporter can know
Saved state Data represented in project/sample files notes, pad trim, song positions, recorded fader motion Potentially knowable if the format is decoded
Baked audio A gesture whose result became a new WAV a chord resampled while changing reverb X/Y The resulting sound is knowable; the original gesture and device chain are not necessarily recoverable
Live-only performance A gesture heard during a performance but not recorded into project data punch-in FX, temporary loop, group solo Not recoverable from a later backup unless it was resampled or recorded externally

This distinction is essential. “Not present in the Live set” can mean four different things:

  1. the EP saved it and the exporter translated it;
  2. the EP saved it but the exporter approximated or omitted it;
  3. the EP baked it into sample audio, so only the audible result survives;
  4. the EP never saved it, so an archive export cannot reconstruct it.

Audit vocabulary

Status Meaning
Represented The current exporter creates a usable Live counterpart from the saved data. This does not imply bit-identical audio.
Approximate The musical intent is present, but device behavior or parameter scaling differs.
Partial Some required state is translated and some is omitted or misread.
Missing The EP state is available or strongly evidenced, but the current exporter does not put it in Live.
Baked only Live can receive the rendered sample, not the process that created it.
Unknowable from archive The gesture is not part of the saved project/sample state.
Unresolved More EP-side evidence is needed before the expected translation can be stated safely.

Evidence policy

Musical behavior is taken primarily from the current official EP-133 v2.5 guide and release notes. Community tutorials are used to understand how musicians combine the features into songs, not as authority for binary offsets or DSP laws. Binary claims are checked against the supplied OS 2.5.1 backup and the local parser.

The imaginary project is not a claim that a particular TAR already exists. It is a design oracle: every item should either be possible on the device, explicitly identified as a live gesture, or marked as an open question.

Primary sources

Musician-workflow references