Re: [linux-audio-dev] Synth APIs, MONKEY

2002-12-12 Thread David Olofson
On Thursday 12 December 2002 14.12, Sami P Perttu wrote: [...] > In XAP, then, things like filter cutoff and Q would be controls and > respond to "set" and "ramp" events. Conversions or possibly plugins > that convert between audio rate signals and events will still be > needed, I think, but they a

Re: [linux-audio-dev] Synth APIs, MONKEY

2002-12-12 Thread Sami P Perttu
On Wed, 11 Dec 2002, David Olofson wrote: > An event system with "set" and "ramp" events can do the same thing - > although it does get pretty inefficient when you want to transfer > actuall audio rate data! ;-) Yes. It seems that audio architecture design is dominated by the audio versus control

Re: [linux-audio-dev] Synth APIs, MONKEY

2002-12-11 Thread David Olofson
On Wednesday 11 December 2002 20.25, Sami P Perttu wrote: [...] > > That sounds a lot like a specialized event system, actually. You > > have structured data - and that is essentially what events are > > about. > > Hmm, that's one way of looking at it. I had thought of the subblock > aspect as some

Re: [linux-audio-dev] Synth APIs, MONKEY

2002-12-11 Thread Sami P Perttu
On Wed, 11 Dec 2002, David Olofson wrote: > > Well, in MONKEY I have done away with separate audio and control > > signals - there is only one type of signal. However, each block of > > a signal may consist of an arbitrary number of consecutive > > subblocks. There are three types of subblocks: co

Re: [linux-audio-dev] Synth APIs, MONKEY

2002-12-11 Thread David Olofson
On Wednesday 11 December 2002 13.14, Sami P Perttu wrote: [...] > > This sounds interesting and very flexible - but what's the cost? > > How many voices of "real" sounds can you play at once on your > > average PC? (Say, a 2 GHz P4 or someting.) Is it possible to > > start a sound with sample accur

[linux-audio-dev] Synth APIs, MONKEY

2002-12-11 Thread Sami P Perttu
> > 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 and then destroy it? That is what > > events are in my