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

Caveat:  I'm technically out-of-office, and I haven't read this long and
what looks to be very productive thread.  I'll catch up on my flight home
tomorrow.

>>>
A light bulb did go on today when I realized the ordering issue.  Is this
actually a common case?  It seems the ONLY time this can happen is when the
host does a Y split.  Plugins obviously would not have the same buffer for
two outputs (except a trash output for disconnected outs..).  So this case
can happen only when a host wants to clone a channel.

Is that really that common that it is the sole reason to shoot down
potential other wins?
<<<

Our host app uses the some component API for internal mixers and tees as
what's used for the plugins.  This will be true when we host GMPI plugins.
One internal mixer component is "Y" split, known to the user as a "bus
send."  This a very common component from the host side, and actually sadly
one of the most expensive because of the reuqired buffer copy.

What we do today with splitters is have the plugin process the first output
in place, and then allocate new buffers for all other outputs.  We don't
attempt to determine whether or not output buffers are processed in-place
downstream or not to try to save an extra buffer copy.  Must plugins are
in-place, so it's simply more likely that a buffer copy will be needed.

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