4 ms·
Does this contribute to macOS's suitability for DAW applications or is that more the baked in low-latency audio drivers?
by almoni 8mo ago
Does this contribute to macOS's suitability for DAW applications or is that more the baked in low-latency audio drivers?
- bigyabai 8mo agoCoreAudio probably deserves most of the credit, there. Similar ASIO-style solutions like JACK, DirectSound and now Pipewire hit the sub-30ms mark without any big scheduler tweaks.
- lukeh 8mo agoIOKit was designed to support CoreAudio from the start, cc gvdl.
- KerrAvon 8mo agoCoreAudio was developed alongside xnu / IOKit for Mac OS X, so it’s kind of all of it. Apple had the opportunity to start fresh with a built-in super low-latency audio subsystem at the turn of the century, and they took it.
- dcrazy 8mo agoAudio actually runs on a dedicated realtime thread. This used to be scheduled differently, but nowadays it might be implemented by the FIXPRI bucket described in this document.