Cross-platform audio in Rust
Go to file
Tom Gowan 49bc3ee367 remove release symbols 2019-07-05 05:51:28 +10:00
.circleci Add testing on circle-ci (#171) 2017-10-21 15:08:34 +02:00
alsa-sys Bump alsa-sys version number 2017-03-06 15:57:18 +00:00
asio-sys fixes, remove transmute 2019-07-05 05:51:26 +10:00
examples Refactor `Host` and related traits into a new `traits` module 2019-06-29 14:45:15 +02:00
src bug fix and comment 2019-07-05 05:51:27 +10:00
.gitignore git ignore, temp files, fetch_add, os cfg 2019-07-05 05:51:26 +10:00
.rustfmt.toml Run rustfmt on the code (#162) 2017-10-11 13:24:49 +02:00
.travis.yml Stop publishing on gh-pages 2017-02-10 09:45:41 +01:00
CHANGELOG.md add changelog entries for #248 #254 & #269; update version to 0.9.0 2019-06-06 10:29:52 -05:00
Cargo.toml remove release symbols 2019-07-05 05:51:28 +10:00
README.md Change step 7. to refer to VCVARS. 2019-07-05 05:51:27 +10:00
appveyor.yml Remove gnu target to avoid need to install gcc for cc crate 2019-06-21 16:17:58 +02:00
build.rs opt in and bug fix 2019-07-05 05:51:26 +10:00

README.md

CPAL - Cross-Platform Audio Library

Build Status Crates.io docs.rs

Low-level library for audio input and output in pure Rust.

This library currently supports the following:

  • Enumerate supported audio hosts.
  • Enumerate all available audio devices.
  • Get the current default input and output devices.
  • Enumerate known supported input and output stream formats for a device.
  • Get the current default input and output stream formats for a device.
  • Build and run input and output PCM streams on a chosen device with a given stream format.

Currently supported backends include:

  • Linux (via ALSA)
  • Windows (via WASAPI by default, see ASIO instructions below)
  • macOS (via CoreAudio)
  • iOS (via CoreAudio)
  • Emscripten

Note that on Linux, the ALSA development files are required. These are provided as part of the libasound2-dev package on Debian and Ubuntu distributions and alsa-lib-devel on Fedora.

ASIO on Windows

ASIO is an audio driver protocol by Steinberg. While it is available on multiple operating systems, it is most commonly used on Windows to work around limitations of WASAPI including access to large numbers of channels and lower-latency audio processing.

CPAL allows for using the ASIO SDK as the audio backend on Windows instead of WASAPI. To do so, follow these steps:

  1. Download the ASIO SDK .zip from this link. The version as of writing this is 2.3.1.

  2. Extract the files and place the ASIOSDK2.3.1 directory somewhere you are happy for it to stay (e.g. ~/.asio).

  3. Assign the full path of the ASIOSDK2.3.1 directory to the CPAL_ASIO_DIR environment variable. How to set persisting Environment Variables on Windows. The existence of the CPAL_ASIO_DIR environment variable determines whether or not CPAL will attempt to build the ASIO SDK and generate bindings to it.

  4. Download and install LLVM from here under the "Pre-Built Binaries" section. The version as of writing this is 7.0.0.

  5. Add the LLVM bin directory to a LIBCLANG_PATH environment variable. If you installed LLVM to the default directory, this should work in the command prompt:

    setx LIBCLANG_PATH "C:\Program Files\LLVM\bin"
    
  6. If you don't have any ASIO devices or drivers availabe, you can download and install ASIO4ALL. Be sure to enable the "offline" feature during installation despite what the installer says about it being useless.

  7. Loading VCVARS. rust-bindgen uses the C++ tool-chain when generating bindings to the ASIO SDK. As a result, it is necessary to load some environment variables in the command prompt that we use to build our project. On 64-bit machines run:

    "C:\Program Files (x86)Microsoft Visual Studio 14.0VC\vcvarsall" amd64
    

    On 32-bit machines run:

    "C:\Program Files (x86)Microsoft Visual Studio 14.0VC\vcvarsall" x86
    
  8. Select ASIO as the backend at the start of our program with the following code:

    #[cfg(target_os = "windows")]
    {
        cpal::os::windows::use_asio_backend().expect("Failed to select ASIO backend");
    }
    

    If you run into this error:

    cpal::os::windows::use_asio_backend().expect("Failed to use asio");
                       ^^^^^^^^^^^^^^^^ did you mean `use_wasapi_backend`?
    

    Make sure that CPAL_ASIO_DIR is set correctly and try cargo clean.

In the future we would like to work on automating this process to make it easier, but we are not familiar enough with the ASIO license to do so yet.