Message written at 19 Feb 1999 10:41:46 +0000
--- Copy of mail to fmtk@sfc.keio.ac.jp ---
In-reply-to: <199902181814.DAA10878@zz039.sfc.keio.ac.jp> (message from
	Fumitake Ohnaka on Fri, 19 Feb 1999 03:14:28 +0900)
References:  <199902181814.DAA10878@zz039.sfc.keio.ac.jp>

On some implementations the code to open stdout for audio does not
exist.  In particular the Macintosh machioen does not support it as
there is not really a stdin/stdout system on that machine.  That
message (in my sources) can only come if compiled with macintosh or
SYMANTEX macros are defined.
  There is a "gotya" in sending audio to stdout by teh way; if you use
WAV or AIFF formats it needs to seek back to teh start for the header,
and so it fails.

The meaning of "The input or output file in -i and -o can start with a
| to indicate a process which is started to create or process audio
files.  This works on Windows and Unix, but not (yet) DOS." is almost
exactly what it says.  I can write
        csound xx.csd -h -o "|mypostprocess"
to create a sound and pass it via a pipe to a process called
mypostprocess.  It works on Unix easily, and on Windows badly (as
pipes are badly designed there).  Does not work on DOS for rather
boring reasons to do with my DOS compiler (despite teh documentation
there are no pipes) and on a Mac I woudl assume you were in trouble
unless matt or someone did some serious coding.

The #if for stdout rules it out for macintosh, Windows, DOS and Linux
(as that seems to be what the linux developers wanted).  It can be
revised (I think the __unix is totally wrong...)