-
Notifications
You must be signed in to change notification settings - Fork 4
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
Write wakewords and utterances in the dedicated thread #104
Comments
No recording
With recording
|
consideration, the save file path is included in the message.context, putting this in a thread will remove that info from downstream clients. eg, something could be parsing the audio for speaker recognition or something so using a thread should probably be a flag with this documented, it shouldnt be an issue most of time and can even default to using a thread. in hivemind context this info is useless too as the file path doesnt exist in both sides of hivemind connection |
Saving on NVMe drive is pretty transparent.
|
Make sure the audio files are written in a dedicated thread to avoid potential delays caused by poor storage.
Matrix dicsussion: https://matrix.to/#/!EOygeDJPfJQOfNacqH:matrix.org/$rPLrUZV32aoIcaDKb42-ycc8FvhAp-np8U8Id5UIgD8?via=matrix.org&via=mozilla.org&via=tchncs.de
The text was updated successfully, but these errors were encountered: