[gmpi] Re: Decision time: 7.2
- From: Mike Berry <mberry@xxxxxxxxx>
- To: gmpi@xxxxxxxxxxxxx
- Date: Fri, 18 Jul 2003 18:26:31 -0600
e.) A plugin is passed input and output buffers. The output buffers may
be NULL, indicating that the corresponding input buffer should be
processed in place. Hosts must not pass NULL output buffers if the
plugin is assymetrical in its inputs and outputs. Hosts must not mix
NULL and non-NULL output buffers in a single call.
Therefore, all symmetrical plugins must support in place and copy to
processing. All assymetrical plugins only support copy-to processing.
All buffer management is handled by the host.
Tim Hockin wrote:
Moving on! :)
Topic 7.2: In-place processing
-------------------------------
Q: Do we do in-place processing?
a) Yes. A plugin-global flag indicates a plugins ability to do this.
This tells the host that ANY input buffer may be re-used on ANY output
(perhaps withing some higher-level grouping of stuff (think MIDI
channel?)). If a plug can not accept this rule, it must not use
in-place processing. (VST model?)
b) Yes. A plugin statically maps inputs to outputs. The host may
re-use an input buffer for an output if they map together.
c) Yes. A plugin is given inputs and produces it's own output buffers
based on internal knowledge or other variables. The host is not
involved, except to furnish new buffers as requested. The plugin must
re-use or release all input buffers. Variations on this can be devised
to allowed shared input/outputs. (baton passing, or similar to DX model)
d) No. All output buffers are unique from input buffers.
e) 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: http://www.freelists.org/archives/gmpi
Email gmpi-request@xxxxxxxxxxxxx w/ subject "unsubscribe" to unsubscribe
--
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: http://www.freelists.org/archives/gmpi
Email gmpi-request@xxxxxxxxxxxxx w/ subject "unsubscribe" to unsubscribe
- Follow-Ups:
- [gmpi] Re: Decision time: 7.2
- From: Steve Harris
- References:
- [gmpi] Decision time: 7.2
- From: Tim Hockin
Other related posts:
- » [gmpi] Decision time: 7.2
- » [gmpi] Re: Decision time: 7.2
- » [gmpi] Re: Decision time: 7.2
- » [gmpi] Re: Decision time: 7.2
- » [gmpi] Re: Decision time: 7.2
- » [gmpi] Re: Decision time: 7.2
- » [gmpi] Re: Decision time: 7.2
- » [gmpi] Re: Decision time: 7.2
- » [gmpi] Re: Decision time: 7.2
- » [gmpi] Re: Decision time: 7.2
- » [gmpi] Re: Decision time: 7.2
- » [gmpi] Re: Decision time: 7.2
- » [gmpi] Re: Decision time: 7.2
- » [gmpi] Re: Decision time: 7.2
- » [gmpi] Re: Decision time: 7.2
- » [gmpi] Re: Decision time: 7.2
- » [gmpi] Re: Decision time: 7.2
- » [gmpi] Re: Decision time: 7.2
- » [gmpi] Re: Decision time: 7.2
- » [gmpi] Re: Decision time: 7.2
- » [gmpi] Re: Decision time: 7.2
- » [gmpi] Re: Decision time: 7.2
- » [gmpi] Re: Decision time: 7.2
- » [gmpi] Re: Decision time: 7.2
- » [gmpi] Re: Decision time: 7.2
- » [gmpi] Re: Decision time: 7.2
- » [gmpi] Re: Decision time: 7.2
- » [gmpi] Re: Decision time: 7.2
- » [gmpi] Re: Decision time: 7.2
- » [gmpi] Re: Decision time: 7.2
- » [gmpi] Re: Decision time: 7.2
- » [gmpi] Re: Decision time: 7.2
- » [gmpi] Re: Decision time: 7.2
- » [gmpi] Re: Decision time: 7.2
- » [gmpi] Re: Decision time: 7.2
- » [gmpi] Re: Decision time: 7.2
Topic 7.2: In-place processing -------------------------------
Q: Do we do in-place processing?
a) Yes. A plugin-global flag indicates a plugins ability to do this.
This tells the host that ANY input buffer may be re-used on ANY output
(perhaps withing some higher-level grouping of stuff (think MIDI
channel?)). If a plug can not accept this rule, it must not use
in-place processing. (VST model?) b) Yes. A plugin statically maps inputs to outputs. The host may
re-use an input buffer for an output if they map together. c) Yes. A plugin is given inputs and produces it's own output buffers
based on internal knowledge or other variables. The host is not
involved, except to furnish new buffers as requested. The plugin must
re-use or release all input buffers. Variations on this can be devised
to allowed shared input/outputs. (baton passing, or similar to DX model)d) No. All output buffers are unique from input buffers.
e) 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: http://www.freelists.org/archives/gmpi Email gmpi-request@xxxxxxxxxxxxx w/ subject "unsubscribe" to unsubscribe
---------------------------------------------------------------------- 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.
- [gmpi] Re: Decision time: 7.2
- From: Steve Harris
- [gmpi] Decision time: 7.2
- From: Tim Hockin