Description
Audit explicit MSB/LSB controller-pair occurrences per channel; only a unique pair yields a fourteen-bit value, no temporal pairing guesses.
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 MSB/LSB controller-pair occurrences per channel; only a unique pair yields a fourteen-bit value, no temporal pairing guesses.
When to use this tool
Use this tool to audit explicit MSB/LSB controller-pair occurrences per channel; only a unique pair yields a fourteen-bit value, no temporal pairing guesses.
How to use the tool and how it works
- Enter messagesJson, msbController using the field definitions below. For JSON text, serialize the explicit records in the shown shape.
- Run the operation. Correct input errors before interpreting an output.
- Read result.channels. Use the ordering, boundary rules and absence conditions described below.
For each channel, locate the selected controller 0–31 and its paired controller plus 32. Return occurrence indexes and combine values only when exactly one of each exists.2
| Input field | Meaning and units | Accepted input |
|---|---|---|
| messagesJson | JSON text encoding array of {status: number, data: array of number}. Keep the record keys and value types shown in the decoded example below. | Text, at most 8,192 UTF-16 code units; the operation’s grammar also applies. |
| msbController | High-resolution controller MSB number, 0–31; paired LSB number is this plus 32. | A finite safe integer within the operation’s stated bounds. |
These are the decoded structures used in the example’s JSON text fields. Supply the corresponding serialized JSON strings as input.
{
"messagesJson": [
{
"status": 176,
"data": [
1,
64
]
},
{
"status": 176,
"data": [
33,
2
]
}
]
}| Output field | Interpretation |
|---|---|
| result | Object containing the named fields below. |
| result.channels | Channels with selected controller occurrences; value is null unless exactly one MSB and one LSB occur. |
{
"input": {
"messagesJson": "[{\"status\":176,\"data\":[1,64]},{\"status\":176,\"data\":[33,2]}]",
"msbController": 1
},
"output": {
"result": {
"channels": [
{
"channel": 0,
"msb": [
0
],
"lsb": [
1
],
"unambiguous": true,
"value": 8194
}
]
}
}
}Limitations and assumptions
- Repeated or incomplete pairs yield null value; the tool does not infer chronology or carry state across batches.
- 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 Controller Pair Audit — tool.io
Similar or alternative tools
- MIDI Fourteen Bit Seven Bit Pair Split
Split an unsigned MIDI fourteen-bit value into its least-significant and most-significant seven-bit data bytes.
- MIDI Seven Bit Pair Fourteen Bit Join
Join MIDI least-significant then most-significant seven-bit data bytes into an unsigned fourteen-bit integer.