Skip to content
Discussion options

You must be logged in to vote

The standalone server exposes a binary WebSocket at /asr. A client opens that socket, sends encoded audio bytes, or 16 kHz mono s16le PCM when the server uses --pcm-input, reads the JSON updates, then sends an empty binary frame to finish.

The complete protocol is documented in docs/API.md. A headless file example is available with:

wlk --pcm-input
wlk-test recording.wav --live

The bundled browser UI captures the microphone. Capturing Zoom, Teams, or general system output requires a loopback or virtual audio device that your client can read and forward. The bundled Chrome extension can capture audio from a browser tab.

Replies: 2 comments 7 replies

Comment options

You must be logged in to vote
7 replies
@radry
Comment options

@CorentinvdBdO
Comment options

@radry
Comment options

@QuentinFuxa
Comment options

@radry
Comment options

Comment options

You must be logged in to vote
0 replies
Answer selected by QuentinFuxa
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
4 participants