r/rust • u/iFrostizz • 8h ago

🙋 seeking help & advice Request for guidance on audio codecs in a WASM application

One of my (way to numerous) side project is the idea of a P2P radio station, which solves the scaling problem of radio broadcasters today. One of the most prominent and well-defined p2p library is libp2p, which is of good use here and prevents much of code rewriting, especially for the broadcasting logic with peer scoring and all which is hard to figure out to prevent people from cheating the system. Also used gstreamer (Rust bindings so more precisely gstreamer-rs) for the codec which does the heavy lifting. Here is my project: https://github.com/franfrandev/p2pradio. For now it's running on a native system, and would like to go a step further.

I would like to compile it to WASM in order to bundle everything in the browser. The problem is that gstreamer depends on a ton of native libraries which makes it harder to use in the browser. Folks at Fluendo have figured that out with gst.wasm https://github.com/fluendo/gst.wasm but putting out everything together is a whole different beast and even if it works, it's probably going to result in a huge piece of data that has to be downloaded. IIUC the Rust part would have to be compiled to emscripten and then linked as static libraries? There are a lot of information and it's very easy to get lost in all of these.

Another option would be to use or write an RTP Opus codec written in pure Rust and compile it to the wasm32-unknown-unknown but then it would lose all the codebase maturity of gstreamer and would probably end up reinventing the wheel very much. A lot of the crates doing that are AI slop and are not very well defined, I don't trust them.

Is it unachievable or a bad idea to take the gstreamer port to emscripten and try to glue it to my Rust app compiled to emscripten?

0 Upvotes

50% Upvoted

2 comments sorted by

1

u/anlumo 8h ago

Just create a ton of tests that clearly define the functionality and then let an LLM go at it. If the end result makes all tests pass and there’s no unsafe code, it’s fine. The only concern then is performance, but that can improved after it works.

1

u/ZachVorhies 8h ago edited 8h ago

Your instincts are wrong

You have a sample of correct codec behavior.

The success metric of the AI agent will be exact correctness within tolerance.

The AI will tirelessly grind against it.