Rust could certainly handle much of the audio pipeline, but using Rust everywhere would not automatically make the application simpler or more reliable. Other

Rust could certainly handle much of the audio pipeline, but using Rust everywhere would not automatically make the application simpler or more reliable. Other options may be available but for me FFmpeg provides mature, well-tested support for decoding, transcoding, resampling, mixing, and muxing across a wide range of formats. Web Audio handles synchronized multitrack playback, per-stem gain, mute and solo, metering, looping, speed control, and the browser-based mobile interface. Since the separation model already depends on Python and PyTorch, rewriting the surrounding audio stack in Rust would not remove the largest runtime dependency. As for RUst itself its currently used for the Tauri desktop shell and process lifecycle. A native Rust audio engine may make sense later if it produces a measurable improvement in latency, memory use, or reliability, but replacing proven components purely for architectural consistency would add considerable complexity. For the vibe coding part: AI tools have assisted with development, and I am transparent about that. However, the architectural choices are deliberate, the code is reviewed, and the project has automated backend and browser testing. I would still welcome specific technical criticism or examples of places where the current design is causing real problems. That's where my background kicks in, seasoned musician here with over 25+ year working on IT industry, so as i like to joke, im the maestro of the orchestra :) On another words. i actually know how to cook , but to do it faster i need the assistances otherwise as a family man, I would never have the time to ship that and help my kid on a useful time.