[gmpi] Re: 3.12 Control I/O

Tim said: 
They are 'logically' the same.  But really there are two forms of control
outs.  Specific and generic.
...
Generic outputs can be tied to ANYTHING.  My point was that *maybe* these
generic outputs are different at a more fundamental level.

IMHO, I don't think they are different fundamentally. Why would we want them to be, what's the advantage in that? You got outs with ranges, you got ins with ranges, what's to get in the way of out = ( val - outRangeMin ) / ( outRangeMax - outRangeMin ) * ( inRangeMax - inRangeMin ) + inRangeMin? Unless you want a destination to be able to disable this for some sort of rounding error avoidance.

Maybe we can just address this with really simple requirements language along these lines?:

"It should be possible for any source of parameter-setting events (for continuous controls only) to properly drive any target parameter in the graph, irrespective of any differences between source and destination natural value ranges. In other words, conversion to and from normalized values must be possible and should be simple to implement. Design of this feature are expected to make use of the source and destination value range metadata."

Does this do the job?

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