[gmpi] Re: 3.12 Control I/O
- From: Chris Grigg <gmpi-public@xxxxxxxxxxxxxx>
- To: gmpi@xxxxxxxxxxxxx
- Date: Mon, 17 May 2004 19:09:23 -0700
> I'm beginning to think that these controller plugins don't just use a
parameter-out, since there is so much metadata and routing that needs to
be handled.
Hi Tim,
Well, to me control-out and parameter-in are opposit sides of the same coin.
It's natural to connect the two. They should use the same mechanism
(timestamped events).
Both generally have the same meta-data (datatype, hi/lo range, etc).
I guess I'm used to a modular approach, where you can connect any output
parameter to any input (of the same datatype). I like the flexibility that
gives.
Best Regards,
Jeff
If every event message contained both the set-to value and the
full-range value, then whatever entity receives the message could
handle it however it wants to, i.s. untransformed literal value as
provided, or normalized. No host intervention or other special
signalling to mess with (==get wrong).
Examples (please forgive horrible syntax):
- Set Volume in percent:
msgStructure {
targetParam = "master/volume";
value = 56.789f;
fullRange = 100.0f;
}
- Set Volume as 7-bit MIDI controller:
msgStructure {
targetParam = "master/volume";
value = 57 (int);
fullRange = 127 (int);
// Normalized value is 57/127 if you want it
}
Obviously this would only work for continuous-controller style
parameters, not strings, enums, bools, blobs, etc.
-- 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
- Follow-Ups:
- [gmpi] Re: 3.12 Control I/O
- From: Jeff McClintock
- References:
- [gmpi] 3.12 Control I/O
- From: Tim Hockin
- [gmpi] Re: 3.12 Control I/O
- From: Chris Grigg
- [gmpi] Re: 3.12 Control I/O
- From: Tim Hockin
- [gmpi] Re: 3.12 Control I/O
- From: Chris Grigg
- [gmpi] Re: 3.12 Control I/O
- From: Tim Hockin
- [gmpi] Re: 3.12 Control I/O
- From: Chris Grigg
- [gmpi] Re: 3.12 Control I/O
- From: Tim Hockin
- [gmpi] Re: 3.12 Control I/O
- From: Jeff McClintock
Other related posts:
- » [gmpi] 3.12 Control I/O
- » [gmpi] Re: 3.12 Control I/O
- » [gmpi] Re: 3.12 Control I/O
- » [gmpi] Re: 3.12 Control I/O
- » [gmpi] Re: 3.12 Control I/O
- » [gmpi] Re: 3.12 Control I/O
- » [gmpi] Re: 3.12 Control I/O
- » [gmpi] Re: 3.12 Control I/O
- » [gmpi] Re: 3.12 Control I/O
- » [gmpi] Re: 3.12 Control I/O
- » [gmpi] Re: 3.12 Control I/O
- » [gmpi] Re: 3.12 Control I/O
- » [gmpi] Re: 3.12 Control I/O
- » [gmpi] Re: 3.12 Control I/O
- » [gmpi] Re: 3.12 Control I/O
- » [gmpi] Re: 3.12 Control I/O
- » [gmpi] Re: 3.12 Control I/O
- » [gmpi] Re: 3.12 Control I/O
- » [gmpi] Re: 3.12 Control I/O
- » [gmpi] Re: 3.12 Control I/O
- » [gmpi] Re: 3.12 Control I/O
- » [gmpi] Re: 3.12 Control I/O
- » [gmpi] Re: 3.12 Control I/O
- » [gmpi] Re: 3.12 Control I/O
- » [gmpi] Re: 3.12 Control I/O
- » [gmpi] Re: 3.12 Control I/O
- » [gmpi] Re: 3.12 Control I/O
parameter-out, since there is so much metadata and routing that needs to be handled.
Hi Tim,
Well, to me control-out and parameter-in are opposit sides of the same coin. It's natural to connect the two. They should use the same mechanism (timestamped events).
Both generally have the same meta-data (datatype, hi/lo range, etc).
I guess I'm used to a modular approach, where you can connect any output parameter to any input (of the same datatype). I like the flexibility that gives.
Best Regards, Jeff
- [gmpi] Re: 3.12 Control I/O
- From: Jeff McClintock
- [gmpi] 3.12 Control I/O
- From: Tim Hockin
- [gmpi] Re: 3.12 Control I/O
- From: Chris Grigg
- [gmpi] Re: 3.12 Control I/O
- From: Tim Hockin
- [gmpi] Re: 3.12 Control I/O
- From: Chris Grigg
- [gmpi] Re: 3.12 Control I/O
- From: Tim Hockin
- [gmpi] Re: 3.12 Control I/O
- From: Chris Grigg
- [gmpi] Re: 3.12 Control I/O
- From: Tim Hockin
- [gmpi] Re: 3.12 Control I/O
- From: Jeff McClintock