Re: MIDIClient: one instance or many?
Re: MIDIClient: one instance or many?
- Subject: Re: MIDIClient: one instance or many?
- From: Kurt Revis <email@hidden>
- Date: Sun, 11 Jan 2009 23:17:44 -0800
On Jan 11, 2009, at 11:01 PM, Ross Bencina wrote:
Can somone advise whether an App which opens multiple MIDI input and
output endpoints should usually just create a single "MIDIClient"
instance with MIDIClientCreate(), or should it create multiple
clients?
. . .
To ask another way: what is the intended role of the MIDIClient
object within the system? The MIDIServices.h API overview is silent
on this.
You typically need only one MIDIClient per application. Think of it as
your general connection to the MIDI system provided by the OS.
There's nothing to be gained by using more than one, aside from adding
unnecessary complexity.
The only reason I can imagine for needing multiple MIDIClients would
be if you had multiple subsystems that needed to create endpoints or
get MIDI setup change notifications, and they couldn't all get to one
central MIDIClient for some reason. I could imagine this happening in
some kind of plugin, for instance. An application by itself shouldn't
have that problem.
--
Kurt Revis
email@hidden
_______________________________________________
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