| I have mentioned this. Actually, I have been exploring several ways to
synthesize sound for my algorithmic composition system Silence: Csound,
SAOL, and a pure Java synthesizer. I have now committed to SAOL unless,
after some experience, it doesn't prove as useful as Csound. I am setting
aside my adaptions to Csound (AXCSound) and the pure Java synthesizer in
favor of SAOL.
Instead of producing a Csound VST plugin, then, I will be producing a SAOL
VST plugin... that is, after I get SAOL working in the first place. At the
present time, I am using John Lazzaro's sfront SAOL to C compiler, then
shelling out to run a C compiler. I am in the midst of creating a Java
interface for SAOL called Noise. When that is done, I will attempt the VST
thing.
I would encourage Csound developers to continue the line of work that I had
begun with AXCSound, which is in the public domain and available for
adaptation. I found that modifying Csound to be able to work in the context
of a plugin was not a trivial task. I did add realtime line inputs and
realtime JavaSound MIDI input, and I had designed but not implemented
JavaSound audio input. This looked like it was going to be moderately
difficult, because the VST plugins get sound pulled out of them, but Csound
wants to push sound out of itself.
It would also be highly desirable to make a multiply instantiatable object
out of Csound (currently, there can only be one Csound orchestra running in
a process). If anyone wants the sources of my development work, beyond what
is available in the zip file on my Web page, please let me know.
Why am I changing from Csound to SAOL? I hope and anticipate that various
implementations of SAOL, ranging from sfront through runtime compilers to
embedded systems on chips in sound cards, will become available. This should
mean that a measure of stability and good implementation comes to software
synthesis. Even if I quit using sfront and started using SoundWiz chips (to
use an imaginary sound card manufacturer as an example) all my SAOL
orchestras should continue to work as before. With SAOL, instead of adding
opcodes written in C to the engine, one adds user-defined opcodes written in
SAOL to one's orchestras, because SAOL is a complete procedural language
that happens to be specialized for sound synthesis.
-----Original Message-----
From: owner-csound-outgoing@maths.ex.ac.uk
[mailto:owner-csound-outgoing@maths.ex.ac.uk]On Behalf Of anechoic audio
engine
Sent: Saturday, September 11, 1999 12:39 PM
To: csound@maths.ex.ac.uk
Subject: VST plugin
I've been in non-lurking mode for some time now but the other day someone
mentioned a Csound VST plugin that is supposedly in the works...can anyone
send me more info or a URL about this?
thanks!
KIM
__________________________
kim.cascone
sound.designer...composer
kim@anechoicmedia.com
http://www.anechoicmedia.com
full length:: blueCube( ) (Rastermusic)
comp track:: nb2e_Vortex.aiff (Mille Plateaux)
comp track:: vortexShedding (Caipirinha Music)
full length:: cathodeFlower (Ritornell/Mille Plateaux)
"the smooth always posseses a greater power of deterritorialization than
the striated."
- Deleuze & Guattari
|