feat: [whisper] Partial support for verbose_json format in transcribe endpoint #721
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
mudler
changed the title
mudler
approved these changes
Jul 4, 2023
1 task
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.
Extend the current output to be compatible with the
custom_jsonformat referenced in the OpenAI docsThis PR basically adds an extra field in response: 'segments', which contains text divided by time segments.
These changes can be useful for other tools that expect segmented text like some automatic subtitles or other tools like Buzz
Although support is not complete, those changes are enough to get Buzz working at least. More work is needed to perfectly support
custom_jsonformat.