[gmpi] Re: 3.8 update
- From: Marc Poirier <fipnid@xxxxxxxxx>
- To: gmpi@xxxxxxxxxxxxx
- Date: Fri, 16 Jan 2004 08:10:23 -0800 (PST)
It looks good to me, after all of the suggestions that Chris made.
--- Chris Grigg wrote:
> >I've put the gestures and ramped events stuff into section 3.8.
> >
> >We've got to finish debate on ramping, and we may want to change the
> >terminology on gestures (see a previous mail from me).
> >
> >Please have a read-over. If we want to change things, lets get them
> done,
> >soon. This topic has taken a looong time. :P
> >
> >http://www.gmpi-plugins.org/gmpi/requirements.php
>
>
> Looking good. Just a couple suggested edits to address some slight
> vagueness in the current draft:
>
> >3.8. Events
> >
> >Req 22: GMPI must implement a time-stamped, sample-accurate event
> >system. Events are how...
>
> ...all real-time signals and other events including...
>
> >...control changes are represented.
> >
> >Req 23: All events bound for a plugin during a timeslice must be
> >delivered...
>
> (Should that be 'enqueued' for clarity?)
>
> >...before...
>
> ...the process() function of...
>
> >...that plugin is run. Events must never delivered while a plugin
> >is processing.
>
> (Maybe make that: 'GMPI hosts will never deliver any additional
> events during execution of a plug-in's process() function.'?)
>
>
> >Req 24: Event timestamps....
>
> ...that the plug-in sees in its input queues...
>
> >..must be measured as a sample frame offset from thestart of the
> >processing block.
>
> (Maybe make that 'time slice' for consistency?)
>
>
> >Req 25: GMPI must provide...
>
> (Maybe make that 'support'?)
>
> >...ramped events for controls with real number types. Plugins
> >that do not handle...
>
> (Maybe make that 'process'?)
>
> >...ramped events must be able to receive point value events, or
> >convert ramped events into point value events.
>
> (Maybe make that 'must treat ramp events as immediate point events
> (by ignoring the event's ramp duration and jumping directly to the
> event's target value)'?)
>
>
> >Req 26: GMPI....
>
> ...hosts...
>
> >..must support grouping events into 'gestures'. It must be possible
> >to include zero or more events for multiple controls in a gesture.
> >Gestures must be optional for all plugins...
>
> (Maybe make that 'Support for gesture grouping in plug-ins is
> optional.'? The phrase 'must be optional' is a little confusing.)
>
> >....The host must handle the case of conflicting gestures.
>
> (Maybe define 'conflicting gestures'?)
>
> -- Chris G.
__________________________________
Do you Yahoo!?
Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes
http://hotjobs.sweepstakes.yahoo.com/signingbonus
----------------------------------------------------------------------
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:
