Merge pull request #338 from microsoft/pete-dev

Update mapping-midi1-port-concepts.md
microsoft · May 16, 2024 · a34a551 · a34a551
2 parents baf4985 + f7c217b
commit a34a551
Showing 1 changed file with 4 additions and 2 deletions.
diff --git a/docs/mapping-midi1-port-concepts.md b/docs/mapping-midi1-port-concepts.md
@@ -22,8 +22,10 @@ With Windows MIDI Services, we made the decision early on, validated by hardware
 
 > That means that Windows MIDI Services has no "ports". (We do map back to ports for our older MIDI 1.0 APIs, but that is for backwards compatibility with those APIs)
 
-| UMP Message Type | Group Index | Channel and Status | ... |
-| 2 | 0-15 | | rest of message data |
+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 | ... |
+| 2 | **0-15** | 8 | 2 | rest of data |
 
 ### Cables to Groups