Re: AU Callback on a separate thread ? How ?
Re: AU Callback on a separate thread ? How ?
Correct. The reason i have the callback in another thread is to not block the UI/Mainthread while audio is prepared/playing. This does not imply that you have part of the rendercallback spawn threads to gather the audioframes :)
The UI thread updates itself the usual ways and access data from the rendercallback by a shared static block of "counters", where the UI thread only reads status.
Frank
On Nov 17, 2010, at 2:39 PM, Robert Bielik wrote:
> Pascal skrev 2010-11-17 14:31:
>> Having the AU render callback on a separate should help to do UI updates without any interruption in the audio processing.
>
> These questions popup from time to time, so here goes: ALL rendering should be done within the context of the callback. Not in another thread. Generally not a good idea. There are no benefits. Zilch. Communication with UI should be done through lock-free communication queues.
>
> /Rob
> _______________________________________________
> 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