openWakeWord VS Clippy

https://github.com/dscripka/openWakeWord

Balancing wake reliability vs false wake activation is a tricky balance. OWW is decent but could certainly be better.

It's used with Home Assistant now so I expect the training data and implementation overall to get significantly better fairly soon.

There's also OpenWakeWord[0]. The models are readily available in tflite and ONNX formats and are impressively "light" in terms of compute requirements and performance.

It should be possible.

[0] - https://github.com/dscripka/openWakeWord

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)

potentially build another runner for open wakeword

here's what's on the pipeline next: - finish mel-spectrogram implementation - publish initial version on crates - move python caching rust side - finish implementing in the precise rust port - potentially build another runner for (open wakeword)[https://github.com/dscripka/openWakeWord] - build an android app that supports user-defined wakewords and has some popular defaults to load. ps not a voice assistant, just the thing that activates the voice assistant.

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.