3 ms·
The only thing which scares me terribly is that I'm NOT seeing any discussion of real-time problems. Android has an absolutely shit audio stack. iOS simply de
by bsder 5y ago
The only thing which scares me terribly is that I'm NOT seeing any discussion of real-time problems.
Android has an absolutely shit audio stack. iOS simply destroys Android on this front.
Fixing that requires that you architect the entire kernel around making sure that you can service the audio stack in real-time with low latency.
The fact that I haven't seen even the slightest mention of this makes me worry that the Fuchsia folks haven't really learned any lessons from Android and are simply repeating the same mistakes.
- surajrmal 5y agoFuchsia is designed with real time tasks in mind. The scheduler operates both fair scheduling algorithm as well as a deadline scheduling algorithm. The audio subsystem has it's threads scheduled using the deadline constraints. The official docs seems to be missing some content on this unfortunately. https://fuchsia.dev/reference/fidl/fuchsia.scheduler?hl=en#ProfileProvider.GetDeadlineProfile https://fuchsia.dev/reference/fidl/fuchsia.scheduler?hl=en#P... describes the API which provides the deadline scheduling capability.
- bsder 5y agoYAY! So good to be wrong. Please make sure that the audio subsystem gets the attention it desperately needs.
- kaba0 5y agoAs far as I know, Android’s less than great audio stack is not due to OS constraint — linux itself has both Jack and the now new pipewire, which doesn’t have any problem with low-latency.
- pjmlp 5y agoOnly when not using AAudio. Granted, the NDK is anything but friendly, but the option already exists for the last couple of Android versions.
- deleted 5y ago[deleted]