justin = { main feed , music , code , askjf , pubkey };
Ask Justin Frankel
No reasonable question unanswered since 2009!

Suggested topics: programming, music, sleep, coffee, etc.

Note: please do not ask questions about REAPER features, bugs or scheduling, use the forums instead.

Name: Ask: Human (enter yes):
[back to index] | [unreplied] | [replied] | [recent comments] | [all]
Question: Is there, in your opinion, a clearly better driver/sysyem between ASIO, ALSA and CoreAudio? Why do you think that Microsoft never developed a built-in low-latency universal driver if even Linux has one?
Asked by Joan (37.159.65.x) on May 2 2019, 11:55pm
Reply on May 3 2019, 3:28am:
    Hmm they all have their strengths and weaknesses. Some thoughts:
    • CoreAudio: slightly crufty but relatively decent API. Multiple clients (awesome!), floating point, aggregate devices, overall winner IMO.
    • ASIO: pretty easy API, but missing functionality (nobody seems to implement underrun indicators???), and most drivers don't support multiple clients/routing.
    • ALSA: moderately clean API, but hard to get right across various drivers, also programmer responsible for scheduling. No multiple-client support.
    • JACK: probably the best API of all worlds, but configuring it is still a pain

Comments:
  • Posted by wasereb4 (94.134.90.x) on May 4 2019, 10:02pm:
    "that Microsoft never developed a built-in low-latency universal driver" - that's supposed to be WASAPI I guess?

  • Posted by Justin on May 5 2019, 12:51pm:
    WASAPI is a terrible API IMO, and also in multi-client (shared) mode it is not particularly low in latency.

Comment:
    Your Name:   -- Site Owner's Name:  (for human-verification)

    Comment:
[back to index] | [unreplied] | [replied] | [recent comments] | [all]
Copyright 2024 Justin Frankel. | RSS