WAM: AudioWorklet setup sub optimal about iplug2

[jariseon]

would it be possible to have option whether to use "standard" AWP (where DSP is rendered in audio thread) or "powerhouse" (where DSP is rendered in Worker) implementation ?

i think powerhouse has definite use cases (like sample streaming from a virtual file system), but my concern is that since worker thread has lower priority than audio thread, it might be affected by what is going on in main thread. Also, SABs introduce latency (in chrome this is one buffer, in Firefox it at least used to be > 1 buffer) which needs to be compensated. edit: could also be because of worker thread priorities differ in browsers, might not be result of different SAB latencies.

[olilarkin]

i guess what really needs to be done is to profile the current implementation. I currently have this hack, which is not right and the main thing i want to fix..., how do you think I could have an equivalent of OnIdle() on the main thread in AWP

[olilarkin]

in answer to your question it may well be possible... need to experiment with this stuff

[jariseon]

iiuc you want to inform main thread that AWP is idle? AWP used to have state member and a notification message from AWP -> AWN. it was removed from spec, can't remember why that was, but i guess one workaround option is to call postMessage("set", "state", "idle") to notify the main thread Controller. And post another message when state changes, i.e., not for each buffer. Another way is to use a SAB, but then you'd need to poll in main thread.

[olilarkin]

OnIdle() is a regular poll on the main thread. Not sure how to set that up within AudioWorkletGlobalScope

[jariseon]

right, so host calls OnIdle() ? Web Audio API calls AWP periodically: first it checks if there are any messages, and if so, it invokes AWP.port.onmessage() for each message from main thread. right after that it invokes AWP.process(). currently there's only one thread in AudioWorkletGlobalScope, so it is impossible to do any processing between onmessage and process calls.

unless setTimeout is available in AWGS, but even if it is, it might not be a good idea to steal processing time from other AWPs.

[olilarkin]

closing this. may reopen in the future to provide powerhouse pattern as an option