Rhythm Step Coverage Counts
Count rhythm events at every bounded grid step including unused steps and collisions.
Description
Count rhythm events at every bounded grid step including unused steps and collisions.
Step coverage counts distinguish repeated onsets from merely occupied grid positions.
When to use this tool
Count rhythm events at every bounded grid step including unused steps and collisions.
- Prepare the supplied steps, gridSize fields for this operation.
- Compare the complete example with the representation used by your own input before carrying the result into another step.
How to use the tool and how it works
- Enter steps, gridSize. Use the exact text syntax, units and index conventions explained below.
- Run the tool. If input validation fails, correct the supplied fields before interpreting any result.
- Read result.counts. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.
Require gridSize from 0 to 128 and each step inside it. For every zero-based grid position return the number of supplied step occurrences.1
| Input field | Meaning and representation | Accepted input |
|---|---|---|
| steps | steps. | List of finite numbers; at most 128 entries |
| gridSize | grid size. | Integer from 0 to 128 inclusive |
| Output field | Interpretation |
|---|---|
| result | Object containing the named outputs below. |
| result.counts | The counts list in the ordering and representation described above. |
{
"input": {
"steps": [
0,
2,
2
],
"gridSize": 4
},
"output": {
"result": {
"counts": [
1,
0,
2,
0
]
}
}
}Limitations and assumptions
- No timing interpolation, velocity or rhythm quality is evaluated. Repeated positions increment counts rather than being deduplicated.
- Every declared top-level field is required and unexpected fields are rejected. Numeric inputs must be finite; ordinary text fields are bounded to 8,192 UTF-16 code units, with tighter operation-specific limits where stated.
- Lists are limited to 128 entries. JSON text must meet bounded size and depth checks, and numeric outputs beyond the safe finite magnitude are rejected. Exact large integers use decimal strings.
- Indexes are zero-based and spans have an exclusive end unless explicitly stated otherwise. A valid false, null or empty-list result is distinct from malformed input.
Alternative or Complementary methods
Retain the tick unit, channel numbering and event-pairing policy with the result. Use a MIDI-file parser or audio analysis when the task requires actual messages, playback behavior or recorded sound.
References
Similar or alternative tools
- Rhythm Step Collision Table
Audit simultaneous rhythm step collisions while retaining original event indexes instead of deduplicating.
- Rhythm Duration Fill Audit
Audit integer rhythm duration fill against an explicit tick budget, retaining negative overshoot rather than clamping.