Replies: 1 comment
-
|
Replied on linkedIn |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
First of all, thank you for Murmure. I discovered the project recently and I find the philosophy very strong: local-first, privacy-focused, lightweight, open-source, and usable in real workflows.
I am an osteopath in France, and I am currently exploring a local workflow for clinical note-taking during consultations. My use case is not classic dictation only, but a real conversation between a practitioner and a patient.
Today, my ideal workflow would be:
One limitation for this kind of use case is speaker separation.
I was wondering if a lightweight diarization feature could be possible in Murmure, but maybe not as full generic diarization at first. My intuition is that a simpler approach could be enough for many medical / therapeutic use cases:
Instead of trying to identify every speaker in a complex meeting, Murmure could have a local “voice profile” mode.
Example:
Practitioner: …
Patient: …
For my use case, this would already be extremely useful. I do not need a perfect meeting diarization system with 5 or 6 speakers. I mostly need to know whether the speaker is the practitioner or the patient.
This could help a lot for:
Technically, I may be wrong because I am not a developer, but I was thinking about a lightweight local pipeline such as:
Some possible directions I have seen mentioned recently are:
The key idea would be to keep it aligned with Murmure’s philosophy:
I would love to know if this kind of feature seems realistic within Murmure’s architecture, especially since Murmure already uses Parakeet for local ASR and Ollama for local LLM post-processing.
Do you think a “local voice profile / me vs other speaker” mode would be technically possible, or would it be too complex / too heavy for the project?
Thanks again for your work. Murmure seems very promising for privacy-sensitive professional use cases.
Beta Was this translation helpful? Give feedback.
All reactions