Is this CsoundVST behavior related to why, in Windows Csound5, .csd files
come back with the line numbers of error messages wrong? Or is the cause
some other factor?

Again, is there anything that can be done about this? It makes error
messages much less useful than they could be.

Art Hunkins

----- Original Message -----
From: 
To: 
Sent: Sunday, February 20, 2005 12:29 PM
Subject: [Cs-dev] Some questions about recent changes


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. This is because CsoundVST loads and edits .csd
files, but it does not perform them as .csd files; it performs them by
exporting the .orc and .sco file separately. The reason for this is that in
Python mode, CsoundVST generates the .sco file programmatically, using the
name given on the Csound command line, and it also still exports the .orc
file in the usual way.

So I changed the code back to permit .orc and .sco filenames in .csd files.
The .csd files now work both ways -- either with, or without, .orc and .sco
filenames.




-------------------------------------------------------
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

No, I don't think that has anything to do with it.  The numbering problem
has a simple cause: Csound does not actually use your .csd file during
performance, it uses a temporary .orc and .sco instead.

Fixing this should be fairly easy.  However, I think there is a similar
problem with including files, and that problem is likely considerably more
difficult to solve.

Anthony Kozar
anthony.kozar@utoledo.edu
http://akozar.spymac.net/


On 2/20/05 12:51 PM, Art Hunkins  etched in stone:

> Is this CsoundVST behavior related to why, in Windows Csound5, .csd files
> come back with the line numbers of error messages wrong? Or is the cause
> some other factor?
> 
> Again, is there anything that can be done about this? It makes error
> messages much less useful than they could be.



-------------------------------------------------------
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

> Fixing this should be fairly easy.  However, I think there is a similar
> problem with including files, and that problem is likely considerably more
> difficult to solve.

And once you start using big macros ...

A tip for error hunting massive ensembles. We would put flag macros in, 
which would at least flash across the screen to tell us where we were 
before crashes as the line numbers were totally irrelevant. Ie

#define We_got_here_of #0#
or
$We_loaded_this_macro_ok

that kind of thing.

Iain




-------------------------------------------------------
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