Lists

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

Confused about OpenAComponent vs AUGraphNewNode

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

Confused about OpenAComponent vs AUGraphNewNode

Subject: Confused about OpenAComponent vs AUGraphNewNode
From: Todd Blanchard <email@hidden>
Date: Sun, 12 Aug 2007 13:46:08 -0700

I'm building a system for allowing playing of MIDI virtual instruments live. So far I've been creating my music devices using OpenAComponent, then calling AudioUnitInitialize, then AUMIDIControllerCreate to create the MIDI interface for it.

Now I'm looking at setting up a mixer and it looks like AUGraphNewNode opens (instances) the component - how much more does it do for me? Does it initialize it? Will it create a midi interface for it if it is a music device? I can't seem to figure out how smart AUGraphNewNode is and it seems like a completely different approach than the

OpenAComponent
AudioUnitInitialize
AUMIDIControllerCreate

or...

do I just let AUMIDIControllerCreate do the equivalent of OpenAComponent, then call AUGraphGetNodeInfo to get the AudioUnit and then call AudioUnitInitialize and AUMIDIControllerCreate myself?

It just isn't clear from the docs at all how this is supposed to fit together.

-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


Follow-Ups:

Re: Confused about OpenAComponent vs AUGraphNewNode
From: William Stewart <email@hidden>


Prev by Date:
Flush CoreAudio Component

Next by Date:
Re: How do you get the native bit-depth of the input device?

Previous by thread:
Re: Flush CoreAudio Component

Next by thread:
Re: Confused about OpenAComponent vs AUGraphNewNode

Index(es):

Date
Thread