What I want to know is whether Lyra takes any longer to encode than the alternatives. Because as far as I can tell, nobody cares in the slightest about latency. Phone calls are getting to be like writing postcards to each other. Speak in a whole paragraph. Wait several seconds for the latency to clear. Then the other party responds with a whole paragraph, waits several seconds for the latency to clear... Improvements…
I spent the last year and a half living about as far from my home city as possible (Melbourne > Edinburgh) (Currently in quarantine) and the latency of phone calls drives me nuts . The huge gaps between people speaking, and the complete change in conversation flow since you have to speak in huge continuous paragraphs. The constant "go ahead" , "no you go" etc... Ugh. But I agree with you... nobody seems to care excep…
Well, there's part of your problem right there. No need to even mention Bluetooth or device-related delays.
South Australia to North Britain is the better part of literally half way across the globe. It's either 64000 km at lightspeed (via satellite) or roughly 35000 km via optic fibre cable at 60% lightspeed (e.g. equivalent to ~60000km at lightspeed).
That's 200 ms one way latency just from the distance alone (best case scenario, no less), so 400 ms of latency just from distance alone. Even with something like Starlink we'd still be talking about at least 100 ms latency.
The whole latency from wireless protocols and codecs are just the cherry on top.