[sdiy] OT ? Favorite Software Synths

[Mike]

> not to mention, these programs use the analog functional block
> paradigm for sound creation, unlike other shit like PD or Max/MSP.
>
I love analog, I built my first in 1973. It's a very natural and easy way to
work and generate sounds. It's a very good 'rapid prototyping' system for
sound too.

It's also quite limited.

I've never yet found any limts, that weren't my own, in CSound. Trouble is,
it requires time and skull sweat to learn and use. For what it is good at,
Max is peerless, I'm still trying to get time to set up a machine for Pd.

(Those who have a little patince but don't want to set up a Linux box can
try this: http://puredyne.goto10.org/  it's a whole Linux based sound lab,
including Pd on a bootable CD, store data on a USB key: It's also quite new
and has sparse docs so far)

We all use the tools we like, just because you can't get your head around
Milller Puckettes work,  doesn't make it 'shit'. By dissing something that
doesn't suit your way of working, all you're doing is making yourself look
like a  mental lightweight.

And for my 10 cents worth, Synthedit is OK, and a very good package for
producing your own VSTs. For me, I can write CSoundVST . . . .  if I wanted
VST's,

If we were comparing tools, Synthedit is like having a conventional lathe or
miller; you can just get some materail out and start work. Max/Pd, and
CSound are more like CNC machines. You can make far more complex things, but
you need to sit down and design them first. With a real synth you can
'bend', try  things like plugging audio into control input, you can vamp and
improvise, try that in one of CSound and you've got pages of syntax errors
or your computer music system acts like a $1000 crackle box. Horses for
courses, tools for the job. Try telling  the head of toolroom his  CNC is
'shit' because it won't do a job that's best done with skilled hands and a
file. . . . .

||\/||ike