Open patrick99e99 opened 5 months ago
I believe that the support we have for audio worklets (-sAUDIO_WORKLET
) is fundamentally linked to use of SharedArrayBuffer (since its is based on WASM_WORKERS, which is based on SharedArrayBuffers).
@juj can confirm.
Please include the following in your bug report:
Version of emscripten/emsdk:
I am building with the following flags:
And when I attempt to call the
Module()
function, it is blowing up with:This comes from the code that is attempting to reference SharedArrayBuffer:
I don't know if this is considered desired behavior? Am I supposed to not attempt to instantiate that
Module
function ifcrossOriginIsolated === false
?I also was wondering if there is any way to tell emscripten to not use the SharedArrayBuffer for web audio?
I found that google has a sample webaudio + webassembly project that uses an audioworklet without requiring
crossOriginIsolated
.. But they are not using any of theemscripten_create_wasm_audio_worklet_node
oremscripten_create_wasm_audio_worklet_processor_async
that I am, rather, they are manually building the audio context and using a .js class for their worklet class... So I was wondering if there's any way to still leverage emscripten to use c++ for setting up audio context + worklets but not be required to have those headers set?