Optimally, MIDI encodes this as a single status byte followed by three note+velocity pairs of data bytes. So let's say that you are playing a simple three-note chord. At 31250 baud with eight effective data bits per 10 bit packet you're going to get an additional 0.32 ms of latency per byte. When using MIDI, its maximum bandwidth is going to be a huge bottleneck in achieving that kind of latency. doesn't include input latency: average latency of the audio stream between data entering the stream and it being presented to the audio deviceĮDIT they know they need latency figures "Publish a list of Android device latency"
That's how bad android is.ĮDIT 7ms claimed in screenshot at. The surprising thing is that delayed sound effects from games in general aren't so jarring.įWIW iphone audio latency also isn't good enough, despite being far better than android. The latency is shocking if you use the mode where you free-"play" the instrument, and is why actual musicians often a tough time with these games. Rhythm games like rockband/guitar hero don't actually need this, they need only relate it to the audio playing (and also config compensation for input latency). (If I sound cynical, this isn't the first low-latency offering for android.) It's just "low" for android.įunfact: consoles also have terrible audio latency. It's revealing that they don't reveal latency for any devices at all.
The "lowest possible" on android might not be low enough for musical instuments (<10-15ms).
Oboe provides the lowest possible audio latency across the widest range of Android devices
0 kommentar(er)
