mfcc-rust VS lockbud

hey, quick question. do you mind if I use your stft function in the speech preprocessing library I've been working on? we've been trying to add support for doing mel spectrograms to build a runner for openwakeword, but progress is pretty slow because I've been soloing something I really don't have the right background for(I've never directly studied or worked with signal processing)

So I've been working on an speech preprocessing library for rust for a minute now. The tl;dr is it contains functions related to preprocessing audio for use in speech-centric models. I've run into a situation where I'm running against a few conflicting design constraints and trying to figure out the best way to handle state for a set of functions.

we could always use contributors for mfcc-rust/speechsauce(we're planning on changing the name as it's not limited to just computing mfcc's).

The code has comments and in the GitHub issues is written what's missing, the goal is to mimic functionality from NumPy not present in NDArray (a library for maths operations). You can find the code here: https://github.com/secretsauceai/mfcc-rust. Take a look, if you feel that you can give a hand, that would be amazing!!! Let's make a new exciting voice future!!!

This release represents the first phase in the wakeword project, we are working on a Rust wakeword engine based on Precise and a SpeechPy MFCC port in Rust so that user's can run the wakeword easily on their phone and other devices. It is hard to believe that there aren't any current good solutions to running a modern FOSS wakeword engine on a phone in real time. We want to change that and allow everyone access to this technology, with their own wakeword of choice.

There's tracing-mutex that builds a dag of your locks when you acquire them and panics (at runtime) if it could deadlock: https://github.com/bertptrs/tracing-mutex

parking_lot has a deadlock detection feature for when you deadlock that iirc tells you what deadlocked (so you're not trying to figure it out with a debugger and a lot of time) https://amanieu.github.io/parking_lot/parking_lot/deadlock/i...

I also just found out about https://github.com/BurtonQin/lockbud which seems to detect deadlocks and a few other issues statically? (seems to require compiling your crate with the same version of rust as lockbud uses, which from the docs is an old 1.63 nightly build?)

Hi, I'm looking for tools that can statically detect possible deadlocks in async fns. I'm aware of lockbud and cargo-check-deadlock, neither of which can analyse async code. Is there any tools that support this?

Try this: https://github.com/BurtonQin/lockbud.