Re: AU automation gestures/scroll wheel events
Re: AU automation gestures/scroll wheel events
- Subject: Re: AU automation gestures/scroll wheel events
- From: William Stewart <email@hidden>
- Date: Fri, 5 Jun 2009 17:48:55 -0700
On Jun 4, 2009, at 2:18 PM, Stephen Blinkhorn wrote:
Hi all,
Two quick questions.
i) I am using notifications in my AU to keep track of mouse down and
mouse up events so I can post begin and end gestures for automation
purposes. But when I do something like this..
AudioUnitParameter parameter = {mAU, kDS_FilterCutoff,
kAudioUnitScope_Global, 0};
auEvent.mArgument.mParameter = parameter;
auEvent.mEventType = kAudioUnitEvent_BeginParameterChangeGesture;
..must I always specify the parameter that will be changing or is
this ignored?
Hmm, seems like a stupid question on paper.
yes :) - you have to notify which parameter(s) is changing (you can
send a notification for one gesture to change more than one parameter)
ii) Using the mouse scroll wheel for GUI elements poses the problem
of when to send begin and end gestures. I'm thinking the best way
would be to simply measure elapsed time between events and send an
end gesture if elapsed time is greater than a timeout value. Anyone
got any better ideas?
Thanks,
Stephen
ps, wouldn't it be nice if AULab had a simple little timeline MIDI
sequencer with provision for some automation data recording/playback
etc.
_______________________________________________
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