Actions

OpenScofo support actions as consequences of EVENTS, these actions are very tied with the program where OpenScofo is running and for now just are supported on PureData and Max.

There are currently two types of actions: sendto and luacall. Actions can be executed immediately after the EVENT detection or after a delay specified using the delay keyword.

Delayed Messages

Absolute time delay

Absolute time are clock time, and they don't change if the performer plays your must faster or slower, always have the same duration.

• delay 2000 ms: Has a delay of 2 seconds after the EVENT detection.
• delay 2 sec: Has a delay of 2 seconds after the EVENT detection.

For example:

NOTE C4 2 
    delay 2000 ms sendto e1 [1 2 3 4]

Will send the list 1 2 3 4 to the receiver e1 after 2 seconds.

Relative time delay

Relative time are music time, they change if the performer plays your must faster or slower.

• delay 1 tempo: Has a delay of 1 tempo after the EVENT detection.
• delay 0.5 tempo: Has a delay of 0.5 tempo after the EVENT detection.

Actions

sendto

• sendto e1: Send a bang to the receiver e1.
• sendto myreceiver [hello world]: Send hello world to the receiver myreceiver.
• delay 1 tempo sendto e1: Send a bang to the receiver e1 after the duration on 1 tempo.

luacall

Lua function are executed immediately after the event detection of after some delay time.

• luacall(myluafunc("hello world"): Execute the function myluafunc immediately.
• delay 1 tempo luacall(myluafunc("hello after 1 tempo"): Execute the function after 1 tempo.

LUA {
    function myluafunc(s)
        pd.post(s)
    end
}