mach/libs/sysaudio
Stephen Gutekanst dfcfc20db8 sysaudio: use mach-sysjs via package manager
Signed-off-by: Stephen Gutekanst <stephen@hexops.com>
2023-05-19 08:36:44 -07:00
..
.github all: update pull request template to reflect new libs/ dir 2022-08-26 15:12:04 -07:00
examples sysaudio: improve backend selection; remove i8 sample support (#767) 2023-04-30 16:36:39 -07:00
libs sysaudio: use mach-sysjs via package manager 2023-05-19 08:36:44 -07:00
src mach: update to @min/@max (std.math.min/max is going away) (#774) 2023-05-16 01:36:13 -07:00
.gitattributes all: move standalone libraries to libs/ subdirectory 2022-08-26 15:12:04 -07:00
.gitignore all: move standalone libraries to libs/ subdirectory 2022-08-26 15:12:04 -07:00
build.zig sysaudio: use mach-sysjs via package manager 2023-05-19 08:36:44 -07:00
build.zig.zon sysaudio: use mach-sysjs via package manager 2023-05-19 08:36:44 -07:00
LICENSE all: move standalone libraries to libs/ subdirectory 2022-08-26 15:12:04 -07:00
LICENSE-APACHE all: move standalone libraries to libs/ subdirectory 2022-08-26 15:12:04 -07:00
LICENSE-MIT all: move standalone libraries to libs/ subdirectory 2022-08-26 15:12:04 -07:00
README.md sysaudio: better explanation 2023-04-05 03:30:34 -07:00
sdk.zig sysaudio: use mach-sysjs via package manager 2023-05-19 08:36:44 -07:00

mach/sysaudio - cross-platform low-level audio IO in Zig

This repository is a separate copy of the same library in the main Mach repository, and is automatically kept in sync, so that anyone can use this library in their own project if they like!

Experimental

This is an experimental Mach library, according to our stability guarantees:

Experimental libraries may have their APIs change without much notice, and you may have to look at recent changes in order to update your code.

Why this library is not declared stable yet

Join the community

Join the Mach community on Discord to discuss this project, ask questions, get help, etc.

Issues

Issues are tracked in the main Mach repository.

Contributing

Contributions are very welcome. Pull requests must be sent to the main repository to avoid some complex merge conflicts we'd get by accepting contributions in both repositories. Once the changes are merged there, they'll get sync'd to this repository automatically.