Editing Csound (section)

== Csound 6 ==
The development of Csound 6 was led by [[John Fitch (computer scientist)|John Fitch]], Steven Yi and [[Victor Lazzarini]]. After its features were hashed out at the Csound Conference held in 2011 in Hanover, Csound 6 was released in July 2013 and made available on [[GitHub]].<ref>{{cite web|url=https://github.com/csound/csound|title=Csound |website=GitHub.com}}</ref> Csound 6 is also available for [[Android (operating system)|Android]]. The major new features of Csound 6 include:

* A [[GNU bison|bison]]/[[Flex lexical analyser|flex]] based [[Parsing|parser]] for the Csound language is now standard. It generates an [[abstract syntax tree]] that is accessible via the Csound API. The tree can then be [[Compiler|compiled]] to a Csound performance runtime using the API. Therefore, after the tree has been compiled, it can be manipulated by user code before compiling it to a Csound performance runtime. Alternatively, the user could create the entire abstract syntax tree from another language, then compile the tree to a Csound performance runtime.
* There is a new built-in multi-dimensional array type. Arrays can be passed to instruments and opcodes. Arithmetic may be performed directly on arrays.
* There is a new type system that enables user-defined types to be used in the Csound language.
* The orchestra can be re-compiled at any time, or individual instruments can be compiled at any time, during a running performance. This enables true "live coding" in Csound performances.
* The Csound API has been rationalized and simplified.
* Csound can take advantage of any number of CPUs for concurrent processing during performance. This occurs without any changes to Csound code. This produces substantial speedups of most Csound processing. For example, a piece that renders in 100 seconds with 1 core should render in about 50 seconds with 4 cores.
* Csound can compile orchestras and scores directly from strings of text, enabling the use of Csound in environments where writing to the file system is not permitted.
* Score events such as notes can be scheduled to sample accurate times, even if synthesis is processed in blocks of samples.
* All opcodes that return a single value may be used as functions in the orchestra language.
* Audio analysis file formats can be byte-order independent.
* A single score statement can contain multiple string parameters.
* Most oscillator opcodes will use an internal sine function table if the table number is omitted.
* Command-line options can be set programmatically using the Csound API.
* Numerous duplicate areas of code within Csound have been rationalized.
* An Android app was built which provides user-defined graphical user interfaces and JavaScript-based algorithmic composition using HTML5.