libsoundio
libvips
Our great sponsors
libsoundio | libvips | |
---|---|---|
15 | 23 | |
1,843 | 8,958 | |
- | 1.4% | |
1.2 | 9.2 | |
9 days ago | 7 days ago | |
C | C | |
MIT License | GNU Lesser General Public License v3.0 only |
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.
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.
libvips
-
Building an online image compressor
After some research, I found libvips, a demand-driven, horizontally threaded image processing library. It is designed to run quickly while using as little as memory as possible.
- Libvips: A fast image processing library with low memory needs
-
Things you might not know about Next Image
Sharp is a fast and efficient image optimization Node.js module that makes use of the native libvips library.
-
Go Image Converting
h2non/bimg can handle both if the underlying libvips is compiled with support for both formats.
-
.Webp is the bane of my existence
if you're using linux (which it doesn't seem so) there's also vispdisp https://github.com/jcupitt/vipsdisp which is based on https://github.com/libvips/libvips which will likely take over how images are decoded in the future for everything, at least methodology wise.
-
How are responsive image sets are generated, stored, and managed server-side?
The magic happens by way of a library called Libvips, which contains an ultra-high-speed low-memory image resizer.
-
imagor v1 - a fast, Docker-ready image processing server in Go, libvips and more
imagor uses one of the most efficient image processing library libvips. It is typically 4-8x faster than using the quickest ImageMagick and GraphicsMagick settings.
-
[OSError] Cannot find pyvips library (DLLs)
Try the solutions here: https://github.com/libvips/libvips/issues/2479
-
Image library for fast read of huge Tif files?
in that case maybe take a look at https://github.com/libvips/libvips
-
My project: railstart app
libvips v8.6+ or ImageMagick for image analysis and transformations
What are some alternatives?
miniaudio - Audio playback and capture library written in C, in a single source file.
OpenCV - Open Source Computer Vision Library
portaudio - PortAudio is a cross-platform, open-source C language library for real-time audio input and output.
imagick - Go binding to ImageMagick's MagickWand C API
soloud - Free, easy, portable audio engine for games
sharp - High performance Node.js image processing, the fastest module to resize JPEG, PNG, WebP, AVIF and TIFF images. Uses the libvips library.
cubeb - Cross platform audio library
GD - GD Graphics Library
ZLib - A massively spiffy yet delicately unobtrusive compression library.
tesseract-ocr - Tesseract Open Source OCR Engine (main repository)
wgpu-native - Native WebGPU implementation based on wgpu-core
FreeImage - A custom distribution of FreeImage, with a CMake-based build system. Used by the Athena Game Framework.