[gmpi] Re: R: Re: Topic 4: Host Interface
- From: "Laurent de Soras [Ohm Force]" <laurent@xxxxxxxxxxxx>
- To: gmpi@xxxxxxxxxxxxx
- Date: Fri, 28 Mar 2003 10:37:05 +0100
Angus F. Hewlett wrote:
>
Yes, we also have to distinguish between transport state and graph state.
Graph state must be controlled by the host (that's the definition of a
host, more-or-less), but transport state information should be pluggable
(that's not to say hosts must necessarily obey it).
I'd like to see transport information as simply another graph-level event
stream (or encapsulated within our other event streams, however it turns
out); that allows for the possibility of multiple musical-time contexts
within a single signal graph , and also for filters that are able to
transform time data.
It's exactly my opinion. And it doesn't prevent host to
function in the "traditional" way, being the master of
transport and time information. It's up to the host to
receive and/or make transit between plug-ins transport/time
events.
-- Laurent
==================================+========================
Laurent de Soras | Ohm Force
DSP developer & Software designer | Digital Audio Software
mailto:laurent@xxxxxxxxxxxx | http://www.ohmforce.com
==================================+========================
----------------------------------------------------------------------
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: R: Re: Topic 4: Host Interface
- From: Angus F. Hewlett
Other related posts:
- » [gmpi] R: Re: Topic 4: Host Interface
- » [gmpi] Re: R: Re: Topic 4: Host Interface
- » [gmpi] Re: R: Re: Topic 4: Host Interface
- » [gmpi] Re: R: Re: Topic 4: Host Interface
- » [gmpi] Re: R: Re: Topic 4: Host Interface
- » [gmpi] Re: R: Re: Topic 4: Host Interface
- » [gmpi] Re: R: Re: Topic 4: Host Interface
- » [gmpi] Re: R: Re: Topic 4: Host Interface
- » [gmpi] Re: R: Re: Topic 4: Host Interface
- » [gmpi] Re: R: Re: Topic 4: Host Interface
- » [gmpi] Re: R: Re: Topic 4: Host Interface
- » [gmpi] Re: R: Re: Topic 4: Host Interface
- » [gmpi] Re: R: Re: Topic 4: Host Interface
- » [gmpi] Re: R: Re: Topic 4: Host Interface
- » [gmpi] Re: R: Re: Topic 4: Host Interface
- » [gmpi] Re: R: Re: Topic 4: Host Interface
- » [gmpi] Re: R: Re: Topic 4: Host Interface
- » [gmpi] Re: R: Re: Topic 4: Host Interface
- » [gmpi] Re: R: Re: Topic 4: Host Interface
- » [gmpi] Re: R: Re: Topic 4: Host Interface
- » [gmpi] Re: R: Re: Topic 4: Host Interface
- » [gmpi] Re: R: Re: Topic 4: Host Interface
- » [gmpi] Re: R: Re: Topic 4: Host Interface
- » [gmpi] Re: R: Re: Topic 4: Host Interface
- » [gmpi] Re: R: Re: Topic 4: Host Interface
- » [gmpi] Re: R: Re: Topic 4: Host Interface
- » [gmpi] Re: R: Re: Topic 4: Host Interface
- » [gmpi] Re: R: Re: Topic 4: Host Interface
- » [gmpi] Re: R: Re: Topic 4: Host Interface
- » [gmpi] Re: R: Re: Topic 4: Host Interface
- » [gmpi] Re: R: Re: Topic 4: Host Interface
- » [gmpi] Re: R: Re: Topic 4: Host Interface
- » [gmpi] Re: R: Re: Topic 4: Host Interface
- » [gmpi] Re: R: Re: Topic 4: Host Interface
- » [gmpi] Re: R: Re: Topic 4: Host Interface
- » [gmpi] Re: R: Re: Topic 4: Host Interface
- » [gmpi] Re: R: Re: Topic 4: Host Interface
- » [gmpi] Re: R: Re: Topic 4: Host Interface
- » [gmpi] Re: R: Re: Topic 4: Host Interface
- » [gmpi] Re: R: Re: Topic 4: Host Interface
- » [gmpi] Re: R: Re: Topic 4: Host Interface
- » [gmpi] Re: R: Re: Topic 4: Host Interface
- » [gmpi] Re: R: Re: Topic 4: Host Interface
- » [gmpi] Re: R: Re: Topic 4: Host Interface
- » [gmpi] Re: R: Re: Topic 4: Host Interface
- » [gmpi] Re: R: Re: Topic 4: Host Interface
- » [gmpi] Re: R: Re: Topic 4: Host Interface
- » [gmpi] Re: R: Re: Topic 4: Host Interface
- » [gmpi] Re: R: Re: Topic 4: Host Interface
- » [gmpi] Re: R: Re: Topic 4: Host Interface
- » [gmpi] Re: R: Re: Topic 4: Host Interface
- » [gmpi] Re: R: Re: Topic 4: Host Interface
- » [gmpi] Re: R: Re: Topic 4: Host Interface
- » [gmpi] Re: R: Re: Topic 4: Host Interface
- » [gmpi] Re: R: Re: Topic 4: Host Interface
- » [gmpi] Re: R: Re: Topic 4: Host Interface
Angus F. Hewlett wrote: >
Yes, we also have to distinguish between transport state and graph state. Graph state must be controlled by the host (that's the definition of a host, more-or-less), but transport state information should be pluggable (that's not to say hosts must necessarily obey it).
I'd like to see transport information as simply another graph-level event stream (or encapsulated within our other event streams, however it turns out); that allows for the possibility of multiple musical-time contexts within a single signal graph , and also for filters that are able to transform time data.
It's exactly my opinion. And it doesn't prevent host to function in the "traditional" way, being the master of transport and time information. It's up to the host to receive and/or make transit between plug-ins transport/time events.
---------------------------------------------------------------------- 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.
- [gmpi] Re: R: Re: Topic 4: Host Interface
- From: Angus F. Hewlett