From 4e31cb7769954ddc7c9afe221733fcd7c633eace Mon Sep 17 00:00:00 2001 From: Pete Brown Date: Thu, 16 May 2024 14:14:42 -0400 Subject: [PATCH] Update mapping-midi1-port-concepts.md --- docs/mapping-midi1-port-concepts.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/mapping-midi1-port-concepts.md b/docs/mapping-midi1-port-concepts.md index 03ed686c7..cf9df302b 100644 --- a/docs/mapping-midi1-port-concepts.md +++ b/docs/mapping-midi1-port-concepts.md @@ -24,7 +24,7 @@ With Windows MIDI Services, we made the decision early on, validated by hardware The way the messages themselves map over is super clean. It's documented in the MIDI 2.0 UMP spec, but in a nut shell, it looks like this (in the case of a MIDI 1.0 Channel Voice message): -| UMP Message Type | **Group** | Status | Channel Index | Channel and Status | ... | +| UMP Message Type | **Group** | Status | Channel Index | ... | | 2 | **0-15** | 8 | 2 | rest of data | ### Cables to Groups