First, I don't see how this is not compatible with older versions. Running
the .csd without an .orc or .sco filename still works fine.

CsoundVST does not pass a .csd to Csound. It passes an .orc and .sco to
Csound. However, CsoundVST does load and edit .csd files, because it is
simpler to load one file rather than two files.

CsoundVST also loads and edits Python source code (.py files), in which
case CsoundVST may run its internal Python interpreter to programmatically
build a .csd file. Or the Python script may programmatically write a .sco
file directly, but still use a programmatically loaded .csd or .orc file
for its orchestra.

Of course CsoundVST is also used as a VST plugin, where the .csd, .orc, or
even Python file contains an orchestra but not, usually, any .sco at all.

In all these cases, it is simpler if the Csound command is the
old-fashioned kind that starts out with the name of the Csound command and
contains and .orc and .sco filename. 

For me, this has the additional advantage of preserving the .orc and .sco
files that are generated from a Python piece. 

In other words, with a programmatically generated piece, the piece is not
the .csd file, which does not exist except in memory, it is source code in
some other language. But keeping the generated and saved .orc and .sco
files documents the final form of the peice. Using the .csd file behavior
that deletes the temporary .orc and .sco files would defeat this purpose.

Many times I have been able to revive an older piece from the .orc and .sco
files when the script or other software I used to generate the piece is no
longer workable, so this serves a very valuable documenting function.

Other Csound API clients might face similar issues, and might similarly
benefit from the flexibility of being able to use an old style Csound
command line in a .csd file.




Original Message:
-----------------
From: Anthony Kozar anthony.kozar@utoledo.edu
Date: Sun, 20 Feb 2005 14:10:32 -0500
To: csound-devel@lists.sourceforge.net
Subject: Re: [Cs-dev] Some questions about recent changes


It seems like a bad idea to me to use the  in a way which is not
compatible with other versions of Csound.  Perhaps you should take a look at
what Matt has done in MacCsound.  He saves MacCsound-specific options
inbetween  and  tags.

The only reason I can think of to have orchname and scorename in a CSD would
be if there were no  or  tags and those files were
created beforehand, but you still pass the .csd as an argument to Csound.
Is this what you are doing?

Anthony

On 2/20/05 12:29 PM, gogins@pipeline.com  etched in
stone:

> I also noticed that option parsing was changed to disallow using .orc and
> .sco names in .csd and .csoundrc files.  However, this breaks some
behavior
> of CsoundVST, which depends on being able to include .orc and .sco
> filenames in .csd files.



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel

--------------------------------------------------------------------
mail2web - Check your email from the web at
http://mail2web.com/ .




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id396&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net