Subject: RE: [linux-audio-dev] MuCoS, Glame, API Issues
From: Benno Senoner (sbenno_AT_gardena.net)
Date: Sun Mar 12 2000 - 09:55:30 EST
On Sun, 12 Mar 2000, David Olofson wrote:
> On Fri, 10 Mar 2000, Richard Guenther wrote:
> > > This is a choice the host can make depending on what the current
> > > processing net looks like. Plugins don't have to bother with it
> > > anything more than either supporting in-place processing (most algos
> > > inherently do), or saying LADSPA_PROPERTY_INPLACE_BROKEN.
> >
> > So a plugin that supports inplace modifying still needs to support the
> > case of non inplace modifying? Err...
>
> Not explicitly. You always have one input buffer pointer and one
> output buffer pointer. If the plugin supports inplace processing, the
> host may chose to use the same physical memory for both buffers. It
> makes no difference to the plugin.
>
>
> //David
I wouldn't say that: there are some plugins/ algorithms which need separate
input and output memory areas, since the source data gets overwritten during
processing, in order to optimize the algorithm.
In this case the plugin should inform the host that it doesn't support
input buffer == output buffer using some flags.
Or am I missing something ?
Benno.
This archive was generated by hypermail 2b28 : Sun Mar 12 2000 - 18:28:09 EST