Supplementing transcription hint #15
Merged
Conversation
This file contains 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
|
Thanks for the contribution I'll look into merging it in a few days. |
|
Merged, it seems to work, but Gladia lacks more documentation on how to use it. In the future I'm open to merging more API parameters like this one. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 PR is to supplement the transcription_hint parameter to the Gladia API.
https://docs.gladia.io/chapters/speech-to-text-api/pages/live-speech-recognition
Testing it in Japanese, I realised that the effect is limited, but saw some improvement. We may need more testing in western languages.
When the hint field in the config file is left blank, the API simply ignore it. Adding words in this field starts the hinting.