Re: MIDIClientDispose and MIDIServer
Re: MIDIClientDispose and MIDIServer
- Subject: Re: MIDIClientDispose and MIDIServer
- From: Doug Wyatt <email@hidden>
- Date: Mon, 6 Dec 2004 11:39:14 -0800
On Dec 6, 2004, at 10:55, Pete Gontier wrote:
So I take it you just need to make CoreMIDI calls for a little while
from your
startup item, then stop and go into a state where you're not going to
need it
any more? Or do you need CoreMIDI at irregular intervals?
I have ten zillion entry points. I am a helper app for a USB device
with a
control panel. The device is configured via MIDI messages. It needs to
be
configured each time it is plugged in. It needs to be configured each
time a
user logs in. It needs to be configured when the user diddles the
control
panel. I'm probably forgetting one or two of the cases as I write this
email.
I'm afraid that to be any more helpful I'd have to understand why
it's not
practical to divide your app up into multiple processes.
It's technically possible. It's just not friendly to my schedule.
One idea is to look into using the mach_init mechanism; your main
startup item
could be a shell that sends a mach message to launch the process that
actually
does work. That's actually fairly simple and reliable, assuming the
code is
amenable to being divided that way. Or is the code which decides when
to do
work substantial and intricately linked to the code that does work?
:-/
Right now it is. Separating them would be work for which I don't have
time.
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.
Doug
_______________________________________________
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