MIDI Channel Message Record Formatter

Description

Format exactly one MIDI channel-message byte record with explicit status and validated seven-bit data arity.

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]

Format exactly one MIDI channel-message byte record with explicit status and validated seven-bit data arity.

When to use this tool

Use this tool to format exactly one MIDI channel-message byte record with explicit status and validated seven-bit data arity.

How to use the tool and how it works

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

Validate a channel status and its exact required count of seven-bit data bytes, then prepend the status.^[2]

Input field	Meaning and units	Accepted input
status	MIDI 1.0 channel status byte, 128–239.	A finite safe integer within the operation’s stated bounds.
data	Seven-bit data bytes in message order, with exact length determined by status.	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.bytes	Raw integer message bytes in serialization order.

json

{
  "input": {
    "status": 146,
    "data": [
      60,
      100
    ]
  },
  "output": {
    "result": {
      "bytes": [
        146,
        60,
        100
      ]
    }
  }
}

Limitations and assumptions

This emits raw message bytes without timing, running-status compression or a MIDI file envelope.
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 Formatter — 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.