This is a snapshot of CSOUND, currently running at the MIT MediaLab
on DEC-RISC machines (under Ultrix 4.2), on SGI Indigo's (under 4.1 OS),
on SUN's (under 4.1 OS), on HP 700's under SR 9.01, and on Macintosh's
under THINK_C's Lightspeed C 5.0.
It is also known to run on NeXTs, and probably on many others.
If you plan to run on a Unix system, then these sources are what you need.
If you plan to run on the Mac, you should ftp the .hqx versions of same.

All system differences are controlled by the top-level 'makefile'.  By editing
this makefile you can include X11 windows software, define the soundfile
system you are addressing, and include certain device-dependent I/O drivers.

The makefile can also control the speed of audio processing: electing
single precision floats will double your speed with no loss in fidelity;
even greater improvements will result from any hardware accelerators present.
Check your hardware and software options carefully while editing this makefile.

The top makefile requires you to specify the libraries which will receive your
executables on successful installation.  Once makefile is suitably modified,
installation requires just five commands from within the top directory:
		make all
		make install
		make manpp
		make clean

If you experience difficulty, the first 'make all' can be done in separate
stages:
	make csound	;the top-level csound compilation
	make anals	;subdir of standalone analysis progs (adsyn, lpc, pvoc)
	make utils1	;subdir of standalone score decoding, sort & extract
	make utils2	;subdir of file managing programs (sndinfo, scale)

If you get only as far as 'make csound' you can immediately start using Csound
since you have a COMPLETE EXECUTABLE.  This includes a -U (sound Utility)
option for generating the sound analysis control files suitable for ADSYN, LPC
and PVOC audio reconstruction (see the new Manual).  The Csound executable
also includes the SCOT, CSCORE, SCSORT, and EXTRACT score manipulating 
programs, which are invoked through other flags in the Csound command line.
The 'make anals,' 'utils1' and 'utils2' simply create stand-alone versions
of the above analysis and score programs, so you can run them in less space.

Problematic routines can be bypassed by commenting out the offending lines in
the lower 'makef' files.   NO OTHER FILES SHOULD BE MODIFIED AT INSTALLATION.
Finally, use 'make clean' to remove old intermediate files & conserve storage.

Sound is written to a file in a predefined Sound File Directory, declared by
setting an environment variable SFDIR (eg. 'setenv SFDIR /usr/sound/logname').
You can read/write any of 6 Soundfile formats:   8-bit char, 8-bit a-law,
8-bit u-law, 16-bit short ints, 32-bit long ints, or 32-bit floats;  two of
these (16-bit int, 32-bit int) are also read/writeable as AIFF or WAVE files.
If you install with SFIRCAM defined, soundfiles will have a 1024-byte header.
Installing with SFSUN41 defined enables use of SUN 4.1 multi-media conventions.
Since sounddisk drivers, RECORD and PLAY commands are often hardware dependent,
this package recognizes only some of these.  If you have a VAX and Digital
Sound Corp DAC's, you should import the IRCAM sound-file system and their
play command.  If you have a DECstation and the LoFi board, you can should
install with -DDEC and invoke DECaudio and DECplay.
If you have an SGI with audio board, install with -DSGI and invoke SGIplay.  
A SUN installation can read/write u-law soundfiles by invoking dac/adc in the
command line, or can write other formats using the 4.1 library.

I have made a small header optional on all control files for LPC and PVOC,
so that srate, npoles, etc. can be automatic (see the lpc.h file).
Csound will read the header, then step over it no matter how long it is.
The idea is to document your lp files by expanding the text in the header.
See the 'man' pages on this topic.  The directory 'analfils' contains
sample files for adsyn, lp and pvoc. See the README in that directory, and
how to set the environment variable SADIR.

The directories 'scorfils' and 'morefils' contain orchestras/scores of musical
examples, included for your initial assurance.  Some of these are transcriptions
of traditional pieces, likely to run in realtime if your machine is fast enough.
Others are original scores by expert users (James Dashow, Jon Nelson,
Richard Boulanger); usual copyrights apply.
The directory 'midifils' contains the beginning of a MIDI performance direction,
including a Beethoven Pastoral transcription; see the README in that directory.
The directory 'testfils' contains smaller orchestras/scores of tests I've made
in passing.  The directory 'cscofils' contains some CSCORE score-manipulating
programs; the default version is also in the top directory.
You might want to check all these files against the manual for syntax and form;
the task of creating bigger orchestras and better scores is left to you.

The Csound Users' Manual is maintained as a Microsoft Word document,
available over ftp in either Word or PostScript format.  Download either.
The manual is very detailed (it's a Reference tool, not a Primer), with the goal
of giving an accurate account of each facet of the Score and Orchestra languages.
This new version, however, does include tuturials and examples as Appendices.

I am maintaining a MAILING LIST for Csound users.  This is currently not a
full-fledged Bulletin Board (which I don't have time to maintain), but is the
list I use for announcements of new releases.  To have your name added-to or
removed-from this list, send mail to:
			csound-request@media-lab.media.mit.edu
Send bug reports to:		csound@media-lab.media.mit.edu

								Barry Vercoe
								February, 1994
