[gmpi] Re: Revised Topic 7.3: Unconnected inputs/outputs

  • From: Steve Harris <S.W.Harris@xxxxxxxxxxxxxxx>
  • To: gmpi@xxxxxxxxxxxxx
  • Date: Sat, 7 Jun 2003 00:41:57 +0100

On Fri, Jun 06, 2003 at 12:30:42 -0700, Tim Hockin wrote:
> > On Fri, Jun 06, 2003 at 02:41:19 -0700, Tim Hockin wrote:
> > >   c) If a plugin supports disconnected inputs/outputs, they are flagged
> > >      or negotiated at connection-time.  If an in/out is agreed to be
> > >      disconnected, no buffer is needed.  Otherwise, the host must
> > >      provide a zero-filled (or SILENT) buffer for logically disconnect
> > >      in/outs.
> > 
> > I prefer that the /ports/ (not buffers) are always flagged, and the host
> > always provides buffers. Simpler and functionally equivalent.
> 
> Which was exactly option E.
> 
>   b) They are given a zero-filled (or SILENT) buffer, and no further
>      information (plugin may assume they are all always connected).
>   e) Same as option B, except the plugin is notified of the disconnected
>      state of the port.  Plugins may ignore the notice, and just read
>      the zeroed buffer.  No extra work needed by plugins, optimizations
>      are possible.

OK, I read "notified" to mean an event was sent, not a flag was set.
Important difference.

- Steve 

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