Earlier quoted context omitted.
> Do you understand that low-enough-latency audio doesn't take a super computer anymore It never did. Low latency audio has almost nothing to do with CPU power. Here's a summary of some of the issues faced on modern general purpose computers: https://manual.ardour.org/setting-up-your-system/the-right-c... I know how WASM and Web workers work. Since nothing you can do in WASM or a web worker has anything to do with ei…
And even when it doesn't require it, we always want it . :-)
Elementary Audio: a modern platform for writing high performance audio software
61–70 of 110 posts
Re: Elementary Audio: a modern platform for writing high performance audio software
#62It'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 ap…
> 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.
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.
Re: Elementary Audio: a modern platform for writing high performance audio software
#63Earlier quoted context omitted.
And even when it doesn't require it, we always want it . :-)
And even when we set it, we don't get it, because we blithely read a "latency" label in a GUI instead of measuring the round-trip latency on the specific device in question.
1. time from an acoustic pressure wave reaching a transducer (microphone), being converted to a digital representation, being processed by a computer, being converted back to an analog representation and finally causing a new acoustic pressure wave care of another transducer (speaker).
2. time between when someone uses some kind of physical control (mouse, MIDI keyboard, touch surface, many others) to indicate that they would like something to happen (a new note, a change in a parameter) and an acoustic pressure wave emerging somewhere that reflects that change.
The first one is "roundtrip" latency; the second one is playback latency.
Re: Elementary Audio: a modern platform for writing high performance audio software
#64It'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 ap…
> 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.
Re: Elementary Audio: a modern platform for writing high performance audio software
#65>high performance audio software >runs in browser doubt.gif
Re: Elementary Audio: a modern platform for writing high performance audio software
#66Earlier quoted context omitted.
It does say you can make plugins, but the link doesn't work. It would be huge if you could make cross-platform AU/VST*/AAX without the costs of JUCE, but I suspect that isn't on offer here.
still not convinced you can make cross-platform plugins without JUCE by using iPlug, Faust or even Rust the selling point of this seems to allow js/web developers to build plugins and we already know what happened when web developers were allowed to build desktop apps (Electron) luckily given real-time and cpu constraints this might never happen to Audio Plug-ins
Re: Elementary Audio: a modern platform for writing high performance audio software
#67Earlier quoted context omitted.
This is my new favorite comment for illustrating the perilous future of general computing and how it needs to be taken away from JavaScript if we have any chance of survival. Electron, Webassembly fetishism, the pursuit of language synchrony at the expense of common sense, it all gets you this. This comment. Right here. This is the future of software and it should scare the shit out of you. Let me get this straight:…
I'm a web person defending web things but providing something on the web has a significant advantage. I know you've heard this again and again, but I can't emphasize it enough. You can use the site from most platforms, including PCs and mobiles. You don't have to install software, a single click is enough. Of course, browsers have considerable limitations, and serious users will eventually choose other tools, but pro…
In the audio world that is cool for toys.
There are a lot of really cool things to play with in the browser/multi media space, maybe this is another.
But when it comes to getting shit done, writing plugins and transports, creating instruments and rigs for live use (my hobby these days) the quite demeaning comments here are on the mark.
This "Elementary" is prioritising the wrong things. And there are a lot of frame works that do not require you know C or C++
Pure Data, and Sonic Pi are two I have played with (the former much more than the latter).
Platform independence is simply not an issue when building these systems. Installing software is not an important issue.
Sorry. This is, on the face of it, a waste of time. I hate saying that, but if it were me doing this I would pitch it as a fun toy.
Re: Elementary Audio: a modern platform for writing high performance audio software
#68Maybe I'm missing something from my quick read, but the idea of using this for plugins seems like a real misfire. I'm curious whether the devs come from the pro audio world at all. It's one area where prioritizing for development time by using high level garbage collected languages just isn't done because your user is always concerned with how many instances they can run and what the lowest latency they can get is, a…
my friend is running an independent studio, i'm a bedroom musician, and we're planning some elementary plugins together. we tried some stuff with max and it wasn't expressive enough, we tried the steinberg sdks but they were too much of a lift, elementary is good enough for our workflows and in that perfect zone with enough control and enough familiarity that we feel we can be productive. we'll see in due time if it'…
Re: Elementary Audio: a modern platform for writing high performance audio software
#69It'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 ap…
Re: Elementary Audio: a modern platform for writing high performance audio software
#70The 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 line of thinking down the road.