Steller's scheduler needs more robust timing

Question

Steller's scheduler needs more robust timing

Opened this issue 12 years ago · 1 comments

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.

Answer 1 · 2014-02-17T03:43:39.000Z

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.