. . . i wonder if the referenced minimum latency standard of categorically 20 ms or less is sufficient to integrate successfully in a NINJAM style jam session, how do you think?
If there's some plug and chug modular code swapout that can be done with reasonable amounts of code rephrasing, i'd be interested to know about it, to enable jamming from a personal computer here with NINJAM server and outdated windows client installed, and a mobile phone overseas with a duct taped .apk file wired over to it. with the above referenced latency standard for some android devices, is it a doable type of scenario, do you think? how about with the longer 45 ms standard which seems more universally established across devices? is that just too laggy, already?
curious if it's worth my looking at in detail. what do you say?
ps the link above claims musicians need 10 ms latency at most, but stops short of saying that devices just don't offer this. do you know if there's any standardized way to look up mobile devices by their achievable audio latency? this could prove useful to check beyond androids low precision latency flags as reported. can you point me in any narrower direction than standard web search engines are likely to turn up?