AU automation questions
AU automation questions
- Subject: AU automation questions
- From: "Frederik Slijkerman" <email@hidden>
- Date: Wed, 12 Apr 2006 09:43:21 +0200
Hi all,
I've got two automation-related questions regarding AU plugins. We're
currently rewriting our automation code to use Begin/EndGesture
notifications because Logic on Intel doesn't support the older
notifications.
- What is the recommended way to deal with older hosts that still expect the
kAudioUnitCarbonViewEvent_MouseDownInControl /
kAudioUnitCarbonViewEvent_MouseUpInControl notifications? Should we send
Begin/EndGesture to all hosts, and MouseDown/UpInControl to hosts that
provide an event listener (possibly duplicating the Begin/EndGesture
notification), or should we only send Begin/EndGesture to hosts that do not
provide an old-style event listener?
- How should we deal with preset changes? In our plugins, this simply
changes all parameters of the plugin. In our currently available AUs, we
send out MouseDownInControl notifications for all parameters, then change
the parameters and call AUParameterSet as well, and finally send out
MouseUpInControl notifications for all parameters. Is this correct if we
only change the notifications to use Begin/EndGesture, or is there a better
way?
By the way, the generic carbon view code in the CoreAudio SDK still only
sends out MouseDown/UpInControl notifications, so we couldn't use that for
inspiration. :-)
Thanks a lot!
Frederik Slijkerman
FabFilter Software Instruments
_______________________________________________
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