feat: Transcribe output from audio devices to keyboard or a file #34
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.
These changes allow you to transcribe the audio you are listening to rather than the microphone.
I find this especially useful for transcribing and translating meetings without having to rely on the meeting software having these features built in.
The transcription can be written to a file and you can use any software to read that file. Also I'm considering doing something in LocalAI so you can view a log of transcriptions there or do some further processing on them.
From the new README:
Example Workflow: Transcribing an Online Meeting or Video Stream
To create a transcript of an online meeting or video stream by capturing system audio:
List available capture devices:
Identify the monitor device, e.g., "Monitor of Built-in Audio Analog Stereo".
Start the daemon specifying the device and output file:
VOXINPUT_CAPTURE_DEVICE="Monitor of Built-in Audio Analog Stereo" ./voxinput listen --output-file meeting_transcript.txtNote: Add
--no-realtimeif you prefer the HTTP API.Start recording:
Play your online meeting or video stream; the system audio will be captured.
Stop recording:
The transcript is now in
meeting_transcript.txt.