Re: Using an AU directly
Re: Using an AU directly
- Subject: Re: Using an AU directly
- From: Jean-Daniel Dupas <email@hidden>
- Date: Mon, 7 Sep 2009 14:55:21 +0200
Le 7 sept. 2009 à 14:50, Darrell Gibson a écrit :
Philippe,
Thanks for your suggestion. I've not looked at CAPThread before so
I'll take a look. However, am I write in assuming that the
PublicUtility have been dropped in the 10.6 SDK? This would put me
off going down this route.
Wrong assumption. It was just stripped down. CAPThread is available on
10.6.
You mention that this utility has a similar functionality to that of
the CoreAudio IOProc. Is there any info on the core audio system?
It would help me understand the underlying API that I seem to be
getting into.
I'm currently working on a "proof of concept". As a result I want
to perform real-time analysis of the data coming out of an AU
network, but I don't actually want an audio output.
Thanks for your help,
Darrell.
________________________________________
From: philippe wicker [email@hidden]
Sent: 07 September 2009 12:28
To: Darrell Gibson
Cc: Jean-Daniel Dupas; email@hidden
Subject: Re: Using an AU directly
What you could do is create a time constrained thread (you can use the
PublicUtility/CAPThread wrapper for this purpose), let your RT thread
looping on a pthread_cond_timedwait_relative_np (or use PublicUtility/
CAGuard::WaitUntil() method) and call AudioUnitRender on your AU
when your thread returns from the WaitUntil(). Doing so is somehow
equivalent to what CoreAudio is doing when it calls your IOProc.
Now you'll have to be careful about what kind of job you want to do in
this RT thread loop apart from calling your AU render. Maybe you could
tell us why you need "real time" calls of your AU render and what do
you plan to do with the AU rendered outputs?
Philippe
-- Jean-Daniel
_______________________________________________
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