The following are simple examples explaining the design of Csound scores containing instructions to control parameters that can vary continuously. We will use simple notes (no sound-object) and no Csound instrument file, so that all scores can easily converted into sound files using the "default.orc" orchestra file supplied with BP3.
Consider the following grammar with the metronome set to 60 beats per minute:
The graphic display does not show pitchbend controls:
Pianoroll and object display of "C5 D5 E5"
The _pitchcont instruction at the beginning instructs the interpreter to interpolate pitchbend values throughout whole sequence. This process can be interrupted with _pitchstep.
The _pitchrange(200) instruction indicates that the pitch may vary between -200 and +200 units, which are mapped to the MIDI standard values 0 and +16383 (both logarithmic). This is the range required by "default.orc", which counts intervals in cents. There are 1200 cents in an octave. So, _pitchbend(100) would raise the following note by one semitone.
Note: No pitchbend value is assigned to 'C5'. The default value is '0'. Notes 'D5' and 'E5' are preceded by _pitchbend(0), which assigns a '0' value. All pitchbend variations are assigned during the prolongation of 'D5'. How is this done?
The MIDI output is deceptive. Pitchbend assignments are not taken into account in this format:
"C5 D5 E5" in the MIDI output
However, the Csound output has taken all parameters into account:
"C5 D5 E5" (with pitchbend assignments) in the Csound output
How does Csound process this phrase? Let us look at the Csound score:
A table (Function Table Statement, see documentation) labelled f101 has been created by Bol Processor and inserted above 'D5' to specify variations of the pitchbend parameter. This table is called by the 10th argument of line 'D5'. Arguments 8 and 9 contain the start and end values of pitchbend according to "default.orc". These are 0 for all three notes.
The second argument of the table is the duration of its validity, here 1.000 seconds. The third argument (256) is its size — always a power of 2. The fourth argument "-7" specifies the GEN routine that Csound will use for its interpolation (see documentation). By default, GEN07 (linear interpolation) is used.
Numbers highlighted in red indicate the values of pitchbend during the variation: 0, 120, -150, 0. Numbers in black indicate the time intervals between two values. Note that 102 + 51 + 103 = 256.
All continuous parameters are handled in the same way by the Bol Processor when creating Csound scores. This includes standard MIDI controls (volume, pressure, modulation, panoramic, pitchbend) and any additional parameters defined in the Csound instrument file. See for example the pages Sound-objects, Csound-objects and Sarasvati Vina.
Note
There is a workaround for playing the same piece with the correct pitchbend changes in MIDI. Change the rule to:
This is the same piece in a polymetric structure, with a line of silences '-' placed in the right places to receive pitchbend modifications. As pitchbend modifies all sounds on the current MIDI channel it will also modify 'D5' during its prolongation. The following is a MIDI rendering on PianoTeq — at a higher speed, so that 'D5' remains audible:
C5 D5 E5 in the MIDI format with pitchbend effects on D5
This page deals with the Bol Processor BP3 using an updated version of the Csound orchestra file "default.orc". Changes to the diapason ('A4' frequency) in the settings now affect the production of Csound scores.
In the revised Csound orchestra file, a few lines have been added to change the value of icps (oscillator frequency) according to that of the p4 argument:
if (p4 < 15.0) then icps = cpspch(p4) else icps = p4 endif
By default, this instrument receives the pitch value (argument p4) in the octave point pitch-class format — see documentation. In this case, the frequency depends only on the diapason set up in the Csound orchestra, or 440 Hz by default, i.e. cpspch(8.09) = 440.
To "tune" the Csound instrument to the diapason selected for the project in the Bol Processor BP3, if the base frequency is not exactly 440 Hz, p4 will contain the actual frequency of the note (cps format) instead of its octave point pitch-class value. The orchestra file "default.orc" can decide which format is used because (1) no note is ever sent above the 14th octave and (2) frequencies are never lower than 15 Hz. So, the value of p4 automatically makes the decision in "default.orc".
Let us try for example:
S --> A4 B4 C5
If the diapason is 440 Hz, we get the standard Csound score output:
This score shows the actual frequencies of the notes, for example 'A4' = 435 Hz. This sequence of notes will sound slightly lower than the previous one.
If the diapason is radically different from 440 Hz, the names of the notes will not change. Only the frequencies will be change accordingly. See for example the Csound score created with 'A4' = 300 Hz:
Let us now examine the changes in diapason when dealing with Csound objects. Take for example the object "a" in "-gr.tryCsoundObjects". The Csound score of its prototype (as shown in "-so.tryCsoundObjects") is a mix of 3 instruments:
t 0 120 i1 0 0.5 4.05 ; F0 i2 1.5 0.5 5.05 ; F1 i3 1.5 0.2 643.5 1 ; D#5 e
Instruments i1 and i2 use the octave point pitch-class format, while instrument i3 uses the direct cps format. This score has been created with 'A4' = 440 Hz which explains why 643.5 Hz is labelled D#5. The labelling of the notes is of minor importance as it will be revised when the performance Csound score is created.
When 'A4' = 440 Hz the Csound score of a performance of "a" exactly reflects the score in its prototype:
t 0.000 60.000 i1 0.000 0.250 4.05 90.000 90.000 0.000 0.000 0.000 0.000 ; F0 i2 0.750 0.250 5.05 0.000 0.000 90.000 90.000 0.000 0.000 0.000 ; F1 i3 0.750 0.100 643.50 1.000 ; D#5 s e
If the diapason is set to 500 Hz the Csound score of the performance will be:
t 0.000 60.000 i1 0.000 0.250 24.80 90.000 90.000 0.000 0.000 0.000 0.000 ; F0 i2 0.750 0.250 49.61 0.000 0.000 90.000 90.000 0.000 0.000 0.000 ; F1 i3 0.750 0.100 643.50 1.000 ; C#5 s e
Pianorolls with A4 = 440 Hz (left) and 500 Hz (right)
All pitches are now given in the cps format. The pitches of notes F0 and F1 would be changed in the sound output. However, the pitch of instrument i3 would remain at 643.50 Hz as set in the sound-object's prototype. As a result of the change in reference, the name of the note produced by i3 would now be 'C#5'. This change is reflected in the pianorolls (see image).
Important…
This automatic pitch format selection does not work if you try to send a frequency lower than 15 Hz, as it would be the case for 'F0' in the previous example if the diapason was set to 300 Hz. This should never happen, however, as 15 Hz is below the range of audible sounds.
At the opposite end, octaves beyond 14 are way beyond the musical range since 'C15' is already more than 535 KHz…
This might have an incidence on Csound scores being used for producing anything else than music, although in this case the use of the octave point pitch-class format is very unlikely.
Changing middle C key number
"Middle C", or 'C4' in the English convention, is the key in the middle of a piano keyboard. By convention, its MIDI key number is 60, but this value can be changed in the settings.
For example, setting 'C4' to key #48 will cause all notes on a MIDI device to be one octave (12 semitones) lower . This does not change the Csound sound output. Playing "A4 B4 C5" with 'C4' other than 60 will produce the same sound output and the same Csound score, but in the cps pitch format:
When applied to Csound objects, changing 'C4' to a key number other than 60 will not change the note names or their actual frequencies, but it will use the cps pitch format. For example, playing "a" will result in the following Csound score:
t 0.000 60.000 i1 0.000 0.250 21.83 90.000 90.000 0.000 0.000 0.000 0.000 ; F0 i2 0.750 0.250 43.65 0.000 0.000 90.000 90.000 0.000 0.000 0.000 ; F1 i3 0.750 0.100 643.50 1.000 ; D#5 s e
This article is a continuation of Csound check in which we introduced the creation of Csound parameters monitored by performance controls. Musical phrases were created from simple notes translated into Csound events in a straightforward manner. We now consider the creation of Csound scores based on sound-objects containing Csound instructions — which may be called "Csound objects".
Csound object "e" in the sound-object prototypes file "-so.tryCsoundObjects"
Csound objects contain a Csound score with a specific tempo and duration. For example, in object "e" shown above, the tempo (line "t" of the score) is 120 beats/min. The total duration is 2 beats, or 1000 ms. Note that to calculate the total duration of this sound-object, the durations of 'E3' and 'G3' (0.667 sec) shouldn't be added to those of 'C3' and 'D3', because of the start dates.
The duration of a Csound object is independent of the duration set by MIDI events that may coexist in the sound-object prototype. In most situations, note sequences and durations are identical in the MIDI stream and the Csound score. This makes it possible to play almost the same items via MIDI and Csound. However, as we will see, Csound is open to controls that are not available in MIDI.
Items are found in "‑da.tryCsoundObjects". They can also be created with the grammar "‑gr.tryCsoundObjects" using the alphabet "‑al.tryCsoundObjects" associated with the sound-object prototype file "‑so.tryCsoundObjects".
Calculations can be easily verified given the C-sound resource file "‑cs.tryCsoundObjects". This resource provides access to six Csound instruments, which should be programmed in the relevant Csound orchestra file. Unfortunately, only 'Instrument_1' has been programmed. Attempting to convert the Csound score to a sound file using the other instruments will therefore produce an error message from Csound. On this page, we will focus on visually checking Csound scores.
Let us start with sound-object 'a' whose Csound score is shown below. The score is given for a tempo of 60 beats per minute, giving a total duration of 2 beats ( = 1.5 + 0.5) or 2000 ms.
The first event (note 'F0') is repeated 2 times with identical timing, a meaningless detail to check that Csound and the Bol Processor can handle this abnormal case.
Events i1 and i2, calling instruments 1 and 2, describe tonal positions in the octave point pitch-class format: octave number + semitones above C. We notice that "5.05" has been mislabelled as 'G5'. This will have no effect on the computation, as the Bol Processor will automatically correct it to 'F1'. It will also rename notes according to the convention set in the settings: English, French or Indian.
Pitch format in instrument 3
Event i3, calling instrument 3, defines pitch as frequency (in Hz). It was assumed that 643.5 Hz is 'D#5' because the diapason is 'A4' = 440 Hz. However, a precise calculation yields 'E5' minus 41 cents.
The tuning of A4 is defined in the settings (page "-se.tryCsoundObjects"). Bol Processor will change the name of this note according to the diapason.
Changes of the diapason are taken into account by BP3 when generating Csound scores, but this was not yet the case with BP2. The following examples have been produced with the default 'A4' = 440 Hz, giving identical results with BP2 and BP3. See the page Csound tuning in BP3 page to examine different cases.
Producing object "a" at a tempo of 60 beats per minute results in the following Csound score:
Note that this score is more complete than the one contained in sound-object "a". This is because the "-so.tryCsoundObjects" sound-object prototype file is linked to a Csound resource file named "-cs.tryCsoundObjects":
'Instrument_1' of the Csound resource file is designed to handle 10 arguments while the score of "i1" events in "a" only contains 4. The 6 missing arguments are filled with default values of the parameters they represent. Here, for example, '90' is the default volume. Zeros represent default pitchbend or function table indexes.
You cannot convert this and other examples to sound with the supplied Csound orchestra "0-default.orc", because it onlyhandles instrument 1. All examples on this page are for visual inspection only.
Object graphic of f {a b, c}
In the following example, we need to look at the graph to understand why the events of "a" are delayed by 160ms with respect to "b". Object "b" has a pivot set at 20% of its duration from the start date. This can be checked in "-so.tryCsoundObjects".
Although the object graphic and the pianoroll for this item indicate that "b" should start on a negative date (-160ms), the Csound score is shifted to display only positive or null dates.
Note on pivots and relocation: sound-object "b" has its pivot shown as a full arrow, unlike other sound-objects in this set which only have a red triangle. This means that it is not relocatable. Relocation would be performed if these sound-objects had topological properties such as prohibiting the covering of their beginning/end, allowing truncation of beginning/end to a certain degree, breaking the tempo etc. A time-setting algorithm is run on each production to produce a solution that minimises the number of constraints violated. This is explained on the sound-objects page.
Sequence "b midiobject"
Let us now look at a phrase containing "midiobject", a sound-object with both a MIDI stream and a Csound score. The MIDI stream is ignored when constructing the score. The time resolution (10 ms) also has no effect on the accuracy of timings in the Csound score.
Since the score of "midiobject" has been defined with a tempo of 60 beats/min for a duration of 2 beats, the durations of the notes E3, C3, D3, G3 are unchanged.
Expression {a b a, c midiobject}
Now consider a polymetric structure in which the first line contains 3 sound-objects and the second line contains 2 sound-objects. The structure will be forced to a symbolic duration of 3 beats — the duration of "a b a" — and the second line will arrange the objects as "two in three" with symbolic durations of 1.5 beats.
This is clear on the picture, looking at the pivots of sound-objects, if one does not get confused by the physical duration of the sound-objects. The sound-object prototype "b" has a duration of 0.8 beats, resulting in a physical duration of 800 ms.
PIanoroll of {a b a, c midiobject}
On the second line, the symbolic duration of each object is 1.5 beats. Consequently, the sound-object "c", whose prototype has a physical duration of 1000 ms, is set to physical duration = 1000 * 1.5 = 1500 ms. The sound-object "midiobject", whose prototype duration is 2000 ms, is set to physical duration 2000 * 1.5 = 3000 ms.
These durations are reflected in the Csound score below.
The examples on the rest of this page may not match the configurations produced in 'da.tryCsoundObjects' exactly, because some sound-object parameters were modified after the page was written.
Combined objects and notes
In the following example, we combine sound-objects (containing Csound scores) with simple notes that are converted to Csound events. These notes are played on (default) MIDI channel 1, which is assigned to instrument 1.
aC4 D4b c
Combined objects and notes on pianoroll. Notes in brown colour are those available on both MIDI and Csound outputs. Notes in green are exclusively Csound.
This combination is highlighted in the pianoroll. Notes that are present in both the MIDI stream and the Csound score are displayed in brown, while notes that are present only in the Csound output are displayed in green.
Pitchbend mapping by instrument 2
Let us apply a continuous pitchbend control to a sound-object containing four Csound instructions, using instrument 2, which maps the MIDI pitchbend range [0..16384] to a range of [-200..+200], both on logarithmic scales. (This mapping is therefore linear.)
In the Bol Processor score, the use of mapped values in _pitchbend() controls is possible, thanks to a _pitchrange(200) instruction at the beginning of the sequence.
The resulting Csound score makes it clear that the pitchbend should vary continuously over each Csound event : 0 to 24.997, 24.997 to 49.994 etc. Csound will further interpolate the values using its GEN 07 (linear interpolation) generator.
_pitchrange(200) _pitchcont _pitchbend(0) c _pitchbend(100)
Volume control is possible on instruments 1 and 2, but not on instrument 3. Therefore its effect is only applied to certain events of sound-object "a":
In the following example, a continuous pitchbend correction cannot be applied because instrument 5, called by "d", does not have a pitchbend parameter. However, the value of +100 cents is applied to the pitch parameter itself.
The Csound score of sound-object "d" is limited to 1 note at 440 Hz (with reference to instrument 5). This note was labelled 'A4' on the prototype, but we should remember that with a diapason of 435 Hz it will be slightly higher than 'A4'. The increase is 1200 * log2(440/435) = 24 cents. So, in the performance it will be set to 124 cents above 435 Hz, giving 435 * 2^(124/1200) = 467 Hz. As shown below:
_pitchrange(200) _pitchcont _pitchbend(100) d _pitchbend(0)
i5 0.000 0.500 466.16 ; A4
In the following example, a continuous pitchbend correction results in different adjustments of the pitchbend parameters of the instruments called by sound-objects "a", "b" and "c". Simple notes 'C4' and 'D4' call instrument 1 because it is the one assigned to the (default) channel 1. The volume is also adjusted continuously.
Note that we also apply negative values to the pitchbend parameter, expecting the Csound orchestra to do the extrapolation.
_pitchrange(200) _pitchcont _volumecont _volume(30) _pitchbend(-10) a C4 D4 b c _pitchbend(100) _volume(127)
D4 starts at 1.840 instead of 2.000. This is because of the forced continuity of "b".
Settings of the "blurb" parameter
Let us check an arbitrary parameter "burb" which affects arguments 9, 10 and 11 of instrument 2.
This parameter is designed as additive in its combinations. The default value is '0'.
In sound-object "e", the third event 'D3' is required to set 'blurb' to a start value of 10 and to an end value of 30.
Csound score of sound-object "e"
These values are added to those interpolated over the continuous 'blurb' variation: 25.6 + (100 - 25.6) * 0.5 = 62.8 and 100 at dates 0.5 and 1 sec. This gives an initial value of 62.8 + 10 = 72.8 and a final value of 100 + 30 = 130.
_cont(blurb) _value(blurb,25.6) e _value(blurb,100)
In the Csound score of "e", event 'D3' has non-zero initial values on arguments 9 and 10. These values are added to those determined by variations of the "blurb" parameter, thereby giving 40 for argument 9 (the initial value of "blurb") and 70 for argument 10 (the final value). The same calculation is applied to the attached table f103. Consequently, the first and last values of a function table always reflect the initial and final values of the parameter. This allows Csound instruments to operate in a consistent manner, either interpolating the initial and final values, or picking up (and interpolating) the values in the attached function table.
The "oops" parameter in instrument 6
The Bol Processor combines Csound parameters either additively or multiplicatively. For predefined MIDI-mapped parameters, the combination mode is preset: all parameters, except volume, are combined additively. For additional (non-MIDI) parameters, the composer can choose both the default value and the combination mode.
For example, instrument 6 deals with an "oops" parameter that combines multiplicatively. Sound-object "f" contains calls to this instrument with values of "oops" other than the default.
The "oops" parameter varies from 0 to 4 over 1500 ms. At the start of 'D3' and 'E3', its values are 4 * (500 / 1500) = 1.33 and 4 * (1000 / 1500) = 2.66 respectively.
The initial value of "oops" in 'C3' is 0 * 0.5 = 0, and its final value 1.5 * 1.33 = 2, as shown on the score.
The initial value for 'D3' will be O, and for 'E3' it will be 0.25 * 2.66 = 0.665. The value at the end of 'D3' is 4.7 * 2.66 = 12.5. The value at the end of D3 is 2.5 * 4 = 10.
These examples have been designed to test all the features of the Csound interface as it is implemented in Bol Processor. We expect more to come as both environments continue to explore new concepts and build tools for musicians.
We apologise for the lack of a corpus of real musical pieces created with Bol Processor and Csound. A first example of high musical quality was composed in 1996: read and listen to Sarasvati vina!
Csound in the Bol Processor (BP2, BP3) environment
This article and the next one on Csound objects are reserved for Csound geeks interested in creating Csound scores with Bol Processor. They are complementary but they can be studied independently.
The examples in this section are not intended to be auditory. Rather, the idea was to produce short Csound scores that could be used to illustrate the treatment of parameters in a variety of contexts.
The calculations in this article can be easily checked against the Csound instrument file "‑cs.chekAllCsound" included in the bp3-ctests-main.zip example set.
All items can be produced with the grammar "‑gr.checkAllCsound".
Instrument 2 is used because it's the one assigned to channel 1 by default in the Csound instrument file "-cs.checkAllCsound". This score will not produce any sound with the "default.orc" orchestra file because it does not contain a definition for instrument 2. Argument 4 is the pitch (in Herz) related to the diapason (frequency of A4) set in "-se.checkAllCsound". Argument 5 is the MIDI value of the volume, default 90 according to the settings. Arguments 6 and 7 can be used for the 'blurb' parameter (see infra). Argument 8 is not not used, its value remains 0.
No treatment of MIDI pitchbend in instrument 2
Instrument 2 does not use the pitchbend value as a parameter, but changes the pitch parameter (in Hz) accordingly. In the following example, G4, which is 200 cents higher, will be played 2 semitones higher, at the same pitch as A4 (440 Hz).
Now we will force the instrument to 3. Note that many new parameters are displayed. The default volume is 90 on the MIDI scale. This is converted to 16.98 (log scale) using the volume mapping defined in instrument 3. As instrument 3 accepts pitchbend corrections (arguments 5 and 6), pitchbend = 16383 (+2 semitones) is applied to G4 instead of changing its frequency.
Arguments 5 and 6 represent the start and end values of the pitchbend. This makes it possible to tell Csound to calculate a portamento (see infra).
Mapping of modulation in instrument 3
Playing simple notes on channel 2 calls up instrument 3, which has volume and modulation control parameters. Here the modulation range (0 to 12431) is mapped to 0 to 3035.097 (arguments 11 and 12).
Another way to do the same without tempering with channels is to use instrument 3.
ins(3) _modcont _mod(0) C4 D4__ E4 _mod(12431)
Note that instrument specifications override the assignments of The_default instrument, which are made on the basis of the MIDI channel. For instance, in the following example, because of the _ins(1) statement, _chan(2) does not set the instrument index to 3, so _mod() is ignored:
Let us consider a polymetric structure in which the same note (D5) has two consecutive NoteOn's.
In MIDI, a NoteOff is inserted before the second NoteOn of "D5". In Csound the same instrument is called twice. In both versions the break between successive occurrences of "D5" is audible.
Note that this example would sound strange without the volume controls: we would get a silence during the time the two D5' are superimposed, simply because they are sine waves with equal amplitudes and opposite phases!
Let us look at the same note played at different volumes in stepwise variations. Notice that instrument 3 is now specified by its name "Harpsichord". (Don't look for it in an orchestra file!)
The following illustration shows the volume decreasing continuously from 127 (i.e. +24 after mapping) to 0 (i.e. -24 after mapping). Instrument 3 has two parameters (7 and 8) that take the start and end volumes respectively, and these values are interpolated by Csound (using scheme GEN07) to produce a continuous change.
So far we have seen how instruments interpolate between single start and end values. Instrument 1, here called "The_default", i.e. the one defined in "default.orc", is able to vary pitchbend and volume in a more sophisticated way, using a function table.
BP3 automatically creates function tables when required and when the instrument specification (here "-cs.checkAllCsound") provides slots (arguments) for entering function table indexes.
Let us look at a simple example with pitchbend. Both of the following notations result in the same score. You will hear the production of this score with the demo orchestra "default.orc". (Doesn't sound great!)
Note that GENO7 is used. GENO8 (cubic spline interpolation) could be considered, but it has the disadvantage of forcing the first derivative to zero at the start and end points. GEN07 is also much faster.
Here, C4 needs a 4-point table, because of _pitchcont whereas D4 only needs linear interpolation?
Don't forget to set _pitchrange(200) on channel 2, otherwise _pitchbend(180) will be used as the MIDI value (range 0..16383). Note again that channel 2 will not call instrument 3 because instrument 1 has already been specified.
The same applies to 'pitchbend', 'pressure', 'panoramic' and 'modulation' (all case sensitive). In instrument 3, MIDI modulation is remapped to the range 0..4000.
The 'Splashmachine' instrument handles the 'splash' parameter which is instructed to create function tables with GEN08 (cubic spline) instead of GEN07.
The algorithm is implemented in function Findabc() of "CsoundMaths.c".
When three pairs of input/output values are supplied, BP2 attempts to define a quadratic mapping from the input (x) to output (y).
This is an example of a successful mapping:
BP2 expects the mapping function to be monotonous, i.e. the three values (x1, x2, x3) supplied as the input and the ones supplied as the output (y1, y2, y3) must be strictly ordered. Even in this case a proper quadratic mapping may not be possible. See for instance:
Here the quadratic function is not monotonous even though the input values are ordered properly. In this case, BP2 replaces the incorrect part (the one containing an extremum) with a linear function, and changes the other part to make the curve tangent to the linear part. This yields the graph shown below: