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
We fixed this once by switching to requestAnimationFrame, but it looks like it's back.
This time, I suspect it's a cross-browser intersectionObserver issue, because I can still hear some notes when scrolling up quickly.
The text was updated successfully, but these errors were encountered:
It looks like we can solve a lot of tempo issues if we use the WebAudio clock instead of the Javascript/computer clock for scheduling notes. This is a decent refactor, but early tests show a dramatic improvement in all browsers, so we're doing it.
Reference docs: https://www.html5rocks.com/en/tutorials/audio/scheduling/#toc-usingsettimeout
Sorry, something went wrong.
I just pushed up a rebuilt playing and scrolling system that fixes this issue in all the browsers I've been able to test. I'm really happy about it!
No branches or pull requests
We fixed this once by switching to requestAnimationFrame, but it looks like it's back.
This time, I suspect it's a cross-browser intersectionObserver issue, because I can still hear some notes when scrolling up quickly.
The text was updated successfully, but these errors were encountered: