Yep, pd and suchlike excellent environments for putting together networks.
However, other applications don't import pd patches or instruments and there
is no way to share softsynths on Linux. Hence the current API debate.
What I'd like to see is a simple XML format for LADSPA plugin networks and
instruments. PNet is a bit of a red herring - it's value would be as a tiny
testbed host and a source of reference code to stuff into other hosts as
needed.
Admittedly LADSPA's current lack of a string data type would make coding of
sample-based instruments difficult...
--Richard
-----Original Message-----
From: linux-audio-dev-admin(a)music.columbia.edu
[mailto:linux-audio-dev-admin@music.columbia.edu]On Behalf Of Frank
Barknecht
Sent: 10 December 2002 22:51
To: linux-audio-dev(a)music.columbia.edu
Subject: Re: [linux-audio-dev] LADSPA and Softsynths
Hi,
Richard Furse hat gesagt: // Richard Furse wrote:
Just an observation about an alternative path on
softsynths: a LADSPA
plugin
or network can be used easily enough as a softsynth
using control-voltage
(CV) approaches (a few already exist). It's just a matter of agreeing the
conventions - implementation is trivial.
I've been meaning to finish writing PNet for a while (I've mentioned it a
few times) - essentially an environment where LADSPA plugins are strung
together to form a "patch" and are wired up to "standard" CV controls
for
pitch, velocity, MIDI CC etc.
I wonder, how this differs from the approach in Pure Data (Pd). The
[plugin~] Pd-external can load LADSPA plugins and connects them to the
rest of the signal world. I think, Alsa Modular Synth or SSM do something
similar, but I didn't use those for a long time. Or do I miss the
point and PNet is something to build an object file to load inside
another application? A LADSPA-Meta-plugin?
ciao
--
Frank Barknecht _ ______footils.org__