Rhythm Step Collision Table

Audit simultaneous rhythm step collisions while retaining original event indexes instead of deduplicating.

Description

Audit simultaneous rhythm step collisions while retaining original event indexes instead of deduplicating.

Repeated onset positions can be exposed as occurrence collisions without creating a full grid.

When to use this tool

Audit simultaneous rhythm step collisions while retaining original event indexes instead of deduplicating.

Prepare the supplied steps 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. 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.collisions. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.

Require steps as integers from 0 to 127, group equal positions and return only repeated groups with source indexes.^[1]

Input field	Meaning and representation	Accepted input
steps	steps.	List of finite numbers; at most 128 entries

Output field	Interpretation
result	Object containing the named outputs below.
result.collisions	The collisions list in the ordering and representation described above.

json

{
  "input": {
    "steps": [
      2,
      1,
      2
    ]
  },
  "output": {
    "result": {
      "collisions": [
        {
          "key": "2",
          "indexes": [
            0,
            2
          ]
        }
      ]
    }
  }
}

Limitations and assumptions

No grid length, time signature or audible collision is inferred. Input occurrences remain distinct evidence.
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

Tool behavior and example: Rhythm Step Collision Table — tool.io

Similar or alternative tools

Rhythm Step Coverage Counts
Count rhythm events at every bounded grid step including unused steps and collisions.
Rhythm Duration Fill Audit
Audit integer rhythm duration fill against an explicit tick budget, retaining negative overshoot rather than clamping.