-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: calculate audio transcription cost #7601
Comments
@ishaan-jaff @krrishdholakia Any suggestions on these issues? I can create a pull request to try to resolve these issues |
Hey @liuhu i missed this |
@krrishdholakia according to your suggestions #7610 (comment) I've split the PR, cloud you help me review and approve them. #9649 #9648 #9647 |
@krrishdholakia @ishaan-jaff I've created new PRs based on @krrishdholakia suggestions 💯, any other comments? |
What happened?
1. custom_pricing not working for stt model.
The model config:
the root reasons:
SPECIAL_MODEL_INFO_PARAMS
not containsinput_cost_per_second
, and we also need to addoutput_cost_per_second
for tts modellitellm/litellm/litellm_core_utils/litellm_logging.py
Lines 2560 to 2575 in 55139b8
litellm/litellm/types/router.py
Lines 373 to 378 in 55139b8
2.
model_prices_and_context_window_backup.json
not contains some groq stt modelswhisper-large-v3, whisper-large-v3-turbo, distil-whisper-large-v3-en
3. when i fix 1 and 2 on above issues, appear response_cost Exception
curl:
some error log for
response_cost
:Exception: This model isn't mapped yet. model=whisper-1, custom_llm_provider=groq. Add it here - https://github.com/BerriAI/litellm/blob/main/model_prices_and_context_window.json.\n
The root reason:
groq use
OpenAIAudioTranscription
and it is hard code to set model name and provider in transcription handlerlitellm/litellm/llms/openai/transcriptions/handler.py
Line 145 in 55139b8
4. groq stt miss some unit test
Relevant log output
Are you a ML Ops Team?
Yes
What LiteLLM version are you on ?
v1.56.9
Twitter / LinkedIn details
@Hugo_Liu_X
The text was updated successfully, but these errors were encountered: