Skip to content

Clarify why silent notes can happen #174

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
DSmolken merged 1 commit into from
Jun 8, 2026
Merged

Clarify why silent notes can happen #174

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion docs/opcodes/seq_position.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,10 @@ The player will keep an internal counter creating a consecutive
note-on sequence for each region, starting at 1 and resetting at seq_length.
Maximum allowed value is 100.

Note that, as with other opcodes that restrict when a region plays,
`seq_position` is _combined_ with other playback restrictions.
If you have irregular region mappings, you may find you have "silent" steps.

## Example

```sfz
Expand Down Expand Up @@ -91,4 +95,4 @@ except for sfizz where it will behave the same as setting `seq_position` to 1.


[seq_length]: seq_length.md
[lorand / hirand]: lorand.md
[lorand / hirand]: lorand.md