Some information relates to prerelease product that may be substantially modified before it’s released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
The CoreMidi namespace provides classes for interacting with the MIDI subsystem.
Provides data for the IOError event.
Global methods and constants for using CoreMidi.
Notification posted by the Midi class.
Main entry point to use MIDI in MacOS X and iOS.
Represents a MIDI device (typically they represent a hardware device, but virtual devices also exist). Devices can contain one or more entities.
Endpoints represent an individual source or destination on the MIDI stream.
Exception raised by Midi methods.
A connection to a MIDI network host, using a MidiNetworkSession.
A remote MIDI host.
A singleton class that maintains the MidiNetworkConnections between various MIDI entities.
Encapsulates a series of MIDI events.
Input and Output ports.
Manages MIDI play-through connections.
MIDI transformations and routings.
Provides data for the ObjectRemoved and E:CoreMidi.ObjectAddedOrRemovedEventArgs.ObjectRemoved events.
Provides data for the PropertyChanged event.
Represents a transformation of a MIDI control.
Source or Destination of a MidiThruConnection.
Object that defines how a MIDI event is transformed.
MIDI Value map.
Errors raised by the CoreMIDI stack.
An enumeration whose values specify which hosts are eligible to connect to a MIDI network session.
MIDI Control Transformation Type.
MIDI transform types.
CoreMIDI is an API that talks to the MIDI server on iOS and OSX which in turn interacts with MIDI devices connected to your Mac or iOS device.
When using CoreMIDI, you will run into various classes that deal with different parts of the MIDI stack, the following graphic illustrates the relationships:
The MIDI device itself is represented by the MidiDevice class. Devices can contain one or more entities (MidiEntity). For example a MIDI device could contain two independent MIDI tone generators. Each Entity contains a series of endpoints which are either sources or destintions. Both MIDI sources and MIDI destinations are encapsulated by the MidiEntity class.
To start with MIDI, you will need to create a MidiClient object. This object is the gateway between your application and the MIDI server process. You subscribe to the events that this object raises to track devices being added, removed and to changes in their properties and setup configuration.
You also use the MidiClient to create input ports and output ports. The input ports raise the MessageReceived event when new MIDI data is available and you can use the Packets property in the arguments received to get the data out
See the MidiClient class for an example of how to set things up.
To use networked MIDI connections, you need to enable the network session and set its connection policy, like this:
var session = MidiNetworkSession.DefaultSession; session.Enabled = true; session.ConnectionPolicy = MidiNetworkConnectionPolicy.Anyone;
To connect to a remote MIDI network host you use the MidiNetworkHost, like this:
var host = MidiNetworkHost.Create ("My Session", "myhost.xamarin.com", 5004); var connection = MidiNetworkConnection.FromHost (host);