Managing Projects
On the T1, a Project is the complete state of the device.
A Project includes:
- all 16 Banks
- the Patterns and Tracks inside those Banks
- the relevant saved settings associated with that state
Projects can be backed up to a computer and restored later using T1 Config.
Inside a Project, your day-to-day work happens mainly through Banks, Patterns, Tracks, autosave, and manual Bank saving.
Projects on the T1
A Project is the top-level state of the T1.
When you work on the device, you are always working inside the current Project. That Project holds all of the Banks you use, the Patterns inside them, and the saved settings associated with that overall state.
This is important because the T1 supports both:
- working directly on the device
- saving or restoring the full Project through T1 Config
So when the docs refer to a Project, it means the full T1 state, not just one Bank or one Pattern.
Autosave vs Manual Bank Save
This is the most important working distinction to understand on the T1.
Autosave
The T1 continuously autosaves your current working state.
That means:
- your recent work is 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 just to protect in-progress work
Autosave is ideal for:
- sketching
- experimenting
- live development
- making incremental changes while composing
Manual Bank Save
Manual Bank saving writes the current Bank state intentionally.
That matters when you want to:
- preserve a known-good version
- create something stable you can come back to later
- store a prepared performance state
- avoid losing a version you may want to reload
In short:
- autosave is for continuity while working
- manual Bank save is for commitment and recall
Reloading a Bank
Reloading is the counterpart to manual Bank saving.
When you reload a Bank, you discard the current unsaved changes and return that Bank to its last saved state.
This is useful when:
- an experiment went too far
- you want to undo broad changes
- you want to return to a prepared version before a performance
- you want confidence that a Bank is back in its known saved state
This is one of the main reasons to save deliberately even though autosave exists: reload only helps if there is a saved Bank state worth returning to.
Two Kinds of Saving
The T1 works with two different levels of saving:
Bank saving
Bank saving stores one Bank state inside the current Project on the T1.
Use Bank saving when you want to:
- preserve a version of one Bank
- create a restore point for that Bank
- 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 device state
- transfer a setup
- restore all Banks and settings later
- keep external backups of complete T1 states
This distinction is essential:
- Bank save affects one Bank inside the current Project
- Project backup affects the complete Project
Backing Up the Full Project
To save or restore the complete T1 state, use the Project menu in T1 Config.
This is different from saving or reloading a Bank on the device.
Use T1 Config when you want to:
- download the current Project from the T1
- upload a previously saved Project to the T1
- keep full backups of all Banks and settings
- restore a complete working environment later
For full backup and restore instructions, see T1 Config: Project.
Performance Mindset
Project management is not only for studio work. It also matters in performance.
Before a live session, it is often useful to:
- save Banks you know you want to perform with
- verify which Patterns inside them are your main entry points
- treat reload as a way to recover a prepared Bank state
- make a full Project backup in T1 Config if the complete setup matters
In that context, autosave is convenient, but deliberate Bank saving and Project backup are what give you dependable recall.
Tips
- Treat the Project as the full T1 state.
- Treat Banks as your main musical containers inside that Project.
- Treat Patterns as sections or variations inside a Bank.
- Let autosave protect your day-to-day work.
- Use manual Bank save whenever you reach a version you know you may want back.
- Save a Bank before making bold changes if you think you may want to reload later.
- If an idea starts feeling like a separate song, setup, or sketch, move it to a different Bank.
- Use T1 Config when you want to back up or restore the complete Project.