[gmpi] Revised Topic 7.3: Unconnected inputs/outputs
- From: Tim Hockin <thockin@xxxxxxxxxx>
- To: gmpi@xxxxxxxxxxxxx (GMPI Mailing list)
- Date: Fri, 6 Jun 2003 02:41:19 -0700 (PDT)
A new summary - please update it if you think anything is missing,
inaccurate, or mis-represented.
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, and no further
information (plugin may assume they are all always connected).
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) Same as option B, except the plugin is notified of the disconnected
state. Plugins may ignore the notice, and just read the zeroed
buffer. No extra work needed by plugins, optimizations are
possible.
f) Other. Explain.
----------------------------------------------------------------------
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:
