| Namespace | Windows.Devices.Midi2.Utilities.Sequencing |
|---|---|
| Type Name | MidiSequenceTrackRouting |
| Type | WinRT Runtime Class |
| IDL | MidiSequenceTrackRouting.idl |
MidiSequenceTrackRouting decides where one track’s messages go. A file written for several instruments at once names the port it wanted for each track, so you can work out a good default. But the choice is up to your app.
Use it with GetTrackRouting and SetTrackRouting on MidiSequencePlayer.
| Constructor | Description |
|---|---|
MidiSequenceTrackRouting() |
Creates an empty routing. Then set the properties you want |
| Property | Description |
|---|---|
Connection |
The MidiEndpointConnection this track goes to. Null to use the connection the player was created with |
Group |
The MidiGroup to send on |
ChannelOverride |
Set this to move a track to a different MidiChannel than the file wrote it for. Null leaves the file’s channel alone |
IsMuted |
Whether this track is silenced |
Tracks can go to different endpoints at the same time and still stay in time with each other, because every message is scheduled against the same clock for the whole PC. That’s what makes it practical to play a rack of hardware from one file.
Start with MidiSequenceTrack.SuggestedDeviceName for a default. Match it against the endpoints on the PC to pick a connection ahead of time, and then let the person using your app change it.
Windows MIDI Services is an open source project with all source available on GitHub. We have a great community on Discord as well. Between GitHub and Discord, you should find the information you are looking for.
