Previous: Database Configuration Files, Up: Configuration Files
This file don't exist in a fixed location. It specifies groups or combinations of instruments and techniques (“orchestras”) for sporch and libsporch.so. It is flexible enough to indicate alternate choices between instruments and techniques as well as to control selections from the ensemble as a whole or groups within the ensemble.
A top level combination or ensemble of instruments in this configuration file is called an orchestra.
An orchestra contains a hierarchical organization of sections and instruments. The orch
definition must appear at the top level of the file while
sec
and inst
definitions are nested inside of it.
orch
orch
keyword is followed by a pair of braces (‘{ }’) that must contain a name for the orchestra and
either sec
or inst
definitions.
name
min
orch
/sec
/inst
and not to any subsections or instruments nested inside of it.
max
orch
/sec
/inst
and not to any subsections or instruments nested inside of it.
Not setting this value implies a limitless number of matches.
cons
orch
definition.
If no collections or models are explicitly specified with colls
, then libsporch.so chooses the best ones based on
the user pref
setting (in the conf files) and otherwise the “smoothness” of spectra from pitch to pitch
and dynamic level to dynamic level.
colls
sec
sec
keyword is followed by
a pair of braces as in the orch
definition. Sections can optionally have names and
must contain more nested sec
or inst
definitions.
name
min
max
colls
inst
orch
or sec
definition.
The inst
keyword is followed by a pair of braces containing a mandatory instrument id (referring to the instrument stored in the database)
and an technique id.
name
inst
tech
inst
)
min
max
colls
models
cons
is set to ‘inst’, then one model is chosen for all pitches and dynamic levels.
Otherwise, analyses from the specified models may be mixed together (according to whatever selections provide the smoothest connection
from pitch to pitch and dynamic level to dynamic level).