• 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: property listeners and RT
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: property listeners and RT


  • Subject: Re: property listeners and RT
  • From: William Stewart <email@hidden>
  • Date: Mon, 9 Nov 2009 13:05:20 -0800


On Nov 8, 2009, at 12:30 PM, Paul Davis wrote:

On Sun, Nov 8, 2009 at 3:18 PM, Ian Kemmish <email@hidden> wrote:
I think you'll find that the mantra is "parameters for performance;
properties for setting up".

That is, parameters may be automated, and the changes should be used by the
AU in real time; the UI's parameter listeners will get called sometime in
the not-too-distant future.

OK, so the host needs to arrange for this happen. I guess its arguably better than every plugin having to share some mechanism for "notify listeners when the time is right". I'm still finding it odd to adapt to an MVC model where the controller is responsible for notifying Views about Model state changes, but I predict I'll be over that by the middle of next week :)

On the other hand, properties are intended for editing from the UI by the
user, and not for automation. So properties tend to get changed in the
app's "main" thread, but definitely not on the real time thread, and Apple's
sample code for PropertyChanged() calls the UI's property listeners right
there and then.

No - they don't.


Got all that. The issue for me was the sample code that I've seen recently for parameter changes notifies listeners right there and there and then too :)

No - what sample code is this?

You both need to look at the way an AUEventListener is constructed and the implications this has for what thread the notification is delivered on. Alot of misinformation otherwise.

Bill


Presumably the assumption was that was code for
some kind of interesting non-plugin-GUI-view parameter changing, but
not automation. Thanks for helping to clarify this.

--p
_______________________________________________
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
References: 
 >Re: property listeners and RT (From: Ian Kemmish <email@hidden>)
 >Re: property listeners and RT (From: Paul Davis <email@hidden>)

  • Prev by Date: Re: au property listeners and RT
  • Next by Date: Re: AudioUnit metering seems to be broken in generic views
  • Previous by thread: Re: property listeners and RT
  • Next by thread: Passing parsed packets from Audio File Stream Services to Audio Queue
  • Index(es):
    • Date
    • Thread