Does anyone know a way to programatically skip all scheduled events?
Say I have a bunch of events scheduled for the future, via scoreline, schedule and related opcodes and plans changed and those events are no longer wanted, how can i “turn them off”?
I tried insertig an “x” statememnt via scoreline_i but that doesn’t seem to work.
as far as i understand, none of the score statements work in scoreline_i because they are part of the score preprocessor (which is not present in the actual csound language). so "x" etc will not work.
i seem to remember that in csound 7 there will be an opcode to undo scheduled events (i don't remember the name). but in csound 6 it is not, as far as i know.
turnoff3 turns off also future events, present also in Csound 6.18, if I remember correctly.
You need to call it on every instrument thought that may play.
as far as i understand, none of the score statements work in scoreline_i
because they are part of the score preprocessor (which is not present in
the actual csound language). so “x” etc will not work.
i seem to remember that in csound 7 there will be an opcode to undo
scheduled events (i don’t remember the name). but in csound 6 it is
not, as far as i know.
ciao -
joachim
Hi!
Does anyone know a way to programatically skip all scheduled events?
Say I have a bunch of events scheduled for the future, via scoreline,
schedule and related opcodes and plans changed and those events are no
longer wanted, how can i “turn them off”?
I tried insertig an “x” statememnt via scoreline_i but that doesn’t seem
to work.
Any ideas?
Cheers
Max
-odac
sr = 44100
0dbfs = 1
nchnls = 1
ksmps = 2
instr 1
scoreline_i {{
x
}}
endin
instr 2
a1 poscil .1, 330
out a1
endin
i1 1 1
i2 3 1
Prof. Maximilian Marcoll
Studio Director
Studio for Electroacoustic Music (SEAM)
University of Music/Franz Liszt/Weimar
Bauhaus University Weimar
All events sent to Csound via the score section, csoundEvent (csound 7 api) or csoundReadScore() (csound 6 api) before the engine start are “score events”: you can rewind them etc.
All events sent to Csound from anywhere after the engine started, are realtime events, kept on a separate list. As Tarmo said turnoff3 can act on these, but certain score commands may not work. Some preprocessing is possible with readscore.
I started investigating the possibility of turning an event off in the scheduled realtime list with matching parameters.
Prof. Victor Lazzarini
Maynooth University
Ireland