Thinking in Cycles
Cycles let a Track change over time without needing a new Pattern. Instead of a sequence repeating exactly the same way on every loop, the T1 can move through multiple stored variations of that Track across repeated passes.
A useful mental model is:
- Patterns define structure
- Cycles define development inside that structure
This is one of the main ways the T1 creates longer musical form from compact material. A single Pattern can keep its identity, while individual Tracks evolve over time through Cycles.
In practice, Cycles are useful for creating:
- evolving repetition instead of static looping
- longer phrases from short material
- Track-level variation without changing the whole Pattern
- structured movement between sparse, dense, tense, or relaxed versions of the same idea
Because Cycles are per Track, they let you add movement to one part while the rest of the Pattern stays stable.
Pattern changes affect the whole project, while Cycle changes reshape just one Track over repeated loop passes.
For the detailed parameter behavior and editing workflow, see Cycles.
How to Think About a Cycle
A useful way to think about a Cycle is as a version of the same Track over time.
Each Cycle can hold a different state of the Track. That state might differ in subtle ways or in more dramatic ones depending on what you change.
For example, one Track might use:
| Cycle | Content |
|---|---|
| 1 | A minimal starting point |
| 2 | More Pulses |
| 3 | Stronger Accent or timing changes |
| 4 | A lighter reset or release |
The Track still belongs to the same Pattern, but it no longer feels static. Instead, it behaves more like a phrase that develops as the Pattern repeats.
A Simple Example Workflow
If you are new to Cycles, try this:
- Create a Track with a simple rhythm.
- Set up 4 Cycles.
- Leave Cycle 1 mostly minimal.
- In Cycle 2, add a few more Pulses or stronger Accent.
- In Cycle 3, add more movement using Timing, Voicing, or Range.
- In Cycle 4, simplify the Track again or create a small release.
Now let the Pattern repeat and listen to how the Track develops over time.
This is often the easiest way to understand Cycles: not as abstract states, but as musical stages of one Track.
When to Use Cycles
Cycles are especially useful when you want:
- more variation without creating more Patterns
- a Track to evolve independently from the rest of the Pattern
- longer phrases built from short loops
- a sense of arrangement inside a repeating sequence
- one Track to feel alive while others stay stable
If a Pattern already feels strong but too repetitive, Cycles are often the next thing to reach for.
Tips
- Start with a small number of Cycles, such as 2 or 4, before building longer structures.
- Make one clear change per Cycle at first. This makes it easier to hear what each Cycle contributes.
- Use Cycles to shape progression, not just variation.
- Keep some Tracks stable while others evolve. The contrast usually feels stronger than changing everything at once.
- If a Pattern feels repetitive but you still like its core idea, try Cycles before making a completely new Pattern.