Subject: Re: [linux-audio-dev] MuCoS, Glame, API Issues
From: Richard Guenther (richi_AT_fs1.dekanat.physik.uni-tuebingen.de)
Date: to maalis 09 2000 - 04:58:13 EST
On Wed, 8 Mar 2000, Paul Barton-Davis wrote:
> >No, the API looks very strange to me, especially the "host controlled"
> >LADSPA_Data * DataLocation per connection!? what is this for (see
> >alexanders question below, too)??
>
> so that the host can improve cache performance by reusing data
> buffers. if you leave buffer allocation to the plugins, the chances
> are that you will trash the cache every time you call a new one. given
> that people have noticed this effect in Csound quite easily (if you
> reuse variable names for multiple purposes, a Csound instrument
> typically runs noticeably faster), I feel confident in pointing out
> that this is a very real effect.
How does host controlled allocation work, if you have sample generating
plugins? How does host controlled allocation work, f.i. on a resample
plugin? I dont see the point - if allocation is dedicated to the plugins
one can forward the buffer and do modifications in-place in every plugin,
this is more cache friendly than for each plugin having a seperate buffer
to read from and to write to. Well, I need to look at the code of the
host controller to gain more information on the internal handling of these
buffers, though (where's the source?).
Richard.
This archive was generated by hypermail 2b28 : su maalis 12 2000 - 09:14:05 EST