The following program demonstrates reading from two different input
files. The idea is to switch between two 2-section scores, and write
out the interleaved sections to a single output file.
cscore()
/* callable from either csound or standalone cscore */
{
fp1 = getcurfp();
/* this is the command-line score */
fp2 = filopen("score2.srt"); /* this is an additional
score file */
a = lget();
/* read section from score 1 */
lput(a);
/* write it out as is */
putstr("s");
setcurfp(fp2);
b = lget();
/* read section from score 2 */
lput(b);
/* write it out as is */
putstr("s");
lrelev(a);
/* optional to reclaim space */
lrelev(b);
setcurfp(fp1);
a = lget();
/* read next section from score 1 */
lput(a);
/* write it out */
putstr("s");
setcurfp(fp2);
b = lget();
/* read next sect from score 2 */
lput(b);
/ * write it out */
putstr("e");
Finally, we show how to take a literal, uninterpreted score file and
imbue it with some expressive timing changes. The theory of composer-related
metric pulses has been investigated at length by Manfred Clynes, and the
following is in the spirit of his work. The strategy here is to first
create an array of new onset times for every possible sixteenth-note
onset, then to index into it so as to adjust the start and duration of
each note of the input score to the interpreted time-points. This
also shows how a Csound orchestra can be invoked repeatedly from
a run-time score generator.
/* fill the array with interpreted
ontimes */
for (acc192=0.,n192=0; n192<4; acc192+=192.*inc192,n192++)
for (acc48=acc192,inc192=four[n192],n48=0; n48<4;
acc48+=48.*inc48,n48++)
for (acc12=acc48,inc48=inc192*four[n48],n12=0;n12<4;
acc12+=12.*inc12,n12++)
for (acc3=acc12,inc12=inc48*four[n12],n3=0;
n3<4; acc3+=3.*inc3,n3++)
for (acc1=acc3,inc3=inc12*four[n3],n1=0;
n1<3; acc1+=inc1,n1++)
for (acc16=acc1,inc1=inc3*three[n1],n16=0; n16<4;
acc16+=.25*inc1*four[n16],n16++)
*p++ = acc16;
/* for (p = pulse16, n1 = 48; n1--; p += 4) /* show
vals & diffs */
/* printf("%g %g %g %g %g %g %g %g\n", *p, *(p+1),
*(p+2), *(p+3),
/* *(p+1)-*p, *(p+2)-*(p+1), *(p+3)-*(p+2), *(p+4)-*(p+3));
*/
a = lget();
/* read sect from tempo-warped score */
b = lseptwf(a);
/* separate warp & fn statements */
lplay(b);
/* and send these to performance */
a = lappstrev(a, "s"); /* append a sect statement to
note list */
lplay(a);
/* play the note-list without interpretation */
for (ep = &a->e[1], n1 = a->nevents; n1--; ) { /* now
pulse-modifiy it */
e = *ep++;
if (e->op == 'i') {
e->p[2] = pulse16[(int)(4. * e->p2orig)];
e->p[3] = pulse16[(int)(4. * (e->p2orig + e->p3orig))]
- e->p[2];
}
}
lplay(a); /* now play modified list */
As stated above, the input files to Cscore may be in original or time-warped and pre-sorted form; this modality will be preserved (section by section) in reading, processing and writing scores. Standalone processing will most often use unwarped sources and create unwarped new files. When running from within Csound the input score will arrive already warped and sorted, and can thus be sent directly (normally section by section) to the orchestra.
A list of events can be conveyed to a Csound orchestra using lplay. There may be any number of lplay calls in a Cscore program. Each list so conveyed can be either time-warped or not, but each list must be in strict p2-chronological order (either from presorting or using lsort). If there is no lplay in a cscore module run from within Csound, all events written out (via putev, putstr or lput) constitute a new score, which will be sent initially to scsort then to the Csound orchestra for performance. These can be examined in the files 'cscore.out' and 'cscore.srt'.
A standalone cscore program will normally use the put commands to write into its output file. If a standalone Cscore program contains lplay, the events thus intended for performance will instead be printed on the console.
A note list sent by lplay for performance should be temporally
distinct from subsequent note lists. No note-end should extend past
the next list's start time, since lplay will complete each list
before starting the next (i.e. like a Section marker that doesn't reset
local time to zero). This is important when using lgetnext() or lgetuntil()
to fetch and process score segments prior to performance.