[gmpi] Re: Reqs 3.9. Time - opening arguments

  • From: Tim Hockin <thockin@xxxxxxxxxx>
  • To: gmpi@xxxxxxxxxxxxx
  • Date: Sun, 1 Feb 2004 14:50:29 -0800

On Sun, Feb 01, 2004 at 06:16:44PM +0100, Koen Tanghe wrote:
> FIXME: The group talked about UST time. Do we really need UST? If so, what
> for? What minimum granularity? Can UST-time wrap? How is this handled?
> --> IIRC, UST time will be needed to sync GMPI hosts (plugins?) connected
> over a (global) network. UST makes sure there is 1 unique "wall clock"
> regardless of where the host is located in the world.


UST *has* to be platform specific.  Is it milliseconds?  microseconds?
processor cycles?  There is no global definition of a UST.

> Req 29:   Every GMPI plugin must be associated with exactly one timeline
> controller.
> --> Maybe replace "must be associated with" by "is driven by" to emphasize
> it's about a timeline INPUT, not output?

Good - updated

> Req 30:   GMPI must allow more than one timeline controller in a graph.
> Hosts may choose not to allow this.
> Req 33:   GMPI must provide a way for a plugin to control a timeline. Hosts
> may choose not to allow this.

> --> I guess the "may choose not to allow this" is because this will be too
> complicated to handle for simple hosts? I'm just a bit worried that this
> might lead to the "no you can't use this plugin in host X, because it
> doesn't support property A, but hosts Y and Z do support it" phenomenon.

I don't want to see the incompatibilities creep in.  Can this reasonably
made a required feature?

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: