2 Aug
2004
2 Aug
'04
10:38 a.m.
On Mon, 2004-08-02 at 02:09, ricktaylor(a)speakeasy.net wrote:
Sorry, I don't really know what you mean by any of this. Screenshots,
better explanation? The planned GUI will be something like ams, is that
similar to what you're thinking?
-----Original
Message-----
From: Dave Robillard [mailto:drobilla@connect.carleton.ca]
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?
[snip]
I'm writing this before I read the thread... you're getting
"untainted" ideas. :}
Snap in modules... Maybe a full screen version of Reactor that could scroll vertically
or horizontally... A visual means of patching back and forth... Maybe not as literal
as Moog Modular but clear and easy to read. A nice simple gui like Vokator. Possibly with screens
like Jahshaka/Blender so you could
page rather than scroll and still keep the screen uncluttered. {I hate clutter}.
I havn't used those apps but I'll scourge the net for screenshots..
Synthedit compatibility... The community there's
fairly large... There's much stuff already
written for the environment.
I'll look in to it.
If it were extensible through something simple like
lisp or ruby... Like emacs and snd... That would be cool.
Scripting is essential.
The engine is totally controlled by OSC messages, so if you can send OSC
messages from whatever language, you can control the synth. Basically
any front end is possible, scripting, graphical, etc.
VST is essential. ...LADSPA.
Personally not into proprietary plugins very much at all. I'm not
against the idea of VST support, I just don't care. I might get around
to it sometime.
OSC would be nice.
See above. 100% OSC
Csound compatibility through a module would be
cool... So you could read .orc and score files rather than just plugging in a step
sequencer {Tho' a step sequencer would be nice.}
OSC
PD compatibility would be nice.
OSC
A sampler module would be nice.
Planned, and pretty high on the priority list.
A timeline like the one in
http://openvip.sourceforge.net/ would rock... either to actually do video or to set up
samples.
Hmm.. that's sequencer stuff, not really in the domain of this prog.
Unless it's integrated with the below-mentioned "OSC sequencer".
hmmmm..
Automation would be nice
Actually I'm thinking about writing an 'OSC sequencer' to do
automation-like things. Not sure about the feasibility of that though.
Compatibility with existing languages/environments
like cm and OSW {which is osc compatible already} would be cool...
yet again OSC
PVM? That way you could stretch it across a cluster.
Mosix? Maybe peer2peer midi {Freshmeat}?
Eyesweb compatibility {should they ever happen to port it}?
aaaand yet again OSC. :)
FM? {See Lollapalooza} Additive functions? {Cube,
Cameleon}
Being a modular, methods of synthesis are the users problem, not mine.
:)
Thanks for the input.
-DR-