miniaudio
libsoundio
Our great sponsors
miniaudio | libsoundio | |
---|---|---|
27 | 15 | |
3,601 | 1,843 | |
- | - | |
8.5 | 1.2 | |
13 days ago | 12 days ago | |
C | C | |
GNU General Public License v3.0 or later | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
miniaudio
- MiniAudio.h: single-file audio playback and capture library for C and C++
-
Amiga/Linux: Jurassic Boing Edition
Unfortunately, I can't currently capture any videos (I added miniaudio.h to play back the Jurassic Park theme song) since I had to move my mom into my home (she's getting a divorce from her narcissistic husband soon and the guy lost his marbles and locked her out of her own home) and it's late at night currently.
-
Audio Library
miniaudio - so far the best entry in cross platform audio. It is a stack allowing to use device alone, decoders and mixers, or node based engine for sophisticated audio processing. Extensible where it should be. Written in C, so there are no creature comforts of having C++. Aways can be wrapped to get advantage of RAII.
-
Implementing libraries
So, I wanna implement this library to the source engine. Is that possible? And also, since source is based on SDL, is it possible for me to implement Nuklear on my source game?
-
Simple High-Level Audio APIs
The most straightforward lib for this is miniaudio. It's straightforward,l to use and easy to integrate into a build system.
-
Dunno if anyone else will find this useful
You give little clues what this is… so cl-miniaudio defines CFFI bindings to https://miniaud.io/ which is "an audio playback and capture library for C and C++. It's made up of a single source file, has no external dependencies and is released into the public domain." and is cross-platform.
-
Title: Release: miniaudio version 0.11.12
Get the update on GitHub: https://github.com/mackron/miniaudio
-
Nuklear – A single-header ANSI C immediate mode cross-platform GUI library
* Miniaudio - A single header file audio library https://miniaud.io/
Both (actually, not just three systems) cross-platform.
For their design and cross-platform support they make for great bases for Go libraries, unlike most C code out there.
- What's the best audio library for c++?
-
Simple way to interface with Windows 10 audio in C (not C++)?
I've used this library before: https://miniaud.io/
libsoundio
-
Audio Engineer Looking to Change Careers
Audio DSP is definitely the deep end of the pool. I believe the Zig programming language owes its creation to Andrew Kelley (the creator) trying to write stuff for an audio workbench going "damn, this is really hard to do with C, why does C suck so much" and just creating a language that's like C but without the bad parts to do it himself. I'm not joking, this is literally the origin of Zig as I've heard it from a podcast, and here is Andrew's old audio lib for proof: https://github.com/andrewrk/libsoundio
-
How can I record and cut a sound in c++
http://libsound.io is a great cross platform library for reading and writing to sound cards. i have used it successfully on macos and i’m sure it supports linux and possibly windows too. you will probably also need lib audio for reading and writing to files.
-
Learn Enough C to Survive
Hmm... after some research it seems that I've misunderstood Zig's situation a bit. Zig has introduced null-terminated string types a couple of years ago, but still encourages you to do most string operations with slices instead. Let me explain:
Zig's string literals (which you create with parenthesis like "Hello world!") are null-terminated byte arrays, expressed as the type const [N:0]u8 (where the :0 tells you that it's null-terminated), whereas the more typical array might be written as const [N]u8. The reason for this feature is not because the language wants you to use null-terminated strings, but because these static strings need to be stored in the global data section of the ELF executable, and these require you to use null-termination. But if you want to do any mutable operation with this string, you need to convert this into a proper slice (ptr + size). And it seems like Zig developers don't really use null-terminated types that much at the API level, but use it for things like C interop or cases where you really need it for special optimizations.
Noting that from the PR that introduced this feature, Andrew Kelley writes:
> I think you will find that the Zig community in general (and especially myself) agrees with you on this [null-terminated strings being fragile], and APIs in general should prefer slices to null terminated pointers. Even if you are using Zig to create a C library, and even in actual C libraries, I would recommend pointer and length arguments rather than null terminated pointers, like this: https://github.com/andrewrk/libsoundio/blob/1.1.0/soundio/so...
> That being said, I want to repeat what I said earlier about null terminated pointers: A null terminated array is not inherently an evil C concept that is intruding in the Zig language. It's a general data storage technique that is valid for some memory constrained use cases. I also stumbled on a Real Actual Use Case inside LLVM. The bottom line for me is that null terminated pointers exist in the real world, and especially in systems programming. You can see this in interfaces with the operating system in the standard library...
So he acknowledges null-terminated strings can certainly be useful in certain situations outside of legacy reasons, which is good to know. And Zig creating a special type for this shows that a good systems language needs to be designed to accommodate the needs of the outside world.
-
Ask HN: Cross platform method for accessing system audio output?
Perhaps you could use either http://libsound.io/ or SDL2 game library + SDLAudioIn (http://burningsmell.org/sdl_audioin/) which provides low-level APIs to access operating-system sound systems like Alsa, PulseAudio, PipeWire, and CoreAudio (not sure how well it is supported by SDL2).
Comparison: https://github.com/andrewrk/libsoundio/wiki/libsoundio-vs-SD...
- Libsoundio – cross-platform audio input and output
-
Is programming truly for me?
Fun fact: Andrew Kelley, the creator of the Zig programming language, kind of created it so he could work on audio processing.
-
libsoundio: why does one sine play without cuts, but adding another or more produces periodic-like clicks?
Based on: https://github.com/andrewrk/libsoundio/blob/master/example/sio_sine.c
-
Library for detecting if a user is speaking into the microphone
Does this fit your needs? https://github.com/andrewrk/libsoundio
-
Jam live with your friends with Svelte!
I listened to the Co-recursive podcast the other day that featured Andrew Kelley, the creator of the Zig programming language. Before Zig he developed Libsoundio - https://github.com/andrewrk/Libsoundio, to solve problems around realtime audio.
-
Mach Engine: The future of graphics (with Zig)
Audio will probably come later, but libsoundio will be the first thing in terms of groundwork. Integrating that in the same way we've integrated GLFW, so you can just cross compile and get cross-platform audio to boot.
What are some alternatives?
portaudio - PortAudio is a cross-platform, open-source C language library for real-time audio input and output.
soloud - Free, easy, portable audio engine for games
ffmpeg-kit - Fork of https://github.com/arthenica/ffmpeg-kit
cubeb - Cross platform audio library
cdecrypt - Decrypt Wii U NUS content — Forked from: https://code.google.com/archive/p/cdecrypt/
ZLib - A massively spiffy yet delicately unobtrusive compression library.
raylib-php - PHP 8 Bindings to raylib
libvips - A fast image processing library with low memory needs.
ffmpeg-kit - FFmpeg Kit for applications. Supports Android, Flutter, iOS, Linux, macOS, React Native and tvOS. Supersedes MobileFFmpeg, flutter_ffmpeg and react-native-ffmpeg.
wgpu-native - Native WebGPU implementation based on wgpu-core