From a605bdce9ef496f80ef5914fd140e38b35b5deff Mon Sep 17 00:00:00 2001 From: Pete Brown Date: Thu, 16 May 2024 13:58:29 -0400 Subject: [PATCH] Update mapping-midi1-port-concepts.md --- docs/mapping-midi1-port-concepts.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/mapping-midi1-port-concepts.md b/docs/mapping-midi1-port-concepts.md index 668d1a921..4f026e72a 100644 --- a/docs/mapping-midi1-port-concepts.md +++ b/docs/mapping-midi1-port-concepts.md @@ -1,7 +1,6 @@ --- layout: page title: Mapping MIDI 1.0 Ports -parent: Windows MIDI Services has_children: false --- @@ -23,6 +22,9 @@ 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 | + ### Cables to Groups When we enumerate a MIDI 1.0 USB device in the service, we create an aggregate endpoint for that device. As part of that, we build a map of UMP group indexes to MIDI 1.0 KS Pins. We use this for routing so when you address a specific Group.