• 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: presets, parameter value properties, tracking
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: presets, parameter value properties, tracking


  • Subject: Re: presets, parameter value properties, tracking
  • From: Paul Davis <email@hidden>
  • Date: Sat, 01 Dec 2018 17:42:51 -0500

On Sat, Dec 1, 2018 at 5:24 PM Paul Davis <email@hidden>
wrote:

> here at ardour HQ we're trying to figure how we're supposed to do
> something that we want to do: indicate to the user when the parameters of a
> plugin, previously set by a preset, have been subsequently modified by the
> user.
>
> the problem comes from the fact that when PresentPreset is set on a
> plugin, it notifies property listeners about the change in the
> PresentProperty value. Great!
>
> but then according to apple docs and other code, we are supposed to call
> AUParameterListenerNotify() with AnyParameter as the parameter ID, so that
> all listeners get notified about the (potentially) new values of all the
> parameters. Ardour is itself a listener.
>
> The notifications occur in this order, so there is no way sensible to know
> when the notifications that we've triggered by using AnyParameter have
> finished.
>
> This means that managing a flag that indicates "all parameters have a
> value that comes from a preset" seems hard, because we don't know whether a
> ParameterValueChanged notification comes from:
>
>    (1) a preset change itself (specifically, us notifying all listeners
> about it)
>    (2) the plugin GUI being used to change a parameter on its own
>    (3) some other GUI (eg. host provided) being used to change a parameter
> on its own
>
> Can anyone recommend a "best practice" here, if there is one?
>

ps. one idea we've had is to queue some other notification that will be
delivered *after* all the parameter value change notifications are done,
but we have no idea what that might be.
 _______________________________________________
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: presets, parameter value properties, tracking
      • From: Howard Moon <email@hidden>
References: 
 >presets, parameter value properties, tracking (From: Paul Davis <email@hidden>)

  • Prev by Date: presets, parameter value properties, tracking
  • Next by Date: Re: presets, parameter value properties, tracking
  • Previous by thread: presets, parameter value properties, tracking
  • Next by thread: Re: presets, parameter value properties, tracking
  • Index(es):
    • Date
    • Thread