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

  • From: Mike Berry <mberry@xxxxxxxxx>
  • To: gmpi@xxxxxxxxxxxxx
  • Date: Sun, 01 Feb 2004 10:48:58 -0700



Koen Tanghe wrote: 


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.
But, it might really be too difficult to handle this in simple hosts...
Anyone here who can estimate the difficulties that may justify the "may
choose" instead of "must" approach?



There is simply no way that Premiere (not a simple host) is going to have a GMPI plugin controlling time in our graph. As an audio/video app, it is already a difficult task to negotiate timing. We have video devices, audio devices, display devices, and all of them want to be the master timing controller. If we have to allow some (audio) plugin(s) to also jump into the mix, that is too much. If phrased as a must, that would be a show-stopper for us.

--
Mike Berry
Adobe Systems


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

  1. Home
  2. gmpi
  3. Archive
  4. 02-2004