Re: AU Callback on a separate thread ? How ?
Re: AU Callback on a separate thread ? How ?
- Subject: Re: AU Callback on a separate thread ? How ?
- From: Pascal <email@hidden>
- Date: Wed, 17 Nov 2010 16:28:58 -0300
Thanks Paul for clarifying my question. Which was about your second point. The rendering of my Audio Units are always done within their Callback and I asked about running the AUGraph in a separate thread from the Main Loop where all the UI calls are made. Sorry if I wasn't clear enough at first.
I have a small 4 tracks-sequencer that I can also use as a drum pad. For development purposes I have just used some UIButtons for my drum pads. If I trigger the drum pads too quickly, I get silence and the buttons are refreshed with delay. It is as if the UI update slows down the AU rendering. Thus my question about separating the two processes (UI and the running of the AUGraph) in two different threads. If it makes sense, what threading methods is best (NSThreads, NSOperation, GCD)?
And also what is the best place to run the sequencer to get the most precise timing ? In the AU callback of a particular track (track 0 for instance) where the reference of my sequencer is passed in a CallbackStruct ?
Thanks.
Pascla
_______________________________________________
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