> Hello Eric-
> I've tried out port() in the saolc that's up on the site (Windows
version),
> and for some reason I get a ton of messages that all read
>
> co_port: not done yet.
Um. That probably means that I screwed up and put the version
with port() in the wrong place. Can you see the build date on it?
I'm out of the office and will fix it when I'm in, maybe tomorrow.
> Also exporting the sinefreq did indeed work fine- I have my own
> non-standard reason for wanting to use this within an instrument rather
> than controllers. This way I can trigger sets of gestures with a single
> instrument line in the score.
Yes, that makes sense to me. What do you think of the "imports"/
"exports" distinction? I liked it at first, but now it seems a bit
precious to me. Should we unify them with "global"?
> The controller construct is a very readable way to effect a variable
within
> a single instrument. One problem I could see is that this will still
> affect all instantiations of that instrument- for instance if you had a
> chord held down all notes would be affected. ZIPI (R.I.P.) had a nice
> construct of Note ID to allow the user to affect a specific instantiation
> of a note.
No, this is what the labels are for. If you do
n1: 0.0 instr1 x y z
n2: 0.0 instr1 x y z
n1: 0.0 instr1 x y z
1.0 n1 control foo 1
1.0 n2 control foo 2
in the score, then "foo" is set to 1 in the first and third instances of
instr1, and to 2 in the second one.
If you don't use a label, you're controlling a global variable rather
than an instrument variable.
Best,
-- Eric
This archive was generated by hypermail 2b29 : Mon Jan 28 2002 - 11:46:32 EST