Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!mcnc!uvaarpa!murdoch!vivaldi.acc.virginia.edu!pmy
From: pmy@vivaldi.acc.virginia.edu (Pete Yadlowsky)
Newsgroups: comp.music
Subject: Re: computer music software for the next
Keywords: music, software, free
Message-ID: <1990Oct6.055545.12472@murdoch.acc.Virginia.EDU>
Date: 6 Oct 90 05:55:45 GMT
References: <84456@tut.cis.ohio-state.edu> <13007@sdcc6.ucsd.edu>
Sender: news@murdoch.acc.Virginia.EDU
Reply-To: pmy@vivaldi.acc.virginia.edu (Pete Yadlowsky)
Organization: University of Virginia, Charlottesville
Lines: 40

In article <13007@sdcc6.ucsd.edu> cpenrose@sdcc13.ucsd.edu (Christopher Penrose) writes:

>csound software (mit)
>ftp access!
>free!
>ems.ai.mit.edu (anonymous)

>This is the standard UNIX distribution of csound.  I actually prefer
>this version as Pete's requires elaborate work directories that I find
>difficult to manage.

But you're not supposed to manage them...the front-end takes care of all
that.

>Csound is extremely useful and quick to code
>with a little experience.  And it is free.

>NeXT (C)sound, LPC 
>ftp access!
>free!
>uvaarpa.acc.virginia.edu (anonymous)
>pmy@uvaarpa.acc.virginia.edu

Actually, pmy@virginia.edu is better.

>Pete has written some NeXTstep interfaces to csound and princeton's
>LPC routines.  I prefer the standard shell interface to csound;

Could you elaborate on this a bit? I'm coming out with a new release
pretty soon, so I'm interested in any suggestions you (or anyone)
may have. Honestly, I can't imagine why one might prefer the shell
interface.

Thanks for the plug, BTW.

--
Peter M. Yadlowsky		| "You know - when I talk to people, I try to
Academic Computing Center	|  look more intelligent than I actually am.
University of Virginia		|  Seems to work."
pmy@Virginia.EDU		|			- LA