• 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: Automation woes
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Automation woes


  • Subject: Re: Automation woes
  • From: Brian Willoughby <email@hidden>
  • Date: Wed, 23 Jan 2008 23:35:59 -0800

Interpolation is by no means the only useful thing to do with gesture bracketing. For one thing, perhaps minor, Pro Tools plugin API has a way to highlight controls that are being controlled, so the begin gesture would draw the highlight and the end gesture would remove it. More importantly, Logic and other DAW software have multiple automation recording modes, some of which erase old automation data whenever the user modifies a parameter. Without the begin gesture and end gesture, there would be no way for the automation system to know that it should erase and update the automation value for the duration that someone holds the mouse on a control, or otherwise holds a control at some new value. Also, the final release of the mouse may come a very long time after the last value change, but the automation system must cease erasing old data and revert to the old automation value as soon as the user "lets go" of the control - i.e. end gesture.

Interpolation is completely optional and rather unrelated to gestures.

Brian Willoughby
Sound Consulting


On Jan 23, 2008, at 22:07, Stephan M. Bernsee wrote: Am 24.01.2008 um 04:05 schrieb William Stewart:
On Jan 23, 2008, at 1:36 PM, Stephan M. Bernsee wrote:
Am 23.01.2008 um 22:24 schrieb Eric Gorouben:
No, I'm afraid not (not at the moment anyway). Except that you should NOT bracket every parameter change by a begin/end gesture event...!

But that wouldn't prevent the automation from working, it would just cause the parameter values to jump instead of being interpolated...

No - there's no implication from Begin/End gesture that there is any interpolation... Setting a parameter is always going to be an explicit "set the parameter to this value now" call. Its up to the AU to dezipper the parameter change if it should be (that is, you never want it to just jump internally because it would cause a glitch or some such)...

Well, but of what use are the begin/end gesture events then, if not to notify the host that any AUParameterSet calls between them are to be interpreted as sampled points along a continuous path?


--smb

_______________________________________________
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: Automation woes
      • From: "Stephan M. Bernsee" <email@hidden>
References: 
 >Re: Automation woes (From: Eric Gorouben <email@hidden>)
 >Re: Automation woes (From: "Stephan M. Bernsee" <email@hidden>)
 >Re: Automation woes (From: William Stewart <email@hidden>)
 >Re: Automation woes (From: "Stephan M. Bernsee" <email@hidden>)

  • Prev by Date: Re: Using AudioConverter to create compressed audio
  • Next by Date: Re: Automation woes
  • Previous by thread: Re: Automation woes
  • Next by thread: Re: Automation woes
  • Index(es):
    • Date
    • Thread