Fix: modify recognize_whisper_api according to the new version of the OpenAI API
#736
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
|
Seems like a duplicate to this! |
Oh, I apologize, I forgot to check if there was already a fix, I fixed it for a little app and thought it would be good to send it. Please check that PR and approve it if it is ok ☺ |
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 addresses the deprecation of the
audio.transcribeendpoint, which is no longer functional. The updated code now utilizes theaudio.transcriptions.createendpoint for speech recognition tasks. This change involves the creation of a new client to interact with the updated endpoint, ensuring the continued functionality of our audio transcription services.