Subject: [linux-audio-dev] LADSPA data types (Was: ... Quasimodo)
From: David Olofson (david_AT_gardena.net)
Date: la maalis 11 2000 - 21:05:01 EST
On Fri, 10 Mar 2000, Paul Barton-Davis wrote:
> Quasimodo. Its limitations at a deep level right now are just 2, as
> far as I am aware: it is *not* sample accurate (i.e. events such as
> incoming MIDI data do not result in changes to the sample stream with
> sample accuracy; its not about speed, since in Quasimodo they
> typically happen too fast (!), but about accuracy). secondly, you
> can't connect a control signal to an audio socket, because control
> signals are represented by scalar values and audio sockets by arrays.
Hmm... This finally turns some of my thoughts into an idea.
A LADSPA port can be either a control port or an audio port.
It has been discussed how to support multiple audio data types. (And
I still claim that this can be done without much init time complexity,
and without *any* change on the process time level. :-)
Now, what if "control" was a data type rather than a special kind of
port? That way, the control/audio distinction could be removed, and
instead automatically handled by the data type handling at init time.
(How did I come up with this? Well, I just thought "Why not hack
control <-> signal converter plugins and have some more fun?")
//David
.- M u C o S --------------------------------. .- David Olofson ------.
| A Free/Open Multimedia | | Audio Hacker |
| Plugin and Integration Standard | | Linux Advocate |
`------------> http://www.linuxdj.com/mucos -' | Open Source Advocate |
.- A u d i a l i t y ------------------------. | Singer |
| Rock Solid Low Latency Signal Processing | | Songwriter |
`---> http://www.angelfire.com/or/audiality -' `-> david_AT_linuxdj.com -'
This archive was generated by hypermail 2b28 : su maalis 12 2000 - 09:14:06 EST