[linux-audio-dev] Plugin APIs (again)

Steve Harris S.W.Harris at ecs.soton.ac.uk
Mon Dec 9 09:40:00 UTC 2002


On Mon, Dec 09, 2002 at 02:10:09PM +0100, David Olofson wrote:
> > Actually it quickly became obvious that for a host to construct a
> > useful GUI the plugin has to at least hint at some ranges.
> 
> Yes, *hint*.

Yes, I agree with you entirly on this point.
 
> > > the RT engine - *unless* you decide on a number of VVIDs to
> > > allocate for each Channel of every plugin, right when they're
> > > instantiated.
> >
> > That sound most sensible. The instrument has to allocate voice
> > table space, so there is likly to be an internal (soft) limit
> > anyway.
> 
> Yes... But keep in mind that there is no strict relation between 
> Physical Voices and Virtual Voices. A synth with only 32 voices may 
> be played with 8 VVIDs or 256 VVIDs. The number of VVIDs is decided 
> by the *sender*, so it can manage the polyphony it wants in a 
> sensible way. The synth only uses the VVIDs to keep track of which 
> Virtual Voice the sender is talking about - whether or not it 
> actually has a Physical Voice at the moment. Voice allocator in 
> between.

OK, but I dont think that actually changes anything at the API level.

- Steve



More information about the Linux-audio-dev mailing list