WebAudioPlugins
WebAudioPlugins copied to clipboard
micbuffa
WebAudioPlugins SDK + examples
Hey all -- been heavily investigating this technology, have a thought / question. Ultimately it will take time for the Web-based DAWs to come into stability and production ready builds....
The restriction to name plugin entry file name as `main.js` won't work for most cases, different environments would use different entries, ex. es5 / es2019 / ts versions.
It will be great to have the SDK to be written in TypeScript or at least have `d.ts` files. working with APIs especially with custom ones would be way more...
Currently, the proposal includes the load mechanism for GUI of a plugin built-in, however this might be not the best solution because: - Restricts to use specific way of building...
There is a common place to distribute JS / FE / WA modules via `npm` - we could introduce a custom field for `package.json` file to describe plugins. With this...
The DX / performance of loading plugin process, it requires to load metadata and then it creates a custom node, what if it will work more like this: ```js const...
`AudioNode.prototype` override creates a problem of possibly unexpected way of how Web Audio works and that is considered as a bad practice in JS.
The code that is shown in README examples will be nice cleanup, I could prepare a PR if you don't mind