rnnoise VS procedural-gl-js

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

Nice writeup, I always like it when the shaders are highlighted like this. I got started in a similar way 7 years ago and have been making 3D terrains with THREE.js & WebGL since.

The real fun begins when you need to implement some sort of Level-of-Detail system and streaming in data to give the illusion of high detail everywhere without sacrificing performance.

Last year I released an open-source framework (https://github.com/felixpalmer/procedural-gl-js) for creating 3D terrains for web applications, you can see Uluru here: https://www.procedural.eu/map/?longitude=131.036&latitude=-2... (unfortunately the aerial imagery from our default provider isn't as high resolution as other places in Europe)

Great visualization and approach with compressing the tile data. Do you have a comparison of how much smaller the payload ends up being compared to simply sending PNG files?

I use PNGs to encode elevation data in my 3D mapping library (https://github.com/felixpalmer/procedural-gl-js/) and this does a pretty good job of compressing the data, for example in the ocean the PNG files are also very small as the image is mostly black. Different use case I now as your data is much more sparse, but I wonder how close the PNG compression would be compared to your approach.

Yeah, the React parts of this are very minimal. I'm not really sure what using it gets you, since it just manages a single div.

The _actual_ library that does all the work is here: https://github.com/felixpalmer/procedural-gl-js

- Tiny filesize means library is parsed fast. Package size is less than THREE.js thanks to code stripping

Check it out on Github: https://github.com/felixpalmer/procedural-gl-js/

The imagery comes from the Orthofoto dataset on https://www.basemap.at/ - the actual texturing is done by the Procedural GL JS library https://github.com/felixpalmer/procedural-gl-js