-
Notifications
You must be signed in to change notification settings - Fork 5
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
this code is voodoo magic (question, not bug report) #2
Comments
I am not sure what you mean by "race condition"? Transferable Streams provides a means to transfer The code fetches multiple URL's and pipes each The purpose of the design is to implement an "infinite" (provided an idealized computer; or "circular buffer", e.g., re-writing indexes of a fixed-length |
The anonymous async function is used for the putpose of starting the async generator while not |
|
When I initially tried to upload the single WAV file GitHub did not allow. I created several files from the single file (WAV header can be included or excluded), thus the multiple Re
There are cases where
|
I used this code in a couple projects for chaining together fetch requests with some range headers. Works really well.. in one case I saw the writable being locked.. took me a while to get that the (async ()=>{ (await fetch()).body.pipeTo(writable) })() part.. |
This is one script that audioworklet reads a sequential queue of readablstreams generated by this method of shared transferable stream: https://github.com/yishengjiang99/ssr-bach/blob/master/js/src/proc2.ts server generally out paces audioworklet processing. |
let me be your apprentice. |
does this rely on some sort of race condition where the readable stream is neither locked or unlocked for the worker to transfer it to the worklet node?
The text was updated successfully, but these errors were encountered: