[gmpi] Re: Decision time: 8.2
- From: "Vincent Burel" <vincent.burel@xxxxxxxxxx>
- To: <gmpi@xxxxxxxxxxxxx>
- Date: Wed, 27 Aug 2003 11:07:08 +0200
----- Original Message -----
From: "Marc Poirier" <fipnid@xxxxxxxxx>
To: <gmpi@xxxxxxxxxxxxx>
Sent: Wednesday, August 27, 2003 4:37 AM
Subject: [gmpi] Re: Decision time: 8.2
> Yeah, that's more what I was thinking anyway. It sure would be goofy for
> the DSP component to be simulating mouse-down / mouse-up events.
I'd prefer to talk about lock/unlock instead of (mouse-down / mouse-up) this
concept exists also on sensitive hardware remote... this is an event like an
other one... like the note-On Note-Off in the M.I.D.I. protocole. And there
is no difference to make with other events comming from a UI.
>At least
> I would find that silly. I was thinking that there would just be a more
> general mechanism in the API for indicating param-change-gesture-start and
> param-change-gesture-stop, like what you were just saying. And then some
> folks said that the DSP component itself should be prohibited from being
> able to use that mechanism. And I say, no, everyone should be able to use
> it, and in some (admittedly probably rare and esoteric) cases, the DSP
> component will have totally valid reasons for needing to use this
> mechanism. I think that everyone agrees that the mechanism needs to
> exist, though, right?
Of course right. the Lock/Unlock can help the DSP to decide which event has
to be processed , in wich order. Imagine the guy with the left hand on the
hardware remote, the right one on the mouse , and the sequencer which sends
automated data ! yes the DSP need to receive Lock/Unlock event !
Vincent Burel
----------------------------------------------------------------------
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
- References:
- [gmpi] Re: Decision time: 8.2
- From: Marc Poirier
Other related posts:
- » [gmpi] Decision time: 8.2
- » [gmpi] Re: Decision time: 8.2
- » [gmpi] Re: Decision time: 8.2
- » [gmpi] Re: Decision time: 8.2
- » [gmpi] Re: Decision time: 8.2
- » [gmpi] Re: Decision time: 8.2
- » [gmpi] Re: Decision time: 8.2
- » [gmpi] Re: Decision time: 8.2
- » [gmpi] Re: Decision time: 8.2
- » [gmpi] Re: Decision time: 8.2
- » [gmpi] Re: Decision time: 8.2
- » [gmpi] Re: Decision time: 8.2
- » [gmpi] Re: Decision time: 8.2
- » [gmpi] Re: Decision time: 8.2
- » [gmpi] Re: Decision time: 8.2
- » [gmpi] Re: Decision time: 8.2
- » [gmpi] Re: Decision time: 8.2
- » [gmpi] Re: Decision time: 8.2
- » [gmpi] Re: Decision time: 8.2
- » [gmpi] Re: Decision time: 8.2
- » [gmpi] Re: Decision time: 8.2
- » [gmpi] Re: Decision time: 8.2
- » [gmpi] Re: Decision time: 8.2
- » [gmpi] Re: Decision time: 8.2
- » [gmpi] Re: Decision time: 8.2
- » [gmpi] Re: Decision time: 8.2
- » [gmpi] Re: Decision time: 8.2
- » [gmpi] Re: Decision time: 8.2
- » [gmpi] Re: Decision time: 8.2
- » [gmpi] Re: Decision time: 8.2
- » [gmpi] Re: Decision time: 8.2
- » [gmpi] Re: Decision time: 8.2
- » [gmpi] Re: Decision time: 8.2
- » [gmpi] Re: Decision time: 8.2
- » [gmpi] Re: Decision time: 8.2
- » [gmpi] Re: Decision time: 8.2
- » [gmpi] Re: Decision time: 8.2
- » [gmpi] Re: Decision time: 8.2
- » [gmpi] Re: Decision time: 8.2
- » [gmpi] Re: Decision time: 8.2
- » [gmpi] Re: Decision time: 8.2
- » [gmpi] Re: Decision time: 8.2
- » [gmpi] Re: Decision time: 8.2
- » [gmpi] Re: Decision time: 8.2
- » [gmpi] Re: Decision time: 8.2
- » [gmpi] Re: Decision time: 8.2
- » [gmpi] Re: Decision time: 8.2
- » [gmpi] Re: Decision time: 8.2
- » [gmpi] Re: Decision time: 8.2
- » [gmpi] Re: Decision time: 8.2
- [gmpi] Re: Decision time: 8.2
- From: Marc Poirier