Re: triginstr - new opcode (re-resend)
| Date | 1999-09-03 17:14 |
| From | richard bowers |
| Subject | Re: triginstr - new opcode (re-resend) |
I agree with David up to a point. I think schedule/when should
be fixed because they're simpler to use but I've just read the documentation for
triginstr and it looks tasty. k-rate variables make it tricky but much richer. I
think updating scheds would make for ungainly opcodes. (Maybe there
should be a third: schedkwhen, or something.)
It ties-in very neatly with an orch I'm working on right now
which will store attack times from real input to a table (written on the
fly somehow) for subsequent reading by, I now know, triginstr.
I'm really looking forward to this one.
Richard Bowers
PS. With the sched* opcodes I find that the triggered
instruments are held indefinitely. Is that the case, anyone? (In realtime it
results in the break-up of the signal due to overflow(?).)
|