Data Structure
The T1's Internal Data Structure
Structure Overview
The T1 organizes musical information in a clear hierarchy designed for performance, composition, and recall.
At the highest level, the T1 works with a Project. Inside that Project, musical data is organized into Banks, Patterns, Tracks, and Cycles.
| System Element | Description |
|---|---|
| Project | The complete T1 state, including all 16 Banks and the related saved settings. |
| Bank | Contains 16 Patterns and the Bank's shared Tempo. |
| Pattern | Contains up to 16 Tracks. |
| Track | Generates or processes musical behaviour and targets a destination such as Note, CC, or FX. |
| Cycle | A per-Track snapshot used to change that Track's state across loop repetitions (up to 16 per Track). |
A practical way to think about the hierarchy is:
- a Project contains all 16 Banks
- a Bank contains 16 Patterns
- a Pattern contains up to 16 Tracks
- a Track can contain up to 16 Cycles
What a Project Contains
A Project is the complete working state of the T1.
A Project includes:
- all 16 Banks
- the Patterns and Tracks inside those Banks
- the relevant saved settings associated with that overall state
Projects can be backed up to a computer and restored later using T1 Config.
This makes Project the highest level of organization on the T1.
Banks
A Bank is a major musical container inside a Project.
Each Bank contains:
- 16 Patterns
- the Bank's Tempo
- the saved state associated with that Bank
Banks are useful for separating larger ideas such as:
- one song
- one live setup
- one sketch
- one family of related variations
Read more: Banks & Patterns
Patterns
A Pattern is a section or variation inside a Bank.
Patterns are useful for organizing different states of the same larger musical idea, such as:
- intro
- main groove
- variation
- breakdown
- alternate harmonic or rhythmic state
A useful mental model is:
- Bank = one song, setup, or sketch space
- Pattern = one section or variation inside that Bank
Read more: Pattern Menu
Tracks
A Track is an individual musical lane inside a Pattern.
Tracks are where sequencing and performance behavior happen. A Track can operate in different modes such as:
- Note
- CC
- FX
Each Track holds the musical behavior that defines how it plays, generates notes, sends control data, or processes incoming material.
Read more: Tracks
Cycles
A Cycle is a per-Track state used to make that Track evolve over repeated loop passes.
Cycles let one Track behave differently on successive repetitions of the same Pattern without changing Pattern or Bank.
Each Track can store up to 16 Cycles.
In practical terms, Cycles are useful when you want:
- variation across repetitions
- evolving phrases inside one Pattern
- multiple states for one Track without switching to another Pattern
Read more: Cycles
Sequencer Structure
The sequencer engine consists of different algorithms that control triggers, pitch, velocity, timing, and other musical behavior. These algorithms generate the final output sequence.
Saving, Reloading, and Backup
The T1 works with two different levels of saving:
Bank save
Manual Bank saving stores one Bank state inside the current Project.
Use Bank save when you want to:
- preserve a known version of one Bank
- create a restore point before experimenting
- reload that Bank later
Project backup
Project backup saves the complete T1 Project to your computer using T1 Config.
Use Project backup when you want to:
- archive the full T1 state
- transfer a setup
- restore all Banks and settings later
- keep external backups of complete device states
This distinction is important:
- Bank save affects one Bank inside the current Project
- Project backup affects the complete Project
Autosave
The T1 continuously autosaves your current working state while you work.
That means:
- recent edits are normally preserved automatically
- the previously used Bank and its working state can be restored after restart
- you do not need to manually save every small change while composing
Autosave is for continuity while working. Manual Bank saving is for deliberate recall.
Read more: Managing Projects
T1 Config and Full Project Backup
Use T1 Config when you want to save or restore the complete Project.
This is different from saving or reloading a Bank on the device.
Use T1 Config to:
- download the current Project from the T1
- upload a previously saved Project to the T1
- keep full backups of all Banks and settings
Read more: T1 Config: Project
When preparing a live set, manually save important Banks after final tweaks. If the full device state matters, also create a Project backup in T1 Config.