Re: [linux-audio-dev] Re: Synth APIs, pitch control

2002-12-13 Thread David Olofson
On Friday 13 December 2002 20.14, Sami P Perttu wrote: > On Fri, 13 Dec 2002, David Olofson wrote: > > On Friday 13 December 2002 15.51, Sami P Perttu wrote: > > [...] > > > > > Re: pull model, an alternative to supporting pull in XAP is to > > > just say that such plugins should act as hosts. > >

Re: [linux-audio-dev] Re: Synth APIs, pitch control

2002-12-13 Thread Sami P Perttu
On Fri, 13 Dec 2002, David Olofson wrote: > On Friday 13 December 2002 15.51, Sami P Perttu wrote: > [...] > > Re: pull model, an alternative to supporting pull in XAP is to just > > say that such plugins should act as hosts. > > That's not much better than not having a plugin API at all. To > sup

Re: [linux-audio-dev] Re: Synth APIs, pitch control

2002-12-13 Thread David Olofson
On Friday 13 December 2002 15.51, Sami P Perttu wrote: [...] > Re: pull model, an alternative to supporting pull in XAP is to just > say that such plugins should act as hosts. That's not much better than not having a plugin API at all. To support direct-from-disk sampling, the host would have to

Re: [linux-audio-dev] Re: Synth APIs, pitch control

2002-12-13 Thread Sami P Perttu
On Fri, 13 Dec 2002, David Olofson wrote: > Well, who's stopping you from proposing a Sequencer DataBase API, or > whatever is needed for this? We real time guys will need that as > well, for sequencing and editing, so it's not like we don't care > about it; we're just trying to solve *our* most i

Re: [linux-audio-dev] Re: Synth APIs, pitch control

2002-12-13 Thread David Olofson
On Friday 13 December 2002 10.42, Sami P Perttu wrote: > On 12 Dec 2002, nick wrote: > > > > http://amsynthe.sourceforge.net/amp_plugin.h which i am still > > > > toying > > > > My whole idea with it was to make it as simple as possible. > > Bearing in mind that many people have learned MIDI alread

Re: [linux-audio-dev] Re: Synth APIs, pitch control

2002-12-13 Thread Steve Harris
On Fri, Dec 13, 2002 at 11:42:39AM +0200, Sami P Perttu wrote: > Even as a control language MIDI has a lot of shortcomings that it's time > to get rid of: note pitch values, low precision most everywhere. We might > as well design a format ourselves. XAP can probably accommodate simple > "musical"

Re: [linux-audio-dev] Re: Synth APIs, pitch control

2002-12-13 Thread Sami P Perttu
On 12 Dec 2002, nick wrote: > > > http://amsynthe.sourceforge.net/amp_plugin.h which i am still toying > > > My whole idea with it was to make it as simple as possible. Bearing in > mind that many people have learned MIDI already, it makes sense to me to > use it. Another cool thing is that you co

Re: [linux-audio-dev] Re: Synth APIs, pitch control

2002-12-12 Thread David Olofson
On Thursday 12 December 2002 21.56, nick wrote: [...] > My whole idea with it was to make it as simple as possible. Bearing > in mind that many people have learned MIDI already, it makes sense > to me to use it. Another cool thing is that you could in theory > write a sequencer as a plugin for it -

Re: [linux-audio-dev] Re: Synth APIs, pitch control

2002-12-12 Thread nick
On Wed, 2002-12-11 at 11:38, Sami P Perttu wrote: > > > a softstudio; it's pretty far already and > > > the first public release is scheduled Q1/2003. > > > > for Linux, obviously? ;-) > > Yes. Linux, GPL. MONKEY is about 30.000 lines of C++ at the moment. I > still have to make a final architectu

Re: [linux-audio-dev] Re: Synth APIs, pitch control

2002-12-11 Thread David Olofson
On Wednesday 11 December 2002 19.32, Tim Hockin wrote: > > This is *exactly* why I'm proposing the use of a structured text > > file that matches the structure of the plugin's "exported" names. > > The *structure* is what you go by; not the actual words. A host > > would not even have to ask the pl

Re: [linux-audio-dev] Re: Synth APIs, pitch control

2002-12-11 Thread Tim Hockin
> This is *exactly* why I'm proposing the use of a structured text file > that matches the structure of the plugin's "exported" names. The > *structure* is what you go by; not the actual words. A host would not > even have to ask the plugin for the english names, but just look up > the correspo

Re: [linux-audio-dev] Re: Synth APIs, pitch control

2002-12-11 Thread David Olofson
On Wednesday 11 December 2002 17.02, Sebastien Metrot wrote: > This doesn't work most of the time because many names can have > multiple meanings and vice versa. This is *exactly* why I'm proposing the use of a structured text file that matches the structure of the plugin's "exported" names. The

Re: [linux-audio-dev] Re: Synth APIs, pitch control

2002-12-11 Thread Steve Harris
On Wed, Dec 11, 2002 at 04:53:40 +0100, David Olofson wrote: > That's something we might want to consider. Indeed, building names > into binaries means we'll actually need one binary for each language > (uurgh! reminds me of how Windoze "handles" languages...), but I'm > not sure external files

Re: [linux-audio-dev] Re: Synth APIs, pitch control

2002-12-11 Thread Sebastien Metrot
t; <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, 11 December, 2002 16:53 Subject: Re: [linux-audio-dev] Re: Synth APIs, pitch control > On Wednesday 11 December 2002 12.38, Sami P Perttu wrote: > [...] > > I shall have to add something like this to MONKEY. Ri

Re: [linux-audio-dev] Re: Synth APIs, pitch control

2002-12-11 Thread David Olofson
On Wednesday 11 December 2002 12.38, Sami P Perttu wrote: [...] > I shall have to add something like this to MONKEY. Right now it > supports LADSPA via a wrapper - the native API is pretty complex - > although creating a nice GUI based on just information in a LADSPA > .so is not possible, mainly d

[linux-audio-dev] Re: Synth APIs, pitch control

2002-12-11 Thread Sami P Perttu
> > a softstudio; it's pretty far already and > > the first public release is scheduled Q1/2003. > > for Linux, obviously? ;-) Yes. Linux, GPL. MONKEY is about 30.000 lines of C++ at the moment. I still have to make a final architecture revision based on some issues reading this list has evoked, a