Recherche Google
OMChroma User ManualGetting started > Relationship with the Csound .orc and .sco files
page précédentepage suivante

Relationship with the Csound .orc and .sco files

Tutorial Getting Started 10 - Relationship with the Csound .orc and .sco files I

Csound divides the process of sound generation in two files: the orchestra file (ending with ".orc") and the score file (ending with ".sco", see the Csound chapter). However, in OpenMusic there is no clear separation between the two files; all the sound process lies within the patch. The example below systematizes the data flow and the relationship with the Csound .orc and .sco files.

This example displays a simple way to convert a Csound score to be used by the OMChroma add-1 class. All the given data are in the TextFile box and OpenMusic deals only with arranging them according to the needs of the matrix.

Note: OMChroma doesn't need the number of instrument statement (the first data of the each line), as it is automatically computed.

Open the corresponding ".orc" and ".sco" files (in the outfiles folder) to take a look at the Csound data generated by OMChroma.

Tutorial Getting Started 11 - Relationship with the Csound .orc and .sco files II

This example is quite developed and all the data are randomly generated by OpenMusic. With respect to the previous example, OpenMusic is used here for what it actually is.

The result of the previous tutorial could be simply obtained in Csound in the traditional way (two text-files). The result of this would be much more difficult to realize directly in Csound.

events

numbers of i-statments (lines) of the score, i.e., how many frequencies are wished

edel

entry delays' range in seconds

durs

durations in seconds

freq

frequency range in midicents

aenv x and y

Cartesian coordinates of the amplitude envelope

aenv stages

stages of the amplitude envelope

aenv exp

exponential factor of the y axis

page précédentepage suivante
A propos...Réalisé avec Scenari