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.

Sign up for GitHub

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

Jump to bottom

problems loading the new m.wasmmodule.js into the worklet #3

Closed

frantic0 opened this issue Apr 2, 2019 · 1 comment

Assignees

frantic0 commented Apr 2, 2019

know for sure it is inclusion of m.wasmmodule.js but can't get any hints about why it is failing (silent error!)

commented out the maxiSample embinding but it didn't work.

do a manual inspection of the m.wasmmodule.js and compare it with the functional ones.

frantic0 self-assigned this

Author

frantic0 commented Apr 2, 2019

fixed, the m.wasmmodule.js was not exporting the Module.

Learned lessons:

m.post.js need cleaning
catching errors with the node processor code into the worklet is quite difficult, no meaningful feedback ([audioworklet] Error handling in AudioWorkletGlobalScope WebAudio/web-audio-api#1282, https://github.com/GoogleChromeLabs/web-audio-samples/blob/gh-pages/audio-worklet/basic/node-onerror.html, context.audioWorklet.addModule() returns DOMException: The user aborted a request. WebAudio/web-audio-api#1581)
when inspecting the m.wasmmodule.js (90k lines, previously 50k lines), start from the bottom where our code is appended and compare with a functional version.

frantic0 closed this as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment