The Web Audio API as a Standardized Interface Beyond Web Browsers

Matuszewski B, Rottier O. The Web Audio API as a Standardized Interface Beyond Web Browsers. J Audio Eng Soc. 2023;71(11):790-801. doi:10.17743/jaes.2022.0114

@article{Matuszewski2023_22344,
  author = {Matuszewski, Benjamin and Rottier, Otto},
  title = {{The Web Audio API as a Standardized Interface Beyond Web Browsers}},
  journal = {Journal of the Audio Engineering Society},
  volume = {71},
  number = {11},
  pages = {790--801},
  year = {2023},
  month = nov,
  publisher = {Audio Engineering Society},
  doi = {10.17743/jaes.2022.0114},
  url = {https://doi.org/10.17743/jaes.2022.0114}
}

TY  - JOUR
TI  - The Web Audio API as a Standardized Interface Beyond Web Browsers
AU  - Matuszewski, Benjamin
AU  - Rottier, Otto
T2  - Journal of the Audio Engineering Society
J2  - J. Audio Eng. Soc.
VL  - 71
IS  - 11
SP  - 790
EP  - 801
PY  - 2023
DA  - 2023/11/06
DO  - 10.17743/jaes.2022.0114
UR  - https://doi.org/10.17743/jaes.2022.0114
PB  - Audio Engineering Society
LA  - en
AB  - In this paper, the authors present two related libraries, web-audio-api-rs and nodeweb-audio-api, that provide a solution for using the Web Audio API outside the Web browsers. The first project is a low-level implementation of the Web Audio API written in the Rust language, and the second provides bindings of the core Rust library for the Node.js platform. The authors' approach here is to consider Web standards and specifications as tools for defining standardized APIs across different environments and languages, which they believe could benefit the audio community in a more general manner. Although such a proposition presents some portability limitations due to the differences between languages, the authors think it nevertheless opens up new possibilities in sharing documentation, resources, and components across a wide range of environments, platforms, and users. The paper first describes the general design and implementation of the authors' libraries. Then, it presents some benchmarks of these libraries against state-of-the-art implementation fromWeb browsers, and the performance improvements that have been made over the last year. Finally, it discusses the current known limitations of these libraries and proposes some directions for future work. The two projects are open-source, reasonably feature-complete, and ready to use in production applications.
ER  -