29 Jul
2004
29 Jul
'04
10:52 p.m.
On Thursday 29 July 2004 06:26 pm, Dave Robillard wrote:
Hello LAU,
I'm designing a modular synth engine, and would like to get some input
on desired features/abilities to make sure it's designed in a way that
will make it the most flexible.
So, what features are important to you in a synth? What annoys you
about the current crop of linux synths?
Already planned (* = working right now):
* Low latency realtime operation via Jack
* 100% LADSPA plugins, not Yet Another Internal Plugin Format
- (DSSI and perhaps VST are being considered)
FWIW DSSI as a response to MusE softsynth handling API dependency QT is
fallacious. There is no dependency according to Werner Schweer. Just saying.
* Seperate engine and frontend(s), ALL communication
via OSC (Open Sound
Control)
The main GUI will be a modular a lot like AMS/SSM/etc. but there's no
reason it has to be, the engine can be used from the command line, in
programs/scripts (from any language that can talk OSC), hardcoded in
custom synths, etc. etc. This will allow, for example, algorithmic
composition in C without the limitations of MIDI and discrete notes.
The use of OSC means you can run the engine transparently over the
network (on 20 machines if you so please..)
Nice. I gotta look into OSC.
- Polyphonic, runtime selectable (in the works right
now)
- Multitimbral
* ALSA MIDI in will be through a seperate application, which will allow
binding of any MIDI controller to any param in the synth
- Sending OSC messages from module ports
* Sample accurate everything
- The main modular frontend will support LASH (formerly LADCCA), and
allow building of control panels ala galan
I'm very open to suggestions, that's why I started this thread.. let's
hear 'em
Cheers,
-DR-