----- Original Message ----- 
From: "Mike Coleman" 
To: "Developer discussions" 
Sent: Thursday, September 13, 2007 12:35 AM
Subject: Re: [Cs-dev] Engine Changes,or Csound 6 (was Re: [Csnd] feature 
request: multiple strings in"i"statements)


> On 9/12/07, Victor Lazzarini  wrote:
>> Orchestras are needed and we see them everywhere (PD patches,
>> SC3 synths, etc.). Now, as far as scores are concerned, Csound 5
>> does not require them: you can use MIDI, OSC, Python, Tcl or Lisp
>> scripting, FLTK, etc to run Csound. Scores however are sometimes
>> handy, and are needed for backwards compatibility.
>
> My impression was that, for Python at least, the existing Python score
> interface would generate an actual score file that would then be read
> by cscore, rather than interfacing at a lower level.  Did I miss
> something?
>
> I don't really see this approach as invalid, necessarily--though it
> isn't useful if you want your Python code to be able to react to
> real-time events.  The primary problem is that it limits you to the
> SCO language, which leaves you with the portamento problem.

Python can send real-time events to an embedded instance of Csound, and it 
can write and read global variables in real time as well.



-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net