Hi Richard,
my wishlist for LADSPA 1.1 (which does not break compatibillity)
1.) Could the ladspa packe have gnu-configure support (i'll gladly help with that).
2.) Could qwe agree to the following ladspa installation layout
$LADSPA_HOME (this is the $prefix from configure, which can be /opt/lad
On Mon, May 13, 2002 at 10:22:29 +0100, Richard W.E. Furse wrote:
> > 1) Default values
> On its way for LADSPA 1.1 (along with 0dB=1.0f). Yes Steve, it has been
:)
> ... But I think most of this is available already through ecasound or
> suchlike.
SSM can do that stuff, but it doesn't store it
On Tue, May 14, 2002 at 11:08:00 +0200, Dr. Matthias Nagorni wrote:
[int port types]
> So you would like to have ports where some int values have special
> meanings like "half wave" or "full wave" but you still would like to allow
> non-int input to these ports, right ? Then you perhaps would like
On Mon, 13 May 2002, Richard W.E. Furse wrote:
> > 4) LADSPA_IS_PORT_DYNAMIC
> I don't understand this. Are we just saying this is an array? If so, I think
> this goes beyond LADSPA's scope.
Yes. In principle one could use audio ports for this purpose. I was
thinking of ports that accept e.g. LFO
On Mon, 13 May 2002, Steve Harris wrote:
> > > > 7) Type of integer port int not float
> > > Don't think it helps much, in some cases there is a fine line between
> > > integer and non-integer ports, eg. "mode" of diode_1185
> > It makes the code for the GUI routines simpler. If integer port vari
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Dr.
> Matthias Nagorni
> Sent: 13 May 2002 10:53
> To: [EMAIL PROTECTED]
> Subject: [linux-audio-dev] A new audio plugin API ?
[...]
> So I would expect that if you can us
On Mon, May 13, 2002 at 07:32:38 +0200, Dr. Matthias Nagorni wrote:
> On Mon, 13 May 2002, Steve Harris wrote:
>
> > > 6) Optional string array for integer ports (e.g. waveform: sine, saw, ...)
> > good idea, but not just for integer ports...
> For which ports else ? Toggles ?
Well, yes, I was j
On Mon, 13 May 2002, Steve Harris wrote:
> > 6) Optional string array for integer ports (e.g. waveform: sine, saw, ...)
> good idea, but not just for integer ports...
For which ports else ? Toggles ?
> > 7) Type of integer port int not float
> Don't think it helps much, in some cases there is a
On Mon, May 13, 2002 at 03:49:28 +0100, Steve Harris wrote:
>(late CV was 1v per octave, with 1v=440 Hz
> IIRC, so maybe 1.0f per octave, 1.0f=440Hz is good).
This is obviously not true, as 0v would be 220Hz, which is not right, but
you get the gist...
1v/1.0f per oc
On Mon, May 13, 2002 at 11:52:35 +0200, Dr. Matthias Nagorni wrote:
> Now the wishlist:
NB I regard these as proposals for a hypothetical new plugin format, with
a similar design to ladsap, other than adding defualts I dont think its
advidible/neccesary to extend LADSPA, it would be good to keep
Hi,
The importance of a widely-accepted audio plugin interface is reflected in
the fact that the subject of LADSPA extension is quite frequently
discussed on this list. After having implemented two hosts for LADSPA, I
would like to present my wishlist for LADSPA extension (or better a new audio
p
11 matches
Mail list logo