inside the first zip file will be two more zip files. One called ChimesAbide
the other Mycsound.
ChimesAbide contains the score and orchestra arrangement and Mycsound
contains instrument designs that chimesabide the chimesabide orchester
the chimesabide.sco file "#includes" .sco files stored in the folder
because this is set up in the pi it will be likly that to run csound -o
chimAbi chimeAbi.orc chimeAbi.sco inside the ChimesAbide directory the
"#include"'s will have to be adjusted.
the trouble im havening should reveal itself when
csound -o chimAbi chimeAbi.orc chimeAbi.sco is run as the files are and
observe the audio.
after words inside chimeAbi.sco I then go to uncomment the #include
statement directly before ending in m1a.sco on and on play back you'll here
a new note followed by the next sound (the sound that would have played
previously) except it plays for longer!? Which is actuallly what I expected
the sound to be on its own ?
I don't want them to occur simultaneously and it should just mean that one
plays after the other.
The obscure thing is that the duration of m1b.sco varies depending on the
presents of m1a.sco which is odd ? and I shouldn't think the s would
Just a suggestion; instead of using s use b with an apprpriate number.
Then ftables will remain, tempo will be universal and it will be simpler,
for example reverbs over measures.
At least that is what I do when I want to write scores based on time 0 but
asseble them. Sections are rather drastic and were originally a way of
conservingrecycling memory in the days of smaller machines.