Ableton Als Templates

• Treat .als as fragile. Copy from a working set instead of inventing structure from scratch.
• vazio in this workflow means: no devices, plugins, or samples on tracks. It may still include clips, scenes, locators, and arrangement guidance.
• Keep clip type aligned with track type.
  • MidiTrack -> MidiClip
  • AudioTrack -> AudioClip
• If the user wants guide clips but no sample dependency, prefer MidiTracks.
• Use conservative renames and track reordering instead of deep structural mutations when possible.

Avoid

Do not do these unless the user explicitly wants to risk Live compatibility:

• editing real GroupTrack internals by hand
• inventing unsupported XML branches from scratch
• mixing MidiClip into audio tracks or AudioClip into MIDI tracks
• relying on Max for Live as the primary path for arrangement generation

Arrangement Heuristics

When the user asks for an arrangement template, optimize for what enters and leaves over time:

• intro: atmosphere, promise, partial groove
• build: tension, implication, transitions
• drop 1: first full delivery
• variation/turn: maintain energy with changes
• breakdown: remove floor, expose musicality
• rebuild/lift: bring back motion gradually
• drop 2: apex or denser return
• outro: dismantle in layers

For less square templates, add sub-sections such as INTRO_A, INTRO_B, TURN, or LIFT instead of rigid 16x16 blocks.

File Editing Notes

Use a script or shell workflow that can safely read and write gzip XML. Validate at least these points after editing:

• set tempo is correct
• expected number of tracks exists
• locators exist at the intended beat positions
• arrangement/session clip counts for a few anchor tracks match expectations
• the output file is still gzip-readable XML

References

For reusable section patterns and naming conventions, read references/patterns.md.