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

At 12:27 AM 5/29/03 -0700, you wrote: 
> The plugin does not know the criteria for optimisation, so it can't decide
> when it should do inplace and when not.

That's bass-ackwards to me. Only the plugin knows what it can optimize.

I touched on this earlier. To optimize buffer management in a graph, you label each input and output of each node with a buffer starting from the inputs to the graph. Any cascade of operations is best done in-place. A Y branch is dealt with by doing one branch as an in-place operation, and the other branch as not-in-place to temporary buffers. This general approach allows the graph to run with the minimum amount of buffer memory. The point is that the buffer optimization must be done by the host which knows the topology of the graph.

This assumes all operations can be done in-place or not-in-place. If we have flags that identify capability, then the host can use this to decide which branch of a Y is done which way.

Bill



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