Review a velocity change before downloading.

What changes?

The first note on track 1 changes from velocity 100 to 92. Its length remains 0.5 quarter-note beats. Pitch, note start, the other seven notes and other XML stay unchanged.

This edit is made with CutTempo's bounded patch and reparse verification code. It was not generated by an AI response to your instruction.

• Input: generated symbolic XML, compressed as .als.
• Authorized range: the first track's clip, beats 0–4.
• Output: a candidate with the single velocity change.

Download original sample (419 bytes) · Download edited sample (428 bytes).

Try the review workflow

1. Open the workspace and choose Try symbolic sample.
2. Confirm the track and clip-local beat range.
3. Open the note inspector, change a velocity, then save and verify the candidate.
4. Compare the changes, restore a note if needed, and download the candidate.

Manual editing does not need an AI generation request. Inspection and candidate saving still use the cloud service. The A/B preview uses simple sine voices and an assumed tempo.

What still needs Ableton verification?

This sample was not exported by Ableton Live. It is not a complete Live project and does not establish compatibility. No Live version has yet been verified for opening, instrument playback, continued editing, saving and reopening a CutTempo candidate.

A real case must start with a self-created, supported Live Set, retain its original, and check the downloaded candidate in the same Live version. Read the supported-file and verification guide before using your own material.