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
According to the specifications, automations that are cancelled halfway through should run until the cancellation point like nothing happened. Unfortunately, the polyfill only removes the affected automation and sets its calculated value at cancelTime, which may work fine if the cancellation falls close to currentTime, but it results in a hard, discontinuous, audible change if the cancellation point is way in the future.
To fix this, after finding the automation which is happening at cancelTime, calculating its value at the cancellation point, and calling cancelScheduledValues(cancelTime), the polyfill should finally reintroduce the same type of automation but limited to the time interval between its original starting point and the cancellation point, with the calculated value as its target.
According to the specifications, automations that are cancelled halfway through should run until the cancellation point like nothing happened. Unfortunately, the polyfill only removes the affected automation and sets its calculated value at
cancelTime
, which may work fine if the cancellation falls close tocurrentTime
, but it results in a hard, discontinuous, audible change if the cancellation point is way in the future.To fix this, after finding the automation which is happening at
cancelTime
, calculating its value at the cancellation point, and callingcancelScheduledValues(cancelTime)
, the polyfill should finally reintroduce the same type of automation but limited to the time interval between its original starting point and the cancellation point, with the calculated value as its target.Demonstration:
The text was updated successfully, but these errors were encountered: