Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

API v0.2 #12

Open
micahscopes opened this issue Jun 24, 2021 · 1 comment
Open

API v0.2 #12

micahscopes opened this issue Jun 24, 2021 · 1 comment

Comments

@micahscopes
Copy link

Is it reasonable for me to think of WAM 0.2 as an API for sending meaningful messages to/from/between AudioWorklet processors?

@jariseon
Copy link
Member

v02 api provides two layers: the higher level layer is accessible from the main thread JS code, while the lower level layer operates at the audio thread side. the hosting web page/app calls the higher level JS apis to load the plugin, to set/get its presets and params, push midi etc. these calls are routed to the lower level api, which in turn forwards them to the wasm module instance.

the api is thin and it only supports most common audio plugin use cases. v02 thus provides means for messaging to/from AudioWorklets, but messaging between AudioWorklets is excluded and left for the host responsibility.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants