[gmpi] Re: Decision time: 8.2

--- Chris Grigg wrote: 
 Given all that, I'm unclear on why touch automation wouldn't be
 purely a host issue.  IOW, how does any of this actually affect the
 plug-in API?  Why does the plug need to care whether the events it
 gets are coming from a touch update source? Like I said, maybe I'm
 just missing something.


No, the plugin doesn't need to know if touch automation is currently
occuring or not, I don't think.  But, if it has enough information to know
that it should be reporting parameter changes in a way such that touch
automation will work, if it is currently happening, then the plugin should
be able to do this.

But it can, and no API changes are necessary to enable that. If the plug wants to be adjusting parameters internally in response to incoming parameters, and sending events to reflect those changes, then why not just send them all the time? And/or, if, per your previous example, the plug only wants to send change events for the dependent parameters when the incoming parameter behaves in certain ways (like interpreting an event after a minimum lag since the previous event as the start of a gesture), then it's free to do that. And if the plug wants to limit the update rate for the dependent parameters, it can do that too. So I don't see why you say you need those mousedown/mouseup events...

...but if you still think you do, please propose a solution. I suppose it could be handled by establishing a parameter/event convention: i.e. UpdateInterval( parameterID, start | stop ).


But regarding your general uncertainty about this topic, I don't really
know where to start.  I have already written an awful lot of messages
trying to explain the details about this, so I don't really want to start
over again, so maybe if I knew more specifically which parts you weren't
following, it would be easier to try to clarify some points.  Also, it's
apparently off-topic now, so maybe it's best to just drop it altogether...

Marc

Actually I don't agree that this is off-topic and see no value in deferring its resolution. You obviously have a picture in mind and are certain that it relates to this point, so we should get to the bottom of the issue. Not that we shouldn't continue on other issues in parallel, we definitely should.

-- Chris G.

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