Previously, Csound logged stuff arbitrarily to stderr or stdout. I believe that now, errors are printed to stderr (which enables turning off messages, -ostdout, and using stdout to pipe audio out of Csound). Therefore I think you need to redirect both stdout and stderr to the same file to do what you want. I think this will do that:

csound >csound.log 2>&1

Regards,
Mike

-----Original Message-----
From: David Akbari 
Sent: Sep 22, 2005 11:07 AM
To: csound@lists.bath.ac.uk
Subject: Re: [Csnd] Logging (-0) removed in Csound 5?


On Sep 22, 2005, at 10:14 AM, Michael Gogins wrote:

> It should always be possible to redirect stderr and/or stdout to a 
> file. This is a standard practice with many programs on all platforms.
>

You know, it's funny you mention that.

For example, if I try doing

[localhost:~] ls -a > list.txt

I get the directory contents in a text file, as expected. However if I 
do

[localhost:~/csoundpath] ./csound -z1 > cs_opcodes.txt

Csound5 (Sept 21 2005) outputs a blank text file with the opcode list 
to the console window.

Is this as expected? Ideally I would want the information to just go 
straight to the text file and not ever appear in the Terminal window. 
Of course it is no problem to copy / paste the output but it is one 
more potentially time saving step ...


-David

-- 
Send bugs reports to this list.
To unsubscribe, send email to csound-unsubscribe@lists.bath.ac.uk



-- 
Send bugs reports to this list.
To unsubscribe, send email to csound-unsubscribe@lists.bath.ac.uk