Michael Rempel wrote:

> Csound5 has removed the logging feature, so you can not use -O to make a
> file to see what happened either.

This could easily be restored.
-- 
Send bugs reports to this list.
To unsubscribe, send email to csound-unsubscribe@lists.bath.ac.uk

This is obvious to some, but useful.

I have been working on a set of UDOs lately. The problem with UDOs in
windows is they dont compile in Csound_AV. AV is very convenient because the
output log is visible on the screen durring and after compile/play. When a
command line version is executed from inside the CSound Editor, the console
screen flashes, but does not stay readable. This is especially true if you
are compiling to disk.

Csound5 has removed the logging feature, so you can not use -O to make a
file to see what happened either.

Note to csound developers, the -O and --logfile command line options
probably should only throw warnings, and not fail completely. Compatability
issue.

I was using a batch file for this, and then realized that the presets in
Csound Editor can call a batch file themselves.

So I made a batch file that contains

c:\csound5\csound.exe %1 %2 %3 %4 %5 %6 %7 %8 %9 %10
pause

and put it on the command line in place of %Csound% in the Csound Editor and
got the magic I was looking for. All the compile output on the console
screen, waiting for me to press a key to continue.

Note that putting a pause in a batch file for the second action in Csound
Editor does not do the trick. A seperate cmd window is opened. All you see
is the pause, not the csound output. At least in Win2k it works that way.
Pause is not available outside batchfile space in windows. Some of you may
need more than 10 parameters. :-)

Enjoy,

Michael Rempel

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

No need on my account, as you can see. 

-----Original Message-----
From: Istvan Varga [mailto:istvan_v@fibermail.hu]
Sent: Wednesday, September 21, 2005 3:39 AM
To: csound@lists.bath.ac.uk
Subject: Re: [Csnd] Windows Tip: for Csound Editor users


Michael Rempel wrote:

> Csound5 has removed the logging feature, so you can not use -O to make a
> file to see what happened either.

This could easily be restored.
-- 
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

On Wed, 21 Sep 2005, Michael Rempel wrote:
>
> Csound5 has removed the logging feature, so you can not use -O to make a
> file to see what happened either.
What about redirecting the output to a log file?

csound parameter parameter parameter > logfile

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

What?  Why was this removed?

I consider the logging feature to be essential!  Please do restore it.

Thanks. :)

Anthony Kozar
anthonykozar@sbcglobal.net
http://akozar.spymac.net/


Istvan Varga wrote on 9/21/05 6:38 AM:

> Michael Rempel wrote:
> 
>> Csound5 has removed the logging feature, so you can not use -O to make a
>> file to see what happened either.
> 
> This could easily be restored.

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

Anthony Kozar wrote:

> What?  Why was this removed?

It was probably related to the replacement of dribble_printf, err_printf,
and whatever was used in Csound 4 with the API functions. The standard
command line frontend could easily implement logging by replacing the
default message callback; this would need some command line parsing done
in the frontend, though, which is ugly. A more complete solution of having
the logging implemented in libcsound itself is actually not as easy as I
thought, because many messages are already printed by the time the command
line flags are parsed; so, either those messages will be lost, or even
more ugly hacks are needed to save the initial messages to a (dynamically
increased) temporary buffer first which will eventually be freed.
-- 
Send bugs reports to this list.
To unsubscribe, send email to csound-unsubscribe@lists.bath.ac.uk

Istvan Varga wrote on 9/22/05 4:27 AM:

> The standard
> command line frontend could easily implement logging by replacing the
> default message callback;

It is a good option for other hosts to be able to do this; but I still think
that having the logging feature in Csound itself is needed.

> A more complete solution of having
> the logging implemented in libcsound itself is actually not as easy as I
> thought, because many messages are already printed by the time the command
> line flags are parsed; so, either those messages will be lost, or even
> more ugly hacks are needed to save the initial messages to a (dynamically
> increased) temporary buffer first which will eventually be freed.

This was the case under Csound 4 too.  The first few messages were not
logged to a file.  It was not a problem for Cs4 as far as I was concerned.
I suppose there may be a lot more messages being output by Cs5 though before
reading the flags.

Anthony Kozar
anthonykozar AT sbcglobal DOT net
http://akozar.spymac.net/

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

Well, for now, there is logging implemented in the command line frontend.
-- 
Send bugs reports to this list.
To unsubscribe, send email to csound-unsubscribe@lists.bath.ac.uk