MIDI Data Byte Range Check

Description

Audit explicit raw byte values for MIDI seven-bit data-byte eligibility, retaining status-bit violations instead of interpreting them as messages.

MIDI 1.0 channel messages use a status byte identifying a message type and a channel, followed by one or two seven-bit data bytes. This family uses channel indexes 0–15 and raw program values 0–127. Raw message bytes do not include musical timing, instrument state or a MIDI file container.^[1]

Audit explicit raw byte values for MIDI seven-bit data-byte eligibility, retaining status-bit violations instead of interpreting them as messages.

When to use this tool

Use this tool to audit explicit raw byte values for MIDI seven-bit data-byte eligibility, retaining status-bit violations instead of interpreting them as messages.

How to use the tool and how it works

Enter bytes using the field definitions below.
Run the operation. Correct input errors before interpreting an output.
Read result.valid, result.violations. Use the ordering, boundary rules and absence conditions described below.

Validate byte range 0–255, then flag whether every byte is below 128 and report indexes and values of high-bit violations.^[2]

Input field	Meaning and units	Accepted input
bytes	Explicit integer byte values, each 0–255; data positions may require 0–127.	Dense list of at most 128 finite numbers; integer/shape constraints above also apply.

Output field	Interpretation
result	Object containing the named fields below.
result.valid	Whether the stated envelope or data-byte rule passes.
result.violations	Original positions and values violating the seven-bit data rule.

json

{
  "input": {
    "bytes": [
      0,
      127,
      128
    ]
  },
  "output": {
    "result": {
      "valid": false,
      "violations": [
        {
          "index": 2,
          "value": 128
        }
      ]
    }
  }
}

Limitations and assumptions

A byte outside 0–255 is an input error; a status-byte value inside that range produces a valid false result.
Message data bytes must be integers 0–127 and channel statuses 128–239. Channels are zero-based; this family does not implement MIDI 2.0 UMP, audio synthesis or a complete timed MIDI file.
Every declared top-level input field is required and unexpected fields are rejected. Ordinary strings are limited to 8,192 UTF-16 code units and lists to 128 entries, with tighter operation-specific bounds where stated. JSON text has bounded nesting and node counts.
Numeric outputs must be finite and no larger in absolute magnitude than the safe-integer limit; operations returning exact large integers use decimal text. Positions are zero-based and spans end exclusively unless the operation explicitly states a different convention.

Alternative or Complementary methods

Separate channel-message encoding from timing, running status and device interpretation. Use a MIDI sequencer or full file/stream parser when those additional layers matter.

References

Summary of MIDI 1.0 Messages — The MIDI Association
Tool behavior and example: MIDI Data Byte Range Check — tool.io

Similar or alternative tools

MIDI Channel Message Byte Count
Return required MIDI 1.0 channel-message byte counts from an explicit status, excluding running-status omission and system messages.
MIDI Channel Pressure Range Map
Map an explicit seven-bit MIDI channel pressure to a caller-supplied ascending finite numeric range; linear caller model, not synth-specific response.