4 ms·
40ms is way too much. To put it in perspective, at 60Hz, that's almost 3 frames of video. 10ms would start to be useful for music, but I wouldn't call it good
by snvzz 6y ago
40ms is way too much. To put it in perspective, at 60Hz, that's almost 3 frames of video.
10ms would start to be useful for music, but I wouldn't call it good until it was below 2ms, which is what I run my jackd setup (which requires linux-rt) at.
I'm afraid we won't see good latency until Android moves away from Linux. The good news is that this is bound to happen, sooner or latter, as Fuchsia exists.
- mhh__ 6y agoIs 10ms really the bounds of usefulness - especially on a phone?
- bsder 6y agoSpeed of sound is one foot per millisecond. 40ms is 40 feet. Bands play with that kind of separation all the time.
- jjcon 6y agoThere is a huge difference between the latency you need to feasibly pull of a live performance - and the latency you need for high quality audio production. Why you would be considering doing that on an android though I'm not sure. Though I guess it may be a reinforcing problem, there isn't an ecosystem because the tech isn't there.
- snvzz 6y ago>Bands play with that kind of separation all the time. Shortcutting this latency is one of many reasons musicians wear earplugs on stage.
- anaisbetts 6y agoThe latency that matters is the discrepancy between what you feel with your fingers and what you hear. Your finger nerves respond extremely quickly, and if what you hear is delayed from what you feel by more than ~10ms, it is extremely jarring and basically unusable