Re: MOTU Ultralight not showing up in output device query
Re: MOTU Ultralight not showing up in output device query
- Subject: Re: MOTU Ultralight not showing up in output device query
- From: Todd Blanchard <email@hidden>
- Date: Mon, 6 Aug 2007 13:06:11 -0700
On Aug 6, 2007, at 12:33 PM, William Stewart wrote:
As an FYI:
static ComponentDescription audioOutputDescription =
{ kAudioUnitType_Output };
The rest of the ComponentDescription fields must be zero for you to
get the results you list below. So, really you need to (or the
compiler is, or you are getting lucky) doing this:
ahem.
I am not "lucky". There are two rules in the C language which
guarantee that all other fields are zero. :-)
1) Static variables are always initialized with zeros in the absence
of specified initial values.
ie
static int x;
x will be set to zero because it lives in the data segment rather
than on the stack.
2) structs declared with initializers will initialize fields in the
struct by taking fields from the initialization expression until it
runs out of values - all remaining fields are set as zero. This is
true even for stack declare structs.
I used to teach this stuff at the University of Colorado, Denver. ;-)
Thanks for all your help so far though. I'm getting the hang of it
and my app is coming together nicely. The TestMatrixMixer example is
what I'm using for my info. Good to know about the debug option in
AULab.
Pity about the midi plugin format because its absence is preventing
people from building arpeggiators that are portable across
applications - ie I can use the same arpeggiator to record in one app
and use live in another.
-Todd Blanchard
_______________________________________________
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