Re: Automation woes
Re: Automation woes
- Subject: Re: Automation woes
- From: "Stephan M. Bernsee" <email@hidden>
- Date: Thu, 24 Jan 2008 08:56:25 +0100
Hi Brian,
I agree with you 100%, although I don't see gestures and interpolation
as being unrelated (for the reason that I have already stated, which
btw. is also mentioned in an earlier discussion about gestures on this
list - gestures do help interpreting the meaning of parameter value
changes as being part of a continuous path. And if you look at the
behaviour you get from Logic this appears to be exactly what they do).
In any event, the thing that I thought Eric seems to be struggling
with is that Logic 8 doesn't record parameter changes made through
AUParameterSet calls without an active gesture session. In an earlier
post on this list ("Cocoa AU template, AUParameterSet and Logic
automation") I was wondering if this is a bug in Logic because I too
was under the impression that gestures were be optional, not
mandatory. In practice, however, it turns out that in Logic 8 gestures
are indeed required in order to record parameter automation events.
Since Eric is aware of this his problem must lie somewhere else.
I still stand by my opinion that it should not be necessary to bracket
each and every call to AUParameterSet with a gesture start/end event -
they wouldn't be very useful then.
Regards,
--smb
Am 24.01.2008 um 08:35 schrieb Brian Willoughby:
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