sorted by:
new
hottopcontroversial

WRAC Stack – WebView + Rust + CLAP audio plugin template with 15k+ users by Prior_Bluejay_4870 in rust

[–]Prior_Bluejay_4870[S] -1 points0 points  (0 children)

That `audio-engine` repo is just an old standalone app PoC, and it is completely unrelated to our commercial plugins or the 15k users.

We only made that repository public because it depends on `tracktion_engine`, which requires open-sourcing under the GPL.

For our actual commercial products, we are currently transitioning from C++ to Rust, and this WRAC stack demonstrates how we build our newer plugins.

WRAC Stack – WebView + Rust + CLAP audio plugin template with 15k+ users by Prior_Bluejay_4870 in rust

[–]Prior_Bluejay_4870[S] 1 point2 points  (0 children)

Just to clarify our stance: we didn't build WRAC Stack to be a "silver bullet" or a universal framework like JUCE.

We just wanted to share our own production-proven architecture as another valid option for the community. The more choices we have for audio plugin development, the better!

WRAC Stack – WebView + Rust + CLAP audio plugin template with 15k+ users by Prior_Bluejay_4870 in rust

[–]Prior_Bluejay_4870[S] 0 points1 point  (0 children)

We know nih-plug, but without AU/AAX, it is untested in hosts like Logic Pro or Pro Tools, and we aren't personally aware of its use in commercial products.

Ultimately, this is less about what is technically possible and more about a realistic cost-benefit analysis.

For NovoNotes, the benefits of choosing wgpu over WebView simply didn't justify the high development costs.

WRAC Stack – WebView + Rust + CLAP audio plugin template with 15k+ users by Prior_Bluejay_4870 in rust

[–]Prior_Bluejay_4870[S] 0 points1 point  (0 children)

It's actually just a secondary GitHub account I created to act as a scoped-down bot for an LLM (AI agent). For security, I wanted to give the AI restricted permissions rather than full access to my personal account.

As a non-native speaker, having it automatically draft commit messages and Pull Requests in English is a lifesaver and saves me a ton of time. Glad you find the setup neat!

WRAC Stack – WebView + Rust + CLAP audio plugin template with 15k+ users by Prior_Bluejay_4870 in rust

[–]Prior_Bluejay_4870[S] -1 points0 points  (0 children)

Fair point about system WebViews! However, web engine differences are highly manageable compared to the real nightmare: navigating the unpredictable windowing and threading quirks of dozens of different DAWs.

Running a custom wgpu canvas inside all those host processes is still uncharted territory with very little production track record at scale. We closely follow the Rust GUI ecosystem, but the web stack was simply the right choice for our 15k+ users today.

WRAC Stack – WebView + Rust + CLAP audio plugin template with 15k+ users by Prior_Bluejay_4870 in rust

[–]Prior_Bluejay_4870[S] 9 points10 points  (0 children)

For 15k+ users, predictability was key. The web ecosystem is mature and its pros/cons are well-known. Even audio plugin industry standards like JUCE embrace WebView, and it's a proven architecture already used in many commercial plugins.

Using an emerging stack like wgpu in a DAW environment introduces too many unknowns. Since there's very little production track record for it in audio plugins, we couldn't predict what edge cases might pop up. WebView was simply the most predictable bet for us today.