On Mon, Jun 2, 2008 at 7:02 AM, Michael Gogins wrote: > In your example of Vercoe's tutorial, most Csound users would understand > that the term "command" implies a Unix shell command, and that it would be > typed at the "shell prompt." The counterpart on Windows is called the > "console" for reasons that escape us. Maybe it's there to console former Unix users. ;) > I think it would be wise to focus on what Csound can do, for "newbies," that > they can't get done with other software, or can't get done as easily or as > well. And I don't think straightforward synthesis is it, although I Good point, there has to be some motivation for people to be willing to learn something different. > personally feel that there are a lot of Csound patches that give the best > commercial synthesizers a run for their money. I think, rather, that score > generation and the time/frequency analysis/resynthesis stuff that you can do > with the pvs opcodes are definitely places where you just get lost with > commercial and popular software. Another advantage might be the ability to > build your own physical modeling instruments, a la Tassman. Csound's command of granular synthesis also has yet to be approached by commercial software. The rapidly increasing options for interfacing Csound with other programs/networks/languages, thanks to you and others, should be of great interest to newcomers, who may wish to use Csound for some aspects and more familiar interfaces for others. -Chuckk -- http://www.badmuthahubbard.com