I've been using this for a while (and occasionally post a preset on Patreon). This synth has some of the easiest to use built-in automation I've seen.
This is the third project that I've known with this name. The other two are an emacs incremental completion plugin:<p><a href="https://emacs-helm.github.io/helm/" rel="nofollow">https://emacs-helm.github.io/helm/</a><p>and a haskell functionally reactive game engine:<p><a href="http://helm-engine.org/" rel="nofollow">http://helm-engine.org/</a>
Would be awesome I could easily send it patches and MIDI messages from the browser via websockets to offload some of the heavier synth generation that the Web Audio API can't handle.
Have you ever heard of Kubernetes, a tool that is so much in the upswing that it dominated the last Amazon announcements, that Docker decided to integrate with it despite being its competitor in some regards, that hundreds of thousands of engineers suffer to use for some time now because our bosses heard it would be a cool thing at some conference (and bosses don't really care if such a software is finished or not)?<p>If so, you might want to reconsider the name of your tool/framework/whatever, because the name Helm is basically taken in many engineers' head.