3 ms·
Yeah, I've thought about it but couldn't figure out a good way to do it UI-wise. In terms of my design goals, it's important that every audible element be visib
by archagon 10y ago
Yeah, I've thought about it but couldn't figure out a good way to do it UI-wise. In terms of my design goals, it's important that every audible element be visible on screen, so I can't just shove it into a separate mode.
I'd love to do an Android version at some point. Wonder if the audio stack is up to snuff?
- widdershins 10y agoAndroid's audio stack is pretty poor. Audio callbacks can happen at very uneven intervals, unlike iOS's reliable high-priority scheduling. The result is that you either have to buffer more (resulting in high latency) or radically reduce the time spent rendering your audio buffers, which of course means less time for making nice sound. Google actually recommends that you use no more than 1/4 of the typical time budget for rendering, to account for these non-deterministic callback times.