Description
Parse exactly one complete explicit-status MIDI channel message; running status, realtime interleaving and system messages are rejected.
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
Parse exactly one complete explicit-status MIDI channel message; running status, realtime interleaving and system messages are rejected.
When to use this tool
Use this tool to parse exactly one complete explicit-status MIDI channel message; running status, realtime interleaving and system messages are rejected.
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.status, result.type, result.channel, result.data. Use the ordering, boundary rules and absence conditions described below.
Require one explicit channel status plus exactly its required seven-bit data bytes. Return status, type nibble, zero-based channel and data.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.status | Channel status byte 128–239. |
| result.type | Channel status high nibble, an integer 8–14. |
| result.channel | Zero-based channel index 0–15. |
| result.data | Data bytes following the explicit status. |
{
"input": {
"bytes": [
146,
60,
100
]
},
"output": {
"result": {
"status": 146,
"type": 9,
"channel": 2,
"data": [
60,
100
]
}
}
}Limitations and assumptions
- Multiple concatenated messages, running status and system events are not accepted as one record.
- 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 Channel Message Record Parser — 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 Message Channel Remapper
Remap all MIDI channel-message channels through an explicit sixteen-entry old-to-new channel table; preserve message type and data.