Hi,
Let's say I am reading audio input from a device and I would like to
do some signal processing and display the results. If the signal
processing is very computationally intensive, I expect that it should
not be done in the AudioQueue callback (I read that if real-time
threads are too compute-bound, they can be demoted in priority). So I
should dump the audio data in a buffer that gets processed by another
thread. My question is: do I have to fiddle with the "run loop"
methods of this second thread? I mean, in a very simple
producer-consumer scenario such as this, is there any reason that the
run loop thread control interface is superior to simple POSIX
condition variables?
- Aaron
_______________________________________________
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
