Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Steller's scheduler needs more robust timing #1

Open
srikumarks opened this issue Dec 28, 2012 · 1 comment
Open

Steller's scheduler needs more robust timing #1

srikumarks opened this issue Dec 28, 2012 · 1 comment
Assignees

Comments

@srikumarks
Copy link
Owner

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.

@ghost ghost assigned srikumarks Dec 28, 2012
@srikumarks
Copy link
Owner Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant