Supersonic Alternatives
Similar projects and alternatives to supersonic
-
-
Kargo
Stop Scripting Promotions. Start Shipping with Kargo. Kargo automates promotion across dev, staging, and prod with approval gates and verification. Open source, built by the team behind Argo CD. Download now.
-
-
-
-
-
SonicWeb
Sonic Pi in the browser — same play, sleep, live_loop. SuperCollider synthesis via Supersonic. No install.
-
tritoncha
REPL-Driven live music synthesis environment with reactive 3D visuals with ClojureScript, Tone.js and Three.js.
-
AppSignal
Monitoring that respects your time & budget. APM, error tracking, and dashboards for modern web apps. Ten-minute setup, transparent flat pricing, and support from engineers who actually use the product.
supersonic discussion
supersonic reviews and mentions
-
Sonic Pi
Of course - and it's what I've been working hard on in the background for the past year.
I ported SuperCollider's scsynth to Web Audio workouts (https://sonic-pi.net/supersonic/demo.html) late 2025, built an experimental spike called Sonic Tau (https://sonic-pi.net/tau). Then I wrapped SuperSonic in a native audio framework and used it to replace scsynth in Sonic Pi v5.
I'm now working on a new audio DSP engine building on this learning which combines my favourite aspects of scsynth and Erlang which I'll be discussing and revealing over on my Patreon over the coming months (https://patreon.com/samaaron)
-
Sonic Pi v5 Released
> In postMessage mode the client and the engine run in separate execution contexts with no shared memory, exchanging serialised OSC - the browser enforces that boundary the same way the kernel does between processes on a socket.
You won't convince anyone that a WASM module running in an AudioWorklet should be considered a separate application.
If you respect the SuperCollider project, you should also respect its license. The virality of the GPL is the point. Instead of trying to find loopholes, just follow the spirit of the license.
> Also, the JS and Erlang clients are entirely my own code and copyright surely their licence isn’t in question.
Those parts that do not directly reference scsynth (or derived) code can indeed be released under the MIT license.
However, SuperSonic as a whole must be licensed under the GPL since it's a combined work and not a mere aggregate.
> I think the question you’re actually raising is what obligations fall on users who combine their software with SuperSonic. You already state that my approach in Sonic Pi is fine.
Yes, but your approach with SuperSonic is not. In fact, it seems like you are actively encouraging other people to embed scsynth without following the GPL:
> Your application code interacts only with the MIT-licensed client APIs and is not intended to be a derivative work of the GPL components.
https://github.com/samaaron/supersonic#license
> It is the project author's good-faith interpretation that application code
Stats
samaaron/supersonic is an open source project licensed under GNU General Public License v3.0 or later which is an OSI approved license.
The primary programming language of supersonic is C++.
Popular Comparisons
Sponsored