You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Is it reasonable for me to think of WAM 0.2 as an API for sending meaningful messages to/from/between AudioWorklet processors?
The text was updated successfully, but these errors were encountered: