Re: MIDIClientDispose and MIDIServer
Re: MIDIClientDispose and MIDIServer
- Subject: Re: MIDIClientDispose and MIDIServer
- From: Pete Gontier <email@hidden>
- Date: Mon, 06 Dec 2004 12:21:48 -0800
circa 12/6/04 11:39 AM, "Doug Wyatt" <email@hidden> wrote:
> I wonder how big a mess it would be to load your MIDI driver yourself and
> pretend you're MIDIServer. You'd have to send some private messages to the
> driver to give it some callback function pointers to use instead of calling
> CoreMIDI APIs. You'd need to check whether MIDIServer were running first. Just
> a thought experiment.
Yes, I have run that one myself a couple of times in the last few days. :-)
The driver in question, however, is the Apple class driver. Baking that code
into my helper app would defeat a lot of the purpose of having Apple
maintain and release class driver binaries with the operating system. Plus
it would bloat my helper app because the sample handles a more general case
than I need.
Another thought experiment I've been running involves my app-level MIDI
abstraction layer, which makes it possible for me to write control panels
for CoreMIDI, OMS, and FreeMIDI all at the same time (though I never got
around to sub-classing for FreeMIDI). In theory, I could sub-class this
layer and implement just enough of the class specification to get by for
just this one device. That would still be effort on the order of writing a
plug-in from scratch, though, and I'd still be giving up many of the
benefits of having Apple maintain and release class driver binaries with the
operating system.
--
Pete Gontier
http://www.m-audio.com/
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden