[gmpi] Re: Decision time: 7.2
- From: Tim Hockin <thockin@xxxxxxxxxx>
- To: gmpi@xxxxxxxxxxxxx
- Date: Tue, 5 Aug 2003 17:18:27 -0700 (PDT)
> > but we already outlined our desired handling of the input/pin mapping,
> > and there is never a situation like the one in bidule that you
> > describe. 1 pin corresponds to a single stream of data, and hence one
> > buffer. plugins can group pins if they wish. i think i got that right.
>
> Hmmm... Maybe the host can model this as an extra (invisible) block in front
> of the one where the pins come together, and this extra block just does the
> mixing before sending it through as a single audio stream to the block
> "where the pins come together"? But then the (invisible) mixing block should
> be able to handle an arbitrary number of inputs. I don't know how Bidule
> handles this internally though...
Making it a separate block (explicit or implicit) loses the possible
optimization from mix-into processing. Ading the extra entity means that
there are distinct input buffers and a process() call which sums them up.
I'm not saying this is a bad thing - the design is clean, but maybe there is
a way to keep that optimization? Too low level for right now.
Tim
----------------------------------------------------------------------
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:
