3 ms·
Very interesting. Must admit I don't understand the calls like el.lowshelf( ... in the example. Is el related to the user interface or does it already describ
by moritzwarhier 5y ago
Very interesting.
Must admit I don't understand the calls like el.lowshelf( ... in the example.
Is el related to the user interface or does it already describe signal processing in some declarative way?
At first glance, I thought the actual processing is invoked when core.render is called.
Anyway, maybe I just have to read more about the project or watch the video.
- acjohnson55 5y agoSeems like it's an object that contains factories for instantiating new audio processing stages and connecting it to the graph at creation-time.
- moritzwarhier 5y agoThat makes sense, thanks
- fenomas 5y agoFrom checking the video, it's the default export of one of the project's core libraries. I gather it's meant to be in scope for all use of the project.
- trypwire 5y agoOP here– good point, that's not well explained in the article! And thanks to the others who have answered already, you're pretty much spot on. The core library, referenced here as `el`, contains a set of factory functions for describing various underlying processing nodes. So when you write `el.lowshelf()` you're just using one of the builtins (like how you might use a div, span, or button in a web app with React)
- moritzwarhier 5y agoThank you very much! So I assume these factory functions still live in the JS world and provide some processed input / nodes for the actual audio rendering happening at the end of the chain?