rnnoise VS LIPS

Sure.

Carla: https://github.com/falkTX/Carla

It lets me install any normal audio pro audio plugins, for example https://github.com/xiph/rnnoise

It also does some cable management, but qpwgraph is maybe better for that.

I looked at your code and the approach (IMO) is kind of bad.

If you want to solve the problem of "voice changer", you can skip the UI entirely and just use plugin parameters. You can also skip the problem of managing the connections. And when you publish your work, every pro audio software (Ableton, Reaper, whatever) can use your audio processing.

Hope that helps.

Interesting! How does it compare with NoiseTorch/RNNoise?

Das ist eine open source lib. Damit sollte das klappen. https://github.com/xiph/rnnoise/blob/master/examples/rnnoise_demo.c

RNNoise (behaves similarly to RTX broadcast/voice/whatever the fuck they're calling it now, but with significantly better performance) - plugs into OBS or other programs flawlessly

OBS ships with rnnoise noise reduction, which is like NVIDIA Broadcast, but works on any CPU. See also NoiseTorch and EasyEffects if you're on Linux.

It's pretty great, works decently, but the sad thing is the author put it out a few years ago, wrote a paper and then moved onto something else and it's pretty much unmaintained and requires some very specific ML knowledge.

https://github.com/xiph/rnnoise

I found this tool https://github.com/xiph/rnnoise and this guide that doesn't have ubuntu guide https://medium.com/@gamunu/linux-noise-cancellation-b9f997f6764d

Sweet, I'll have to give that a go :)

Another option in browser land is lips[0], which exclusively targets a js backend.

[0] https://lips.js.org

For Scheme implementations there are LIPS and biwascheme. I haven't done more than play around with them, so I can't really give an informed opinion about pros and cons or favorites.

Your example revealed a bug in my Scheme interpreter. This is an example that fails to match:

In my interpreter, LIPS Scheme, vector literal syntax is created using a syntax extension, a token that is mapped to a function or a macro. So you can use things like this:

I'm not sure about other Scheme interpreters but in my interpreter LIPS Scheme, there is (env) function that returns a list of symbols. You can also access environment objects e.g. (current-environment) return object that is used internally. And you can even access the scope chain because the env object has __parent__ property that returns the parent scope.

Few of my Open Source projects: * jQuery terminal * LIPS Scheme * Gaiman * Sysend * Wayne

(define promise (--> '>(fetch "https://lips.js.org/") (then (lambda (res) (res.text))) (then (lambda (text) (. (text.match #/\s*([^>]+?)\s*<\/h1>/) 1)))))

ngl when I first saw the headline my first thought was, “Wait, bring CAR into JavaScript? Make it a Lisp? But hasn't it already been done?”

Languages like Biwa Scheme and LIPS Scheme are good for running Scheme in the browser. But I would prefer compiling Scheme code to JavaScript in the server, then serving the compiled JavaScript image to the browser.