Cleaning
More MIDI tests (#85)
Cleaning
Cleaning
Removes PortMidi

This turns out to be unavoidable. To get proper device detection we
have to call MIDIClientCreate which turns out to be called by PortMidi
at initialization time. I will reimplement the rest of the Fa.Midi
module in this branch and then think about abstracting it out to
the platform directory.
Removes PortMidi
(Recomitting for proper message)

This turns out to be unavoidable. To get proper device detection we
have to call MIDIClientCreate which turns out to be called by PortMidi
at initialization time. I will reimplement the rest of the Fa.Midi
module in this branch and then think about abstracting it out to
the platform directory.

See #40, #85
Sketching CoreMIDI-based MIDI impl

Se #85
CoreMIDI-based MIDI impl

Se #85
CoreMIDI-based MIDI impl

Se #85
CoreMIDI-based MIDI impl

Se #85
Temp
CoreMIDI-based MIDI impl

Se #85
Responds to MIDI status callbacks

Se #85
Restart MIDI sessions automatically

Se #85
MIDI Restarts

The current approach works for *one* start/stop turn, but not
more than that. As per the docs CoreMIDI will always use *one* thread,
(i.e. the first registered) for all further notifications. Yes this is terrible.

TODO Rewrite to use single thread for all interactions.

Se #85
Merge branch 'coremidi' of github.com:hanshoglund/faudio into coremidi

Conflicts:
	shared/midi.c
	tools/plug_midi.c