Re: Can anyone comment on Crashes in AUParameterSet?
Re: Can anyone comment on Crashes in AUParameterSet?
- Subject: Re: Can anyone comment on Crashes in AUParameterSet?
- From: Doug Wyatt <email@hidden>
- Date: Wed, 28 May 2003 12:45:53 -0700
On Wednesday, May 28, 2003, at 12:25 US/Pacific, Marc Poirier wrote:
On Tue, 27 May 2003, Doug Wyatt wrote:
I'm pretty positive that AUParameterSet is a convenience function
that
calls AudioUnitSetParameter and AUParameterListenerNotify,
essentially yes -- though if you disassemble you'll see that
AUParameterListenerNotify and AUParameterSet share this code in an
internal function, NotifyListeners.
and
AUParameterListenerNotify is asynchronous (the notifications go into
a
queue and are read when the listeners' read loops next fire and pull
notifications out of the queue).
not really, there is actually no queueing.
Hmmm, I don't understand... Then why do you provide a CFRunLoop and
notification interval when creating an AUParameterListener with
AUListenerCreate? And during a thread in February ("Property
notification questions"), Bill explained that AUParameterListenerNotify
and AUParameterSet were okay to call from the audio thread because they
were non-blocking and you would don't have to wait for the listeners to
react to the change. Is this not the case? Or am I just getting more
confused now?
I confused the issue with an implementation detail -- there is no
queue, just a bit and the latest value. The notifications are always
asynchronous -- except to receivers with a notification interval of 0,
and they're responsible for doing as little work as possible.
Doug
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.