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
Steller's scheduler relies on the AudioContext.currentTime to schedule events. This works well for audio, but after the inclusion of visuals, does not work consistently for synchronized animation. This is because animation runs at 60fps, but the frame size by which currentTime updates may differ between browsers and platforms. For example, this is pretty bad on Chrome on Linux. Even Chrome Canary on MacOSX does worse than Chrome on MacOSX. So the timing needs of the two and different and this really needs to be solved.
The text was updated successfully, but these errors were encountered:
The real (and perhaps the only?) way this can be solved is if the audio subsystem exposes a function to convert between the time coordinates of AudioContext.currentTime and that of the DOM HighRes Time Stamp.
Steller's scheduler relies on the AudioContext.currentTime to schedule events. This works well for audio, but after the inclusion of visuals, does not work consistently for synchronized animation. This is because animation runs at 60fps, but the frame size by which currentTime updates may differ between browsers and platforms. For example, this is pretty bad on Chrome on Linux. Even Chrome Canary on MacOSX does worse than Chrome on MacOSX. So the timing needs of the two and different and this really needs to be solved.
The text was updated successfully, but these errors were encountered: