Description
Audit a complete uninterleaved MIDI SysEx byte envelope F0 data F7; manufacturer identity, universal messages and realtime interleaving are not parsed.
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 a complete uninterleaved MIDI SysEx byte envelope F0 data F7; manufacturer identity, universal messages and realtime interleaving are not parsed.
When to use this tool
Use this tool to audit a complete uninterleaved MIDI SysEx byte envelope F0 data F7; manufacturer identity, universal messages and realtime interleaving are not parsed.
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.starts, result.ends, result.interiorData, result.valid. Use the ordering, boundary rules and absence conditions described below.
Validate bytes, then report whether the stream starts with 240, ends with 247 and has only seven-bit interior bytes; valid requires all three conditions and at least two bytes.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.starts | Whether the first byte is SysEx start 240. |
| result.ends | Whether the final byte is end-of-exclusive 247. |
| result.interiorData | Whether at least two bytes exist and every interior byte is seven-bit data. |
| result.valid | Whether the stated envelope or data-byte rule passes. |
{
"input": {
"bytes": [
240,
1,
2,
247
]
},
"output": {
"result": {
"starts": true,
"ends": true,
"interiorData": true,
"valid": true
}
}
}Limitations and assumptions
- This audits a simple SysEx envelope, not manufacturer payload, interleaved real-time messages or device compatibility.
- 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 System Exclusive Byte Envelope Audit — 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 Data Byte Range Check
Audit explicit raw byte values for MIDI seven-bit data-byte eligibility, retaining status-bit violations instead of interpreting them as messages.