elementary VS react-juce

I don't know which library you're using, but I use Elementary Audio for my audio projects. This looks like a great fit.

Well I m a js dev in life, I recently discovered this library https://www.elementary.audio/, which at first stable release does a pretty good job, I did little experiments and it seems pretty promising

And check out this new native audio implementation with JS !!! https://www.elementary.audio/

Great recommendations in here, and I'm happy to see this thread getting such attention!

This is totally a shameless self-plug, but I think it could be interesting for you:

I'm working on a project called Elementary Audio [1] which is a javascript runtime + framework for writing native audio software. It's like the Web Audio API in that it's javascript+audio, but unlike Web Audio in that it aims to target true native audio apps, like plugins for your DAW or hardware projects.

The API that it offers feels to me very much like thinking and working in analog synths, which is why I think you might find it interesting. You can describe and wire up signals and just see what they sound like without having to worry about what needs to happen under the hood for you to hear it.

I put together a guide for dipping your toes into making sound [2] and you'll find there a bunch of other resources that I recommend for getting into the topic.

I should note too that it's currently in beta and only supports macos and linux (windows coming soon!)

[1]: https://www.elementary.audio/

Funny you should say that :) I'm currently building a small drum synth, will share it as soon as its ready.

In the mean time, check out https://github.com/nick-thompson/elementary for some examples that you can `npm install && npm start` to hear

If you're keen to stay with HTML/CSS-like UI, then you might want to look at react-juce, which is a React frontend for JUCE. It will likely be more familiar to you than using JUCE directly, though it is not the same as using actual HTML/CSS.

It's probably helpful to have some background context for the development of this

The author of this library is also the author of the React JUCE renderer. It's a toolkit that re-uses React Native's rendering engine to allow you to use JS and React to render JUCE components:

https://www.nickwritesablog.com/blueprint-a-juce-rendering-b...

https://github.com/JoshMarler/react-juce

So at this point, you have a (presumably) C++ JUCE app that is using JS/TS to render the UI. Why not work to move DSP stuff into JS as well, so that you're gluing minimal bits of C++ together?

It's not a far leap from there to here when you follow this down the road.