6 ms·
It's hard to know what to say. > The conventional approach to writing audio software is an challenging process requiring expertise in a wide breadth of topics–
by PaulDavisThe1st 5y ago
It's hard to know what to say.
> The conventional approach to writing audio software is an challenging process requiring expertise in a wide breadth of topics– C++, multi-threading and thread safety, lock-free programming, and realtime thread safety come to quickly to mind, and we haven't even mentioned digital signal processing itself. Moreover, the tooling, workflow, and developer experience that we have in this approach pales in comparison to that of the web software industry, for example. All together, the reality of these complications is that the conventional approach for writing audio software is difficult and time consuming. We believe it doesn't have to be that way.
This is then followed by a screenshot of some code that looks like a SuperCollider script from 15 years ago.
There are at least a dozen audio "scripting" languages that free someone from all the issues mentioned above. Many have been mentioned in the thread already. The only things that Elementary Audio appears to have in its favor are that it leverages JS and it runs in the browser (sort of).
For some people, those two alone will be interesting. Have at it, people!
But for people who write plugins designed to run inside DAWs, or modules inside Rack, and in particular for the people who write DAWs or Rack (or Rack-like things), this is of approximately zero interest. It's a web-centric version of SuperCollider, which is cool but ultimately so bounded by the limitations of the platform that for many things, SuperCollider or something similar remains more powerful and more flexible.
- iainctduncan 5y agoThat was my impression too, it looks very much like an SC style computer music language. Which begs the question, who is this for? Someone who writes plugins doesn't need or want the high level SC style language. Someone seriously into computer music/audio isn't going to want the limitations, and has a lot of options already to choose from that are mature, if relatively unknown outside music circles. If it were my company, I would be marketing this squarely at people with the need for high level procedural audio in a web context. This looks like it could be great for browser-based game devs, for example. I do know that Pure Data and Andy Farnell's great sound design book for it were a hit in the game dev world of procedural audio, FWTW.
- aaaaaaaaaaab 5y agoIt's probably for people who are smart enough to know DSP, but only know JavaScript and refuse to learn anything else. If you squint it looks like an empty set.
- chaosprint 5y agoSC is typical OOP language. From this perspective, the raw Web Audio API or Tone.js are more relevant for SC. This Elementary Audio prefers FP, which makes it quite different and I think it has the potential to be very friendly for beginners. But the docs need a lot of more works there.
- PaulDavisThe1st 5y agoCan you provide an example of where SC syntax and Elementary/JS syntax for the same thing differ in a significant way?
- chaosprint 5y ago```Elementary JS core.render(el.cycle(440)); ``` ```SuperCollider { SinOsc.ar(440) }.play ```
- PaulDavisThe1st 5y agoIf that seems "quite different" to you, then good luck! Personally speaking, SC's approach seems more amenable to composition (in the programming, not the musical sense). Collapsing everything down to core.render() puts the emphasis in the wrong place IMO. The oscillator is better considered to be an independent entity, and the "render" step really ought to be implicit. But to each, their own!
- chaosprint 5y agoIt really depends on your angle. for example, "1 + 1" in FP is different from "1 + 1" in OOP. In FP, everything is func. 1 is func; + is a combinator. In OOP, 1 is an obj, + is the method of that obj that takes another obj. It looks like you really enjoy SC's syntax. It's great. But essentially, the language is just one part of SuperCollider. SuperCollider = sclang + scsynth sclang -> OSC msg -> scsynth The scsynth is actually the soul of SuperCollider to many computer musicians and that is what drives many to develop different language front-ends for scsynth. Language is just a wrapper, with different programming paradigms. But down to the lower abstraction, it's the audio graph. I have no connection with Elementary js at all but I think it does a good job for providing a new angle for Web audio. Yet I understand your concern of using it for developing vst plugins.
- Archit3ch 5y ago> SuperCollider or something similar remains more powerful and more flexible SuperCollider's license effectively stops you from designing commercial products. Even the free version of Elementary allows that.
- PaulDavisThe1st 5y agoWell, if you plan to release a commercial product based on writing JS, compiling that to WASM, running somehow inside or alongside a C/C++ core engine also compiled to WASM, both running in some standalone WASM environment ... good luck! Elementary looks like a nice playground for audio if you have a web-leaning bent. Just like SuperCollider is a nice playground for audio if you are familiar with some its fundamental assumptions. Neither of them seem appropriate to be the basis of products I would charge someone for, other than maybe as a one-off custom tool of some sort.
- abetusk 5y agoWhat are you talking about? SuperCollider is licensed under GPLv3 [1]. [0] https://github.com/supercollider/supercollider#license https://github.com/supercollider/supercollider#license
- NateEag 5y agoExactly. Any product you produce must include full source code, at which point anyone can legally post all your code on the internet. So - very difficult to build a commercial software product with it.
- PaulDavisThe1st 5y agoThe entire source code of Ardour is posted on the Internet. Nevertheless, it has no known bad-intent copies, and generates more than US $200k/yr. It is also the basis of two products generally viewed as "commercial", even though they are also GPL-licensed. Almost all of the source code of VCV Rack is posted on the Internet. There have been a few forks for specific reasons, but it's almost certainly the most widely used software modular synthesis in existence, and has created both a paying job for its creator and a mixed libre/paid ecosystem for module developers. The entire source code of Vital, one of the most acclaimed software synthesizers of 2021 is posted on the Internet. The author (Matt Tytel) makes a living from his work. The definition of commercial might be a little wider than you think. Finally, there are several ways to use SC in a product that do not involve the GPL. You fire up sclang as a separate process, feed it SC code, and sclang controls the server. Nothing you write is linked to anything GPL licensed.
- 8f2ab37a-ed6c 5y agoAs a total outsider to the audio programming world, what's the best in class framework / environment to be writing plugins in in 2022 if one were to start today?
- JodieBenitez 5y agoJUCE is a common choice in commercial audio/music software. https://juce.com/ https://juce.com/
- PaulDavisThe1st 5y agoJUCE is also reasonably popular among GPL'ed plugins, since it does allow for a GPL option. It's not perfect, and in fact has many important issues, but it's probably the least bad of a bunch of not-very-good options (no matter what type of license you're planning to use).
- JodieBenitez 5y agoYes... although the Projucer does not make it very obvious since it only shows "personal", "education", "indie" and "pro" license options. This page does mention GPL3: https://juce.com/get-juce https://juce.com/get-juce
- chaosprint 5y agoAs an alternative to JUCE, you can use write VST with Rust, using EGUI lib: https://github.com/DGriffin91/egui_baseview_test_vst2 https://github.com/DGriffin91/egui_baseview_test_vst2 Audio lib choice: - https://github.com/RustAudio/dasp https://github.com/RustAudio/dasp - https://github.com/SamiPerttu/fundsp https://github.com/SamiPerttu/fundsp - https://github.com/chaosprint/glicol https://github.com/chaosprint/glicol Typically, you can use MIT license in Rust community. In this video demo, you can even live coding audio effect in DAWs with Glicol as VST plug-in, built with EGUI: https://youtu.be/tmmBhBmIEW0 https://youtu.be/tmmBhBmIEW0 Apparently, you can use the same combo to make your own.
- 5y ago
- iainctduncan 5y agoI guess another thought, mind you, is that Elementary doesn't need to succeed for hard core audio devs in order for it to succeed as a business - it just needs enough people who think they will succeed. If this turns out to be a great tool for casual or beginner plugin devs, I could see that being a valid market. Witness the explosion of casual Ableton Live plugin devs from Max for Live. I'm sure the vast majority of JUCE licenses don't wind up becoming sustaining businesses too, and the barrier to entry is a lot higher there. Whether those folks will get to the point of paying a license fee is the million dollar question I guess. Ain't nothing wrong with selling pickaxes to miners and all that....
- PaulDavisThe1st 5y agoOverall I think these are all fair points. Still, I think that we have an obligation towards non-hard-core audio devs (whatever that actually means) to remind them that if you want to find gold you likely need a pickaxe, but if you want to turn over a field, you need a plough. It's not important that everyone's efforts become successful businesses. What seems more important to me is two-fold: 1. the existence of suitable entry points for "non-hard-core audio devs" 2. if it isn't possible to provide those entry points using the same tools that the "hard-core audio devs" would use, to be sure that the "non-hard-core" folks understand that there is a difference and that there is a smooth migratory pathway between the two worlds. On that front, Elementary looks fairly good, other than its fairly strong claims that this is a suitable technology for creating commercial audio plugins. Let's be honest: the main thing that gets in the way for "old school" technologies these days is just compilation. Perry Cook's synthesis toolkit is a very old bundle of C++ modules that lets you do more or less the exact same thing that Elementary does. But being C++ means that there's a build step (which may generate errors). For people more familiar with interpreted languages like JS and its cousins, this appears to have become an almost insurmountable obstacle. If you can't just type it and run it, it's crap. I think that's wrong, but I understand the appeal of "type and run" for people starting out on the path of "make the computer do what I want".