Windows Tip: for Csound Editor users

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:csound5csound.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

Leave a Comment.

This site uses Akismet to reduce spam. Learn how your comment data is processed.