Description
Split an unsigned MIDI fourteen-bit value into its least-significant and most-significant seven-bit data bytes.
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
Split an unsigned MIDI fourteen-bit value into its least-significant and most-significant seven-bit data bytes.
When to use this tool
Use this tool to split an unsigned MIDI fourteen-bit value into its least-significant and most-significant seven-bit data bytes.
How to use the tool and how it works
- Enter value using the field definitions below.
- Run the operation. Correct input errors before interpreting an output.
- Read result.lsb, result.msb. Use the ordering, boundary rules and absence conditions described below.
Validate an unsigned fourteen-bit value and split it into value modulo 128 and floor(value/128).2
| Input field | Meaning and units | Accepted input |
|---|---|---|
| value | Unsigned fourteen-bit integer, 0–16383. | A finite safe integer within the operation’s stated bounds. |
| Output field | Interpretation |
|---|---|
| result | Object containing the named fields below. |
| result.lsb | Least-significant seven-bit data component. |
| result.msb | Most-significant seven-bit data component. |
{
"input": {
"value": 8193
},
"output": {
"result": {
"lsb": 1,
"msb": 64
}
}
}Limitations and assumptions
- The returned lsb and msb are seven-bit values; their intended MIDI message is not inferred.
- 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 Fourteen Bit Seven Bit Pair Split — tool.io
Similar or alternative tools
- MIDI Seven Bit Pair Fourteen Bit Join
Join MIDI least-significant then most-significant seven-bit data bytes into an unsigned fourteen-bit integer.
- MIDI Fourteen Bit Controller Pair Audit
Audit explicit MSB/LSB controller-pair occurrences per channel; only a unique pair yields a fourteen-bit value, no temporal pairing guesses.