libsoundio vs RtAudio

Joshua Olson edited this page May 25, 2016 · 2 revisions

Benefits of libsoundio over RtAudio:

  • C library, not C++.
  • Supports channel layouts (also known as channel maps), important for surround sound applications.
  • Exposes both device id and friendly name. id you could save in a config file because it persists between devices becoming plugged and unplugged, while friendly name is suitable for exposing to users.
  • Callback function provides frame_count_min and frame_count_max to optimally leverage fixed-buffer backends such as JACK and CoreAudio, as well as flexible buffer backends such as ALSA and PulseAudio.
  • Exposes extra API that is only available on some backends. For example you can provide application name and stream names which is used by JACK and PulseAudio.
  • Ability to monitor devices and get an event when available devices change.
  • Ability to get an event when the backend is disconnected, for example when the JACK server or PulseAudio server shuts down.
  • Ability to connect to multiple backends at once. For example you could have an ALSA device open and a JACK device open at the same time.
  • Does not have code for deprecated backends such as OSS, DirectSound.

Benefits of RtAudio over libsoundio:

  • Supports ASIO backend. The libsoundio project believes that WASAPI is a suitable replacement for ASIO.
  • Supports older versions of Windows than Windows 7.