[gmpi] Re: Topic 7.3: Unconnected inputs/outputs
- From: Tim Hockin <thockin@xxxxxxxxxx>
- To: gmpi@xxxxxxxxxxxxx
- Date: Mon, 2 Jun 2003 15:19:16 -0700 (PDT)
Damn, I did it again.
> Resending with new notes and annotations
>
> > Topic 7.3: Unconnected inputs/outputs
> > ------------------------------------------
> >
> > Q: How do we handle disconnected inputs/outputs?
> >
> > a) They are given a NULL buffer and must detect it.
> >
> > b) They are given a zero-filled (or SILENT) buffer.
> >
> > 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.
>
> d) The host may disconnect an input/output at any time. Plugins will be
> notified when a port is connected or disconnected. Plugins must internally
> handle a disconnected input/output or request special ZERO and TRASH buffers
> from the host (or something like that). This is conceptually the same as
> c), with clarifications and less resposibility for the host.
e) The plugin ALWAYS gets connections on all audio ports. Disconnected inputs
are zero-filled and flagged as 'disconnected'. Similar for outputs. The
plugin can see this at connection time and optimize or just use as-is.
----------------------------------------------------------------------
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:
