Use usermappings in chat instead of generic diarization names #294
Conversation
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
If the db contains usermappings for the session these are sent to the LLM instead of generic names.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This is an update to PR #288
If the db contains usermappings for the session these are sent to the LLM when using the chat, instead of generic diarization names.
In the PR #288 generic diarization name where sent to the LLM in the chat.
This PR first checks the db and if it exists any usermappings for the current session it replaces OriginalSpeaker with CustomName before sending the transcription to the LLM in the chat.
This way you can reference the real names in the chat, if you have renamed the generic names.