Feat: better user feedback on patterns page
All checks were successful
Deploy Website / deploy (push) Has been skipped

This commit is contained in:
2026-03-04 23:41:11 +01:00
parent 4e1c04f9c7
commit 35370a6f2c
11 changed files with 142 additions and 49 deletions

View File

@@ -31,7 +31,7 @@ Each pattern is an independent sequence of steps with its own properties:
| Sync Mode | Reset or Phase-Lock on re-trigger | `Reset` |
| Follow Up | What happens when the pattern finishes an iteration | `Loop` |
Press `e` in the patterns view to edit these settings. After editing properties, you will have to hit the `c` key to _commit_ these changes. More about that later!
Press `e` in the patterns view to edit these settings. After editing properties, you will have to hit the `c` key to _launch_ these changes. More about that later!
### Follow Up
@@ -46,12 +46,12 @@ The follow-up action determines what happens when a pattern reaches the end of i
Access the patterns view with `F2` (or `Ctrl+Up` from the sequencer). The view shows all banks and patterns in a grid. Indicators show pattern state:
- `>` Currently playing
- `+` Staged to play
- `-` Staged to stop
- `+` Armed to play
- `-` Armed to stop
- `M` Muted
- `S` Soloed
It is quite essential for you to understand the stage / commit system in order to use patterns. Please read the next section carefully!
It is quite essential for you to understand the arm / launch system in order to use patterns. Please read the next section carefully!
### Keybindings
@@ -59,13 +59,13 @@ It is quite essential for you to understand the stage / commit system in order t
|-----|--------|
| `Arrows` | Navigate banks and patterns |
| `Enter` | Select and return to sequencer |
| `p` | Stage pattern to play/stop |
| `c` | Commit staged changes |
| `m` / `x` | Stage mute / solo toggle |
| `p` | Arm pattern to play/stop |
| `c` | Launch armed changes |
| `m` / `x` | Arm mute / solo toggle |
| `e` | Edit pattern properties |
| `r` | Rename bank or pattern |
| `Ctrl+c` / `Ctrl+v` | Copy / Paste |
| `Delete` | Reset to empty pattern |
| `Esc` | Cancel staged changes |
| `Esc` | Cancel armed changes |

View File

@@ -1,35 +1,35 @@
# Stage / Commit
# Arm / Launch
In Cagire, changes to playback happen in two steps. First you **stage**: you mark what you want to happen. Then you **commit**: you apply all staged changes at once. Nothing changes until you commit. It is simpler than it sounds.
In Cagire, changes to playback happen in two steps. First you **arm**: you mark what you want to happen. Then you **launch**: you apply all armed changes at once. Nothing changes until you launch. It is simpler than it sounds.
Say you want patterns `04` and `05` to start playing together. You stage both (`p` on each), then commit (`c`). Both start at the same time. Want to stop them later? Stage them again, commit again. That's it.
Say you want patterns `04` and `05` to start playing together. You arm both (`p` on each), then launch (`c`). Both start at the same time. Want to stop them later? Arm them again, launch again. That's it.
This two-step process exists for good reasons:
- **Multiple changes at once**: queue several patterns to start/stop, commit them together.
- **Multiple changes at once**: queue several patterns to start/stop, launch them together.
- **Clean timing**: all changes land on beat or bar boundaries, never mid-step.
- **Safe preparation**: set up the next section while the current one keeps playing.
## Push changes, then apply
## Arm changes, then launch
Staging is an essential feature to understand to be effective when doing live performances:
Arming is an essential feature to understand to be effective when doing live performances:
1. Open the **Patterns** view (`F2` or `Ctrl+Up` from sequencer)
2. Navigate to a pattern you wish to change/play
3. Press `p` to stage it. The pending change is going to be displayed:
- `+` (staged to play)
- `-` (staged to stop)
- `m` (staged to mute)
- `s` (staged to solo)
3. Press `p` to arm it. The pending change is going to be displayed:
- `+` (armed to play)
- `-` (armed to stop)
- `m` (armed to mute)
- `s` (armed to solo)
- etc.
4. Repeat for other patterns you want to change
5. Press `c` to commit all changes
5. Press `c` to launch all changes
6. Or press `Esc` to cancel
You can also stage mute/solo changes:
You can also arm mute/solo changes:
- Press `m` to stage a mute toggle
- Press `x` to stage a solo toggle
- Press `m` to arm a mute toggle
- Press `x` to arm a solo toggle
- Press `Shift+m` to clear all mutes
- Press `Shift+x` to clear all solos
@@ -41,16 +41,18 @@ It might wait for the next beat/bar boundary.
| Indicator | Meaning |
|-----------|---------|
| `>` | Currently playing |
| `+` | Staged to play |
| `-` | Staged to stop |
| `+` | Armed to play |
| `-` | Armed to stop |
| `M` | Muted |
| `S` | Soloed |
A pattern can show combined indicators, e.g. `>` (playing) and `-` (staged to stop), or `>M` (playing and muted).
A pattern can show combined indicators, e.g. `>` (playing) and `-` (armed to stop), or `>M` (playing and muted).
Armed patterns blink to make pending changes impossible to miss.
## Quantization
Committed changes don't execute immediately. They wait for a quantization boundary:
Launched changes don't execute immediately. They wait for a quantization boundary:
| Setting | Behavior |
|---------|----------|