Have the latest versions of Unity definitely corrected the issues with the audio latency on Android devices.
These issues were so terrible that even the “best latency” option in the audio settings could not do anything about them.
I’m trying to gauge the cost/benefits regarding time and work about a potential migration from 2019 LTS.
No.
1 Like
It’s really something spectacular to be honest.
The number of installs might be inflated if they count all updates too but that would be very disingenuous of Google and I’d doubt it would drop below a billion anyway.
Taking this at face value, we see that one year ago (2021 March) there had already been more than 4 BILLION installs of the official new audio API along its OBOE wrapper, yet all we can find for Unity today in terms of support for the official system is a barely tried Chinese plugin that’s around $ 20??
https://github.com/google/oboe
It is not even managed by Unity itself as an option in 2022. Is that not embarrassing?
Unity should cover all three options:
- pure native: older native or newer AAudio, detected automatically with AAudio having priority, no mixer FMOD stuff though, loading managed manually; could apply to iOS too. (technically unnecessary with an OBOE support)
- mediated native: AAudio + OBOE, still goes up through Unity but somehow manages to avoid the bad latency.
- vanilla Unity: with the horrible lag