Studio LABS · Checkpoint 072

Write the music. Understand every column.

Three exact, version-checked CSV references for musicians and AI assistants. Compose parts in a spreadsheet or text editor, then import them into Studio.

Download the three blank templates (.zip)

Blank templates are not songs: each CSV contains one header row and no events. Complete the required music, tempo, meter and timing values before importing. The newer per-event stereo-panning fields are optional; legacy layouts remain supported by RC1.

Tracks 1–2

Piano Roll / Pitched CSV

Piano, keyboards, strings and other pitched instruments; Track 2 may use a Double Bass SoundFont without becoming TAB.

86 RC1 columns · compatible with 85-column legacy files

Read the complete reference

Tracks 3–4

Guitar TAB CSV

Tracks 3 and 4 are both six-string Guitar TAB; string 1 to 6 each has independent panning.

135 RC1 columns · compatible with 129-column legacy files

Read the complete reference

Tracks 5–6

Drums CSV

Track 5 is Acoustic Drums; Track 6 is Electronic Drums. Both use the same event columns and a separate kit mapping.

21 RC1 columns · compatible with 20-column legacy files

Read the complete reference

For musicians and AI assistants

Use the exact header spellings and order supplied in the templates. Do not silently add, remove, rename or reorder columns. CSV files use UTF-8 and ordinary quoted CSV cells. Keep the human composer's musical intent authoritative.

Use the sample event files to see valid input. The data dictionary contains every field and guidance for empty cells; the Studio RC1 Rust/WASM validator is the final authority on acceptance. The field explanations from the November 19 developer draft have been retained and reconciled to RC1 headers; where only examples rather than exhaustive validation are known, they are labelled as guidance rather than guarantees.

For generative workflows, retrieve the machine-readable AI index and the complete per-format field dictionaries.