• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: AUEventListenerNotify paramErr for PropertyChange events on Leopard
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: AUEventListenerNotify paramErr for PropertyChange events on Leopard


  • Subject: Re: AUEventListenerNotify paramErr for PropertyChange events on Leopard
  • From: William Stewart <email@hidden>
  • Date: Wed, 5 Dec 2007 19:19:01 -0800


On Dec 5, 2007, at 6:59 PM, Sophia Poirier [dfx] wrote:

On Dec 5, 2007, at 9:46 PM, William Stewart wrote:

You shouldn't need to make this call from within an AU - all you need to do there is call the AUBase::PropertyChanged method (which in turn will turn around and call of the registered property change listeners iwth the AU).

Oh hmmm, I thought it had to do with not blocking a render thread, that it was better to call AUEventListenerNotify() if you're sending the property change from within audio rendering. Am I incorrect about this and is PropertyChanged() in actually fine for that?

Its more on the listening end for properties. The property changed notify is executed on the thread you issue it on, but the real trouble can start when that callback is executed. So, for instance a view that is listening for property changes, should definitely be using the EventListener (otherwise those callbacks would execute on the render thread in this case).


When you instantiate a listener using the event listener (say your view), the event listener installs a property listener on the AU. When that property listener is called, it doesn't call the event listeners, but rather just registers that the property has changed, and sets the wheels in motion so that the actual event listeners will fire on their appropriate threads.

That said, we will look into this (as there's nothing here that looks obviously wrong to me

Thank you.

We normally don't expect the ListenerNotify to be called from property changes, so that could be why you are seeing a discrepancy here


Bill
_______________________________________________
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


  • Follow-Ups:
    • Re: AUEventListenerNotify paramErr for PropertyChange events on Leopard
      • From: Robert Abernathy <email@hidden>
References: 
 >AUEventListenerNotify paramErr for PropertyChange events on Leopard (From: "Sophia Poirier [dfx]" <email@hidden>)
 >Re: AUEventListenerNotify paramErr for PropertyChange events on Leopard (From: William Stewart <email@hidden>)
 >Re: AUEventListenerNotify paramErr for PropertyChange events on Leopard (From: "Sophia Poirier [dfx]" <email@hidden>)

  • Prev by Date: Re: AUEventListenerNotify paramErr for PropertyChange events on Leopard
  • Next by Date: Sending NoteOff Events to the Internal Synth
  • Previous by thread: Re: AUEventListenerNotify paramErr for PropertyChange events on Leopard
  • Next by thread: Re: AUEventListenerNotify paramErr for PropertyChange events on Leopard
  • Index(es):
    • Date
    • Thread