On Tuesday 10 December 2002 11.38, nick wrote:
[...]
> For a complete contrast, please look over
> http://amsynthe.sourceforge.net/amp_plugin.h which i am still
> toying with as a(nother) plugin api suitable for synths. I was
> hoping to wait until i had a nicely written host and plugins to
> demon
On Tuesday 10 December 2002 09.38, Sami P Perttu wrote:
> Hi everybody. I've been reading this list for a week. Thought I'd
> "pitch" in here because I'm also writing a softstudio; it's pretty
> far already and the first public release is scheduled Q1/2003.
Sounds interesting! :-)
> First, I don
>The argument against c++ has been a constantly changing ABI, but with
>the release of GCC 3.2 it finally looks like G++ will have a stable API.
>time will tell i guess.
i have my doubts about this. with the flexibility that c++
compile-time flags provide, i'm not sure one can ever talk about "a
s
On Tue, Dec 10, 2002 at 10:38:52 +0200, Sami P Perttu wrote:
> First, I don't understand why you want to design a "synth API". If you
> want to play a note, why not instantiate a DSP network that does the job,
> connect it to the main network (where system audio outs reside), run it
> for a while a
On Tue, 2002-12-10 at 08:38, Sami P Perttu wrote:
> Hi everybody. I've been reading this list for a week. Thought I'd "pitch"
> in here because I'm also writing a softstudio; it's pretty far already and
> the first public release is scheduled Q1/2003.
for Linux, obviously? ;-)
> First, I don't un
Hi everybody. I've been reading this list for a week. Thought I'd "pitch"
in here because I'm also writing a softstudio; it's pretty far already and
the first public release is scheduled Q1/2003.
First, I don't understand why you want to design a "synth API". If you
want to play a note, why not in
