Prepare a small set. Check the result in Live.

Current supported input

• Ableton .als files, up to 300 KB (300,000 bytes).
• No more than 256 MIDI notes across the file.
• At most one complete MIDI clip per track.
• Editable clips with identifiable source IDs and known loop boundaries.

The current workflow does not accept .mid or .midi files. A full song, a complex arrangement or a set with multiple clips on a track may exceed this scope. Choosing a file uploads it to the inspection service immediately. Read the privacy policy before importing your material.

What an accepted edit can change

• Velocity stays within 1–127 and within ±24 units of the original note’s value.
• Duration stays between 0.5× and 1.5× the original note’s duration.
• Note pitches, starts, source note IDs and note count stay fixed.

Confirm the editable tracks and a range within their clips before generation. This range uses clip-local quarter-note beats, not global song bars. It must fit the known loop boundaries of every selected clip. Both each edited source note’s complete interval and its proposed interval must stay inside the range.

For example, a note lasting 0.5 beats may become 0.25–0.75 beats, provided the full interval still fits the confirmed range. A request to change only one field expresses intent; always review both velocity and duration.

Prepare a compact working copy

Keep your original. For Session View material, Ableton documents this route to a new Live Set:

1. Select at least two MIDI Session clips, choosing no more than one per track.
2. Drag the selection into Current Project or a user folder in Live’s browser.
3. Name the new set and locate its .als file.
4. Check its size, clip count and note count before importing it into CutTempo.

Dragging a single clip to the browser saves a Live Clip (.alc), not an .als set. For a single-clip edit, use Save Live Set As to make a working copy first. In that copy, remove unused tracks and other clips from both Session and Arrangement View, then save again. Devices and other project data can still make the file exceed 300 KB.

These preparation steps follow Ableton’s Managing Files and Sets manual. They are not evidence that the exported copy or a CutTempo candidate will open in Live. See the pending verification steps below.

Try a synthetic example first

The symbolic example shows a deterministic velocity change and offers original and edited .als downloads. Its XML is generated for demonstration. It was not exported by Live and is not a complete Live project or proof of compatibility.

Ableton host verification: pending

No Live version or edition has yet been verified for the full round trip. A meaningful check starts with a self-created, supported set and retains its original:

1. Record the exact Live version, edition and operating system.
2. Confirm that the original opens and plays correctly in that Live version.
3. Import the small copy, make a bounded edit, review it, and download the candidate.
4. Open the candidate in the same Live version and check for warnings or missing media.
5. Compare pitches, note starts, dynamics and lengths through the intended instruments.
6. Edit a note, save the candidate, close it, and reopen it to confirm continued use.

A successful XML reparse or download checks a different boundary. Report the outcome, version and any warning to support@borealbit.com. Read the FAQ for demo access, uploads and account storage.