Subject: Re: [linux-audio-dev] Plugin APIs (again)
From: Steve Harris (S.W.Harris_AT_ecs.soton.ac.uk)
Date: Mon Dec 09 2002 - 14:34:06 EET
On Mon, Dec 09, 2002 at 01:25:24AM +0100, David Olofson wrote:
> On Sunday 08 December 2002 22.59, Steve Harris wrote:
> > On Sun, Dec 08, 2002 at 12:19:06PM -0800, Tim Hockin wrote:
> > > I'll buy that. Once the host reads the initial values, it should
> > > refrain from bothering the plugin.
> >
> > I think the host should be able to give the instrument its initial
> > values, read for deafults, or a settings file etc.
>
> Defaults should be part of the control description, just like with
> LADSPA ports, IMO. And why is reading controls for saving to a file
> different from the usual "remember what you say to the plugin"?
Agreed. That was my point, I think.
> That, and/or there should be ramp events. Those can be a bit hairy to
> deal with at times, but please, do suggest an alternative if there is
> one that is simpler and still sufficient for sample accurate
> control... (No, no audio rate "raw" control ports, please!)
Heh, maybe not for this API, but they are fundmanetally superior :)
I look forward to a few years where all DSP code can run blockless and
with audio rate (or near audio rate) control.
> > In practice most hosts only send values within the range hints.
>
> IMHO, in the new API, no host should *ever* use an out-of-range value
> when dealing with hard ranges. So, ranges *may* be hints, but if
> they're *hard*, they're much more than hints.
OK, fine by me.
- Steve
This archive was generated by hypermail 2b28 : Mon Dec 09 2002 - 14:38:43 EET