Repository navigation
Run your Python in Web Workers: a small kit - #10
Merged
Merged
Conversation
workers/host.js starts Pyodide workers, hands a canvas to one and relays its input, relays Web MIDI, and owns the AudioContext; workers/python_worker.js boots Pyodide in each worker; workers/audio_worklet.js plays what an audio worker sends, with a queue that adapts to the machine. docs/workers.md shows how to use it.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When an app redraws a lot and also has to react on time (Web MIDI, live audio, fast input), a long redraw on the page's main thread delays everything else.
workers/lets the app's Python run in Web Workers while the page stays thin:workers/host.js(the page): starts workers, hands a canvas to one of them as anOffscreenCanvasand relays its pointer, wheel and key events, relays Web MIDI to the workers that ask, and owns theAudioContext.workers/python_worker.js(each worker): loads the vendored Pyodide, installs your wheels, copies your files in, runs your module.workers/audio_worklet.js(the audio thread): plays the 256-frame blocks an audio worker sends, with a queue that starts at 1,536 frames, works down to 768 when the machine keeps up and backs off after any dropout.On the Python side it pairs with pydevices'
displaydev.workerdisplay(withboard_configs/workerdisplay),audiodev.worklet_audioandmidiports.webmidi.relay_ports.docs/workers.mdshows the whole setup. Nothing about the default single-thread template changes.