Support for verbose_json for audio transcriptions #199
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.
What
This pull request addresses a bug in the current implementation of the
verbose_json
option for OpenAI's audio transcription API. It also extends theAudioTranscriptionResult
format to support the additional parameters returned whenverbose_json
is enabled, such as word-level and segment-level timestamps.Why
The
verbose_json
option in OpenAI's audio transcription API provides valuable information for synchronizing the audio with the transcription. By fixing the bug and extending theAudioTranscriptionResult
format, developers can easily access and utilize the timestamp data and other parameters to create synchronized audio-transcription experiences.Affected Areas
audio/transcription:
AudioTranscriptionResult
format has been extended with optional values to accommodate the additional data provided by theverbose_json
option.timestampGranularities
was added toAudioTranscriptionQuery