3 ms·
FYI, in Chrome on Linux, there's a glitchy crackling noise. Maybe a buffer under run or something. It happens a lot more often if you strum lots of strings quic
by adrianmonk 2y ago
FYI, in Chrome on Linux, there's a glitchy crackling noise. Maybe a buffer under run or something. It happens a lot more often if you strum lots of strings quickly.
It also happens in Firefox but a lot less.
- moffkalast 2y agoChrome on Windows as well.
- l3x4ur1n 2y agoBrave on Android also
- ikari_pl 2y agoFirefox on Android is fine
- TazeTSchnitzel 2y agoThis can happen a lot with web audio stuff like this, it's the browser struggling to keep up.
- wayoverthecloud 2y agoChrome on Android too
- petrichorko 2y agoYes, modifying buffer_size in audio_shader.js to 4096 completely fixes this issue on Windows (chrome).
- elihu 2y agoCan confirm on Chromium/Linux.
- plasticeagle 2y agoArc on MacOS too.
- chaosprint 2y agoI also have serious popping in chrome on my mac. This shouldn't happen. The main reason is the use of createScriptProcessor. This should be replaced with AudioWorklet. Use WASM + SharedArraybuffer for calculation. The visual of picking the strings is great, I spent a lot of time on it, I believe the vote is also a recognition of this. Here is a similar idea (karplus) implemented with Rust + WASM, which is much better in terms of audio quality: https://jackschaedler.github.io/karplus-stress-tester/ https://jackschaedler.github.io/karplus-stress-tester/ I also wrote a simple api to use Rust wasm audio here: https://glicol.js.org/ https://glicol.js.org/ If you are interested in doing some use cases, leave a message. I am actively maintaining it recently.
- SimDeBeau 2y agoNo sound on firefox on mac or ipad, and glitchy sound on safari on mac