Re: AudioUnit implementation restrictions
Re: AudioUnit implementation restrictions
- Subject: Re: AudioUnit implementation restrictions
- From: William Stewart <email@hidden>
- Date: Fri, 30 May 2008 13:57:00 -0700
The only substantial restriction for audio units is their activity in
their Render call -
(1) cannot block (you can do a "try" on a guard, but not a "lock")
(2) no file system access
(3) no memory allocation
(4) the model assumes that render will be done in "real time"
The exception to these rules are the offline AU type - where none of
the above restrictions need to be observed
Otherwise I don't believe there are any substantial restrictions.
Bill
On May 30, 2008, at 11:18 AM, Dominic Feira wrote:
Hello.
I'm currently working on an AUGenerator Audio Unit. Are there any
things that I can't do from within the context of the AU? Are there
certain things that aren't ok to do inside of the Initialize method
or in other methods?
Here are a two examples of things that I'm doing that I'm not sure
are ok.
1. Using a matrix mixer.
2. Using 2 different AudioConverters.
If there are restrictions, where can I find documentation of them?
Dominic Feira / Code Monkey / Ambrosia Software, Inc. -- http://www.AmbrosiaSW.com
_______________________________________________
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
_______________________________________________
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