[gmpi] Re: Reqs 3.8 Events - gesture start/end
- From: Mike Berry <mberry@xxxxxxxxx>
- To: gmpi@xxxxxxxxxxxxx
- Date: Mon, 29 Dec 2003 15:54:57 -0700
I never meant that one gesture could not affect multiple parameters. In
fact it should be able to. However, what I meant by there not being
gesture polyphony was that one parameter could not be simultaneously
part of multiple gestures. I cannot see a good argument for trying to
support that.
Mike
gogins@xxxxxxxxxxxx wrote:
Evidently we do not agree as to the meaning of the word "gesture". To me,
it means a physical performance gesture, like bowing a fiddle, or an analog
thereof, like touching a pad. Therefore, a gesture can control more than
one parameter at the same time (as a fiddle bow controls both volume and
vibrato, and even timbre depending on how near the bridge it is; or when an
x-y controller is used). Futhermore, obviously more than one gesture can
occur at the same time, as when a guitarist slams the whammy bar and steps
on a wah-wah pedal. The requirement for gestural control is to represent a
high volume of multi-parametric control data that is assigned to one or
more specific voices, unit generators, or instruments or sets of
instruments.
Original Message:
-----------------
From: Paul Davis paul@xxxxxxxxxxxxxxxxxxxxx
Date: Mon, 29 Dec 2003 16:31:59 -0500
To: gmpi@xxxxxxxxxxxxx
Subject: [gmpi] Re: Reqs 3.8 Events - gesture start/end
there is no need for "gesture polyphony." It is a requirement
that the host send a gesture end event prior to sending a second gesture
start event.
Hi Mike,
Just to be clear. Two different parameters could have independent gesture
start/stop.
e.g. I might be automating a mixdown on a hardware control surface, and
have one hand on chan1 volume, and the other on chan2 volume. Both these
gestures might overlap.
i don't believe that this is a valid example of
"gesturing". gesturing, on my understanding, refers to a situation
where you wish to set more than parameter at the same time, even
though the events/messages describing these changes are inevitably
serialized. hardware control surfaces don't generate gestures. script
files (such as a Csound score file) do.
--p
--
Mike Berry
Adobe Systems
----------------------------------------------------------------------
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
- Follow-Ups:
- [gmpi] Re: Reqs 3.8 Events - gesture start/end
- From: Tim Hockin
- References:
- [gmpi] Re: Reqs 3.8 Events - gesture start/end
- From: gogins@xxxxxxxxxxxx
Other related posts:
- » [gmpi] Re: Reqs 3.8 Events - gesture start/end
- » [gmpi] Re: Reqs 3.8 Events - gesture start/end
- » [gmpi] Re: Reqs 3.8 Events - gesture start/end
- » [gmpi] Re: Reqs 3.8 Events - gesture start/end
- » [gmpi] Re: Reqs 3.8 Events - gesture start/end
- » [gmpi] Re: Reqs 3.8 Events - gesture start/end
- » [gmpi] Re: Reqs 3.8 Events - gesture start/end
- » [gmpi] Re: Reqs 3.8 Events - gesture start/end
- » [gmpi] Re: Reqs 3.8 Events - gesture start/end
- » [gmpi] Re: Reqs 3.8 Events - gesture start/end
- » [gmpi] Re: Reqs 3.8 Events - gesture start/end
- » [gmpi] Re: Reqs 3.8 Events - gesture start/end
- » [gmpi] Re: Reqs 3.8 Events - gesture start/end
- » [gmpi] Reqs 3.8 Events - gesture start/end
- » [gmpi] Re: Reqs 3.8 Events - gesture start/end
- » [gmpi] Re: Reqs 3.8 Events - gesture start/end
- » [gmpi] Re: Reqs 3.8 Events - gesture start/end
- » [gmpi] Re: Reqs 3.8 Events - gesture start/end
- » [gmpi] Re: Reqs 3.8 Events - gesture start/end
- » [gmpi] Re: Reqs 3.8 Events - gesture start/end
- » [gmpi] Re: Reqs 3.8 Events - gesture start/end
- » [gmpi] Re: Reqs 3.8 Events - gesture start/end
- » [gmpi] Re: Reqs 3.8 Events - gesture start/end
- » [gmpi] Re: Reqs 3.8 Events - gesture start/end
- » [gmpi] Re: Reqs 3.8 Events - gesture start/end
- » [gmpi] Re: Reqs 3.8 Events - gesture start/end
- » [gmpi] Re: Reqs 3.8 Events - gesture start/end
- » [gmpi] Re: Reqs 3.8 Events - gesture start/end
- » [gmpi] Re: Reqs 3.8 Events - gesture start/end
- » [gmpi] Re: Reqs 3.8 Events - gesture start/end
- » [gmpi] Re: Reqs 3.8 Events - gesture start/end
- » [gmpi] Re: Reqs 3.8 Events - gesture start/end
- » [gmpi] Re: Reqs 3.8 Events - gesture start/end
- » [gmpi] Re: Reqs 3.8 Events - gesture start/end
- » [gmpi] Re: Reqs 3.8 Events - gesture start/end
- » [gmpi] Re: Reqs 3.8 Events - gesture start/end
- » [gmpi] Re: Reqs 3.8 Events - gesture start/end
- » [gmpi] Re: Reqs 3.8 Events - gesture start/end
- » [gmpi] Re: Reqs 3.8 Events - gesture start/end
- » [gmpi] Re: Reqs 3.8 Events - gesture start/end
- » [gmpi] Re: Reqs 3.8 Events - gesture start/end
- » [gmpi] Re: Reqs 3.8 Events - gesture start/end
- » [gmpi] Re: Reqs 3.8 Events - gesture start/end
- » [gmpi] Re: Reqs 3.8 Events - gesture start/end
- » [gmpi] Re: Reqs 3.8 Events - gesture start/end
- » [gmpi] Re: Reqs 3.8 Events - gesture start/end
- » [gmpi] Re: Reqs 3.8 Events - gesture start/end
- » [gmpi] Re: Reqs 3.8 Events - gesture start/end
- » [gmpi] Re: Reqs 3.8 Events - gesture start/end
- » [gmpi] Re: Reqs 3.8 Events - gesture start/end
- » [gmpi] Re: Reqs 3.8 Events - gesture start/end
- » [gmpi] Re: Reqs 3.8 Events - gesture start/end
- » [gmpi] Re: Reqs 3.8 Events - gesture start/end
- » [gmpi] Re: Reqs 3.8 Events - gesture start/end
- » [gmpi] Re: Reqs 3.8 Events - gesture start/end
- » [gmpi] Re: Reqs 3.8 Events - gesture start/end
- » [gmpi] Re: Reqs 3.8 Events - gesture start/end
- » [gmpi] Re: Reqs 3.8 Events - gesture start/end
- » [gmpi] Re: Reqs 3.8 Events - gesture start/end
- » [gmpi] Re: Reqs 3.8 Events - gesture start/end
- » [gmpi] Re: Reqs 3.8 Events - gesture start/end
- » [gmpi] Re: Reqs 3.8 Events - gesture start/end
- » [gmpi] Re: Reqs 3.8 Events - gesture start/end
- » [gmpi] Re: Reqs 3.8 Events - gesture start/end
- » [gmpi] Re: Reqs 3.8 Events - gesture start/end
- » [gmpi] Re: Reqs 3.8 Events - gesture start/end
- » [gmpi] Re: Reqs 3.8 Events - gesture start/end
- » [gmpi] Re: Reqs 3.8 Events - gesture start/end
- » [gmpi] Re: Reqs 3.8 Events - gesture start/end
- » [gmpi] Re: Reqs 3.8 Events - gesture start/end
- » [gmpi] Re: Reqs 3.8 Events - gesture start/end
- » [gmpi] Re: Reqs 3.8 Events - gesture start/end
- » [gmpi] Re: Reqs 3.8 Events - gesture start/end
- » [gmpi] Re: Reqs 3.8 Events - gesture start/end
Evidently we do not agree as to the meaning of the word "gesture". To me, it means a physical performance gesture, like bowing a fiddle, or an analog thereof, like touching a pad. Therefore, a gesture can control more than one parameter at the same time (as a fiddle bow controls both volume and vibrato, and even timbre depending on how near the bridge it is; or when an x-y controller is used). Futhermore, obviously more than one gesture can occur at the same time, as when a guitarist slams the whammy bar and steps on a wah-wah pedal. The requirement for gestural control is to represent a high volume of multi-parametric control data that is assigned to one or more specific voices, unit generators, or instruments or sets of instruments.
Original Message:
-----------------
From: Paul Davis paul@xxxxxxxxxxxxxxxxxxxxx
Date: Mon, 29 Dec 2003 16:31:59 -0500
To: gmpi@xxxxxxxxxxxxx
Subject: [gmpi] Re: Reqs 3.8 Events - gesture start/end
there is no need for "gesture polyphony." It is a requirement that the host send a gesture end event prior to sending a second gesture start event.
Hi Mike, Just to be clear. Two different parameters could have independent gesture start/stop.
e.g. I might be automating a mixdown on a hardware control surface, and have one hand on chan1 volume, and the other on chan2 volume. Both these gestures might overlap.
i don't believe that this is a valid example of "gesturing". gesturing, on my understanding, refers to a situation where you wish to set more than parameter at the same time, even though the events/messages describing these changes are inevitably serialized. hardware control surfaces don't generate gestures. script files (such as a Csound score file) do.
--p
-- Mike Berry Adobe Systems
---------------------------------------------------------------------- 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.
- [gmpi] Re: Reqs 3.8 Events - gesture start/end
- From: Tim Hockin
- [gmpi] Re: Reqs 3.8 Events - gesture start/end
- From: gogins@xxxxxxxxxxxx