Ksp reference Manual

See Also
on init
3.10. polyphonic $ (polyphonic integer)
declare polyphonic $
Declare a user-defined polyphonic variable to store a single integer value per note event
Remarks
• A polyphonic variable acts as a unique variable for each executed note event, avoiding con-
flicts in callbacks that are executed in parallel for example when using 
wait().
• A polyphonic variable retains its value in the release callback of the corresponding note.
• Polyphonic variables need much more memory than normal variables.
• Polyphonic variables should only be used in note and release callbacks.
Examples
on init
declare polyphonic $a
{declare $a}
end on
on note
ignore_event($EVENT_ID)
$a:= 0
while ($a < 13 and $NOTE_HELD = 1) play_note($EVENT_NOTE+$a,$EVENT_VELOCITY,0,$DURATION_QUARTER/2)
inc($a)
wait($DURATION_QUARTER)
end while
end on
To hear the effect of the polyphonic variable, play and hold an octave: both notes will ascend chro-
matically. Then make $a a normal variable and play the octave again: $a will be shared by both
executed callbacks, thus both notes will ascend in larger intervals.
on init
declare $counter
declare polyphonic $polyphonic_counter
end on
on note
message($polyphonic_counter & " " & $counter)
inc($counter)
inc($polyphonic_counter)
end on
Variables
19
KSP Reference Manual

---

Since a polyphonic variable is always unique per callback, $polyphonic_counter will always be 0 in
the displayed message