You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the implementation of flock.ugen.triggerBuffer will allocate a new buffer voice whenever its trigger input transitions to a high state. However, if—for whatever reason—a voice's speed is set to 0, it will still allocate the voice despite the fact that the voice will never make any sound and will never be deallocated (since it never reads to the end of its buffer).
The voice allocation logic should be changed to never allocate voices when the current speed is zero.
The text was updated successfully, but these errors were encountered:
Currently, the implementation of
flock.ugen.triggerBuffer
will allocate a new buffer voice whenever itstrigger
input transitions to a high state. However, if—for whatever reason—a voice'sspeed
is set to 0, it will still allocate the voice despite the fact that the voice will never make any sound and will never be deallocated (since it never reads to the end of its buffer).The voice allocation logic should be changed to never allocate voices when the current speed is zero.
The text was updated successfully, but these errors were encountered: