[gmpi] Re: Reqs 3.8 Events - gesture start/end

>>gesturing, on my understanding, refers to a situation
>> where you wish to set more than parameter at the same time,
>
>Hi Paul,
>Reading your email more carefully, I think we're taking about different
>things.
>
> With these new control surfaces, it's posible to touch a hardware slider,
>but not actually move it.  This indicates to your music software that you
>wish to overwrite any pre-recorded automation with new movements.
>   i.e it's important to know when the user touched and released the slider
>(in addition to recording any actual movements).  kind of an automated
>punch-in/punch-out.

indeed. this is a totally different topic. step back. the h/w control
surface sends a packetized data stream. software on the computer
decodes it, and handles the request for a change in a parameter. this
is serialized, non-gestural.

however, going a step further, michael reminded me of XY pads. anytime
the control device sends two parameters as part of a single message,
we have something that is very close to, gestural. consider a simple
XY pad. each message it transmits contains 2 pieces of information
that could be used to control two parameters independently, yet the
message arrives "atomically", so you effectively changing two
parameters at the same time. all the same, you can do this with the
slider too, just map two parameters to the same control point.

what would i consider a gesture? image using a radio baton (c/o
richard boulanger, or other similar devices made by others). this can
send potentially 3 or more values as part of a single control message
(X,Y,Z plus potentially pressure). when the message is translated into
parameters changes, the changes caused by each component of the
control device's message need to be atomic with respect to each
other. this is where you'd need to flag a gesture: "i am going to set
velocity, pitch and start a new note, and this is all part of the same
*gesture*". 

the primary current point of use for gestures seems to me to be
modelled on something like the Music N languages, where a given voice
can have an almost unlimited number of parameters and you may want to
set them all at once, rather than considering them discrete parameter
setting events.

touch automation is completely different and exists at the host level,
not the plugin level.

--p


----------------------------------------------------------------------
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: