[gmpi] Re: Topic 7: Audio packaging, Process-In-Place

> > Whenever it CAN re-use a buffer, it WILL.  This includes every plugin that
> > can use the simplest method, and probably a bunch for which that was too
> > restrictive.
> 
> But the plugin doesn't understand the graph, so it can;t know wether it
> appropriate to run inline, and if not what (host) buffer it should be
> writing to.

What part of the graph does the plugin need to understand?  I'm REALLY
missing something here..

Given:
* As soon as host calls process(), the buffers are the property of the plug
* All the input buffers are unique (or flagged read-only)

Task:
* Produce output buffers.

It doesn't matter how it is connected.  It doesn't matter what is upstream
or downstream.  All that matters is that the plugin generates a full set out
output buffers.  Simple plugins do 'out[s] = effect(in[s]);'.  More complex
stuff can swap buffers, re-arrange, use some buffers (ideally following the
rule 're-use as many buffers as you can').

You keep saying to think about the host's graph - where does that factor in
at all?

Tim

Sorry if I am being thick, I'm just not seeing it.

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

Other related posts: