Lists

Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists

MIDIClient: one instance or many?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

MIDIClient: one instance or many?

Subject: MIDIClient: one instance or many?
From: "Ross Bencina" <email@hidden>
Date: Mon, 12 Jan 2009 18:01:37 +1100

Hi

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?

At the moment we're calling MIDIClientCreate() to create a separate client (with the same name) for each endpoint we open, but that doesn't quite seem right.

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.

Thanks!

Ross.


_______________________________________________
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


Follow-Ups:

Re: MIDIClient: one instance or many?
From: Kurt Revis <email@hidden>


Prev by Date:
Re: Assert Failure for AUListenerAddParameter

Next by Date:
Re: MIDIClient: one instance or many?

Previous by thread:
Re: Question regarding recording and accounting for drift

Next by thread:
Re: MIDIClient: one instance or many?

Index(es):

Date
Thread