[gmpi] Re: 3.11 Parameters
- From: Tim Hockin <thockin@xxxxxxxxxx>
- To: gmpi@xxxxxxxxxxxxx
- Date: Wed, 31 Mar 2004 11:57:04 -0800
On Wed, Mar 31, 2004 at 08:50:17PM +0100, Steve Harris wrote:
> > Phew, that at least doesn't make me puke! :)
>
> Is that because the parameter that controls port creation is not
> automatable, or because its not a parameter, or becuase automation is
> broken :)
Yes.
> If you tell the UI to change the i/os, does it really tell the host to
> stop the plugin, change some stuff and start it up again?
Whether the host stops the plugin or not is up to the host. Chaning I/O
configs is not the sort of thing that happens as part of a performance, it's
like instantiating a new plugin. You can do it (with potential RT issues)
while a performance is running, but it isn't part of the performance.
It isn't automated, it isn't a parameter, it's akin to a plugin
destroy/create pair. Whether it is implemented as such or not...
----------------------------------------------------------------------
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: //www.freelists.org/archives/gmpi
Email gmpi-request@xxxxxxxxxxxxx w/ subject "unsubscribe" to unsubscribe
Other related posts:
