-
Notifications
You must be signed in to change notification settings - Fork 3.5k
Add support for running output directly in Audio Worklet #25942
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
base: main
Are you sure you want to change the base?
Conversation
39ec937 to
c983f22
Compare
- Skip caching of JS output in the presence of user JS libraries. - Include our core js files, since changing them should invalid the cache. Followup to emscripten-core#25942
- Skip caching of JS output in the presence of user JS libraries. - Include our core js files, since changing them should invalid the cache. Followup to #25942
kripken
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm % comments
1b5c31f to
bc31c4f
Compare
675d266 to
c4c6ef7
Compare
lindell
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From my limited experience, it LGTM.
One thing that we might want to add to the docs in some way is to make it clearer in some way that AUDIO_WORKLET and ENVIRONMENT=worklet is two different things?
a39ca89 to
0fbc359
Compare
|
I added some docs. |
There are some use cases where its useful to be able to run emscripten generated code in an audio worklet without building with `-sAUDIO_WORKLET`. One major one is for deploying in a context where shared memory not available (i.e. no cross origin isolation) Fixes: emscripten-core#25943, emscripten-core#25943
0fbc359 to
b8a7ed3
Compare
|
@juj, thoughts on this before we land? |
There are some use cases where its useful to be able to run emscripten generated code in an audio worklet without building with
-sAUDIO_WORKLET. One major one is for deploying in a context where shared memory not available (i.e. no cross origin isolation)Fixes: #22979, #25943