Re: [Pythonmidi-devel] And there was much rejoicing!

[Jay V. <jv...@ac...>]

>But if there are more Mac developers,

i'm a mac/unix/embedded developer.  i like darwin a lot.

>and people could point me in
>the right direction as to which bits of QuickTime or Audio Units
>would need to be exposed to Python to enable MIDI support I can make
>those bits available pretty easily:

i don't think you have to -only- do the built-in Apple/MIDI API.  if 
you do python for midishare, then you get cross-platform MIDI 
support: MidiShare runs on everything.

if use use MidiShare for the MIDI abtraction layer, in other words, 
there need not be individual 'fixes' for each platforms' MIDI side.

MidiShare is a clean, well-proven, well-designed, abstract C API.  I 
rank it higher than CoreMIDI for plain ol' MIDI hacking fun. 
CoreMIDI implies CoreEverythingElse, yuck.  I like Darwin, and since 
its Darwin, I don't -need- to use the AppleAPI's for everything..

>the Python interfaces to the
>MacOS API's can be generated from the Apple headers with not too
>much effort.

Do MidiShare first, and you get linux/win32/osx MIDI from the get-go.

>Unfortunately the tool to do so is so quirky that I
>seem to be the only person who's able to drive it:-)

what a sucky tool.

-- 

;

Jay Vaughan