[gmpi] Re: wrap up 3.8 - gesture start/end

--- David Olofson wrote:
> > Okay, only on start/end definitely sounds better to me than with
> > each param value change event.  However, I still don't see why it's
> > necessary. Taking the example of a mouse click or XY pad
> > finger-landing, for examples, you can simply send a
> > param-gesture-begin event when the finger lands or mouse clicks
> > down and then a param-gesture-end event when the finger or mouse
> > button is released.  Every parameter change notification that the
> > listener receives during that period of time is a part of the
> > gesture.
> 
> Nope. An automation sequencer could have *hundreds* of control inputs. 
> How on earth do you know which ones belong together...? Just assume 
> that all inputs that go to record enabled tracks belong to the same 
> "gesture"?

Is an automation sequencer actually going to be generating parameter
change gestures?  I don't think so.  It will be sending parameter changes
to the plugin, that's all.  It's not recording automation, it's outputting
automation.


> > Hmmm, I did just think of something, though.  For undo or touch
> > automation, you want to capture the state of the parameter(s) in
> > the gesture before any changes occur, so in other words, when you
> > get the gesture-start event.
> 
> Well, yeah - but since you're a control input, you already know your 
> state. (If not, capture/release would have to be equivalent to 
> connect/disconnect.)

Who's a control input?  I was talking about the host, generally.


> > Though I still don't
> > think that the gesture ID is necessary, since the host can assume
> > that if the other parameters' gesture hasn't ended, then the new
> > one is a part of the same gesture.
> 
> That is assuming there can only be one gesture going on at a time in 
> the whole system or something. But (most) sound engineers have two 
> times five fingers and two feet, right...? :-) Everyone isn't using a 
> mouse to control the whole setup.

I guess this will matter for touch automation features, I see.


> > However, I do see one more problem with gesture IDs: 
> > synchronization of multiple parameter changer sources (for example,
> > a control surface, a hosts' generic UI, a custom UI, etc.).  How do
> > these different entities come up with unique gesture IDs when they
> > have no clue what the other entities are coming up with?
> 
> Provided these are actually "speaking the GMPI protocol", that would 
> be the responsibility of their hosts. For example, if you have two 
> hosts running on different machines; one for the GUIs and one for the 
> DSP plugins, the hosts would have to agree on something. Either split 
> the ID pool when making the host->host connection, or remap remote 
> IDs to/from local IDs somewhere in the host->host communication.

Thanks for explaining, I wasn't thinking of it as something coming from
the host, but that makes sense to me.

Okay, I feel fine with the gesture ID thing now, as has recently been
described, I won't object anymore.  :)

Marc

__________________________________
Do you Yahoo!?
Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes
http://hotjobs.sweepstakes.yahoo.com/signingbonus

----------------------------------------------------------------------
Generalized Music Plugin Interface (GMPI) public discussion list
Participation in this list is contingent upon your abiding by the
following rules:  Please stay on topic.  You are responsible for your own
words.  Please respect your fellow subscribers.  Please do not
redistribute anyone else's words without their permission.

Archive: http://www.freelists.org/archives/gmpi
Email gmpi-request@xxxxxxxxxxxxx w/ subject "unsubscribe" to unsubscribe

Other related posts: