cpal VS Clippy

debugging this nightmare bc its blocking my hobby project. by far the most fucked up issue ive encountered since i started rust.

There is a cross-platform audio library for Rust: cpal https://github.com/rustaudio/cpal

cpal crate should work fine for this use case, though it might be unnecessarily low-level for your use case.

I had to do something similar to this a while back. I used cpal.

Working on a live performance software that would let our band have live real-time practices over the internet. Top priority is minimum latency, so I'm trying to hook it up through ASIO. Not much luck yet. I've tried cpal, but I've run into numerous known random bugs (and some versions don't compile for me). At least I confirmed that I can push the audio through a TCP socket successfully.

With https://github.com/RustAudio/cpal you can access the microphone in a cross platform way, but you’ll get values of range [-1,1] out only. To calculate absolute decibels you would need to calibrate for your specific microphone with a known source.

source of example

you need to use a "loopback" device, as shown here - https://github.com/RustAudio/cpal/pull/478 (note, ive only tested this on windows - if its not supported on linux you could always plug your sound card output into its line-in/mic jack)

I couldn't find it in the API guidelines either. From what I understand, the idea is that any trait bounds, which includes generic type parameter bounds and lifetime bound on a type (struct or enum) would be repeated back in the impl block

there is a nice discussion on this issue here: https://github.com/rust-lang/rust-clippy/issues/1689

You should not blindly follow clippy lints. They are sometimes wrong. Another example https://github.com/rust-lang/rust-clippy/issues/9782 .

I often write () = f() to assert that f() is unit. Unfortunately clippy warns on such code ( https://github.com/rust-lang/rust-clippy/issues/9048 ). There are very recent pull requests for this bug, so hopefully this bug will be fixed very soon. But meanwhile I invented this workaround: [()] = [f()] :)

Apart from running clippy on many projects being essential, clippy is also an exceptionally welcoming project, no matter your prior knowledge.

clippy is a great place to get started :) though it isn't exactly new.

clippy is also pretty compiler-adjacent and unlike rust-analyzer uses rustc's internal APIs. Don't let the size of the code base scare you off! It's actually feasible for a newcomer to contribute even such a substantial change as a new lint, and we have issues labeled as "good first issue" that come with mentorship, so you don't need to go it alone.

Yes, you could use it to write a lint. Although you might find it easier to just fork Clippy and add your own lints to their existing framework.

Check out the readme for more information.

They are two of my favorite Rust tools. If you haven’t tried them yet, I highly recommend giving them a try. Clippy can detect various lints in your code and guide you towards writing more idiomatic code. To install Clippy, simply run rustup component add clippy, and to run it within your workspace, execute cargo clippy. For more details, visit Clippy’s GitHub repository.