| 68 |
end on |
end on |
| 69 |
</code> |
</code> |
| 70 |
|
|
| 71 |
<note class="important"> |
<note> |
| 72 |
Using the <code>wait()</code> function can lead to concurrency issues with |
Using the <code>wait()</code> function can lead to concurrency issues with |
| 73 |
regular variables, which are global variables by default. You might need |
regular variables, which are global variables by default. You might need |
| 74 |
to use <a href="nksp.html#polyphonic_variables">polyphonic variables</a> |
to use <a href="nksp.html#polyphonic_variables">polyphonic variables</a> |
| 75 |
in such cases. |
in such cases. |
| 76 |
</note> |
</note> |
| 77 |
|
|
| 78 |
<note class="important"> |
<note> |
| 79 |
The <code>wait()</code> function is not fully implemented in LinuxSampler |
You need at least LinuxSampler 2.0.0.svn2 or higher for the |
| 80 |
yet. Currently a <code>wait()</code> function call suspends execution, |
<code>wait()</code> function to fully work as expected. Versions |
| 81 |
but since the respective scheduler code is yet missing in LinuxSampler, |
of LinuxSampler older than that will not resume the script at the |
| 82 |
the script will automatically be resumed with the next audio fragment |
requested amount of time, instead those older version will resume |
| 83 |
cycle. So effectively a <code>wait()</code> call will pause your script |
the script always at the beginning of the next audio fragment |
| 84 |
for a few miliseconds with LinuxSampler right now, no matter which |
cycle. So effectively a <code>wait()</code> call with a LinuxSampler |
| 85 |
function argument you provided. Hopefully this will be implemented soon |
version older than 2.0.0.svn2 will pause your script for a few |
| 86 |
though. |
miliseconds, no matter which function argument you provided. |
| 87 |
</note> |
</note> |
| 88 |
|
|
| 89 |
</body> |
</body> |
Parent Directory
| 
Revision Log
| 
Patch