Proof of concept implementation for OpenAI compatible API format #237
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.
Quick and dirty implementation of what it would look like to support OpenAI's API format. This is an attempt to satisfy #227.
Example OpenAI output from
/v1/audio/transcriptions
:Some notes:
json
,text
,srt
,verbose_json
, orvtt
.json
only has one key with "text", whereasverbose_json
includes other basic info.verbose_json
is used along withtimestamp_granularities[]
array to provide segments or word level timestamps. Since we always get segments, we have to throw those away whenjson
format is used.