Skip to content
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

Request to add a speech-to-text model for the fireworks supplier #10422

Closed
4 of 5 tasks
BryceWG opened this issue Nov 7, 2024 · 1 comment
Closed
4 of 5 tasks

Request to add a speech-to-text model for the fireworks supplier #10422

BryceWG opened this issue Nov 7, 2024 · 1 comment

Comments

@BryceWG
Copy link

BryceWG commented Nov 7, 2024

Self Checks

  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue,否则会被关闭。谢谢!:)
  • Please do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

Request to add an ASR model for the fireworks supplier, offering an excellent model such as whisper v3 turbo, and providing lower latency and reduced cost.

2. Additional context or comments

The model request document page is: https://fireworks.ai/models/fireworks/whisper-v3-turbo

3. Can you help us with this feature?

  • I am interested in contributing to this feature.
Copy link

dosubot bot commented Dec 8, 2024

Hi, @BryceWG. I'm Dosu, and I'm helping the Dify team manage their backlog. I'm marking this issue as stale.

Issue Summary:

  • You requested the integration of the "whisper v3 turbo" speech-to-text model.
  • Highlighted benefits include lower latency and cost efficiency.
  • Provided a link to the model's documentation for reference.
  • No further comments or activities have occurred on this issue.

Next Steps:

  • Please let us know if this issue is still relevant to the latest version of the Dify repository by commenting here.
  • If there is no further activity, this issue will be automatically closed in 15 days.

Thank you for your understanding and contribution!

@dosubot dosubot bot added the stale Issue has not had recent activity or appears to be solved. Stale issues will be automatically closed label Dec 8, 2024
@dosubot dosubot bot closed this as not planned Won't fix, can't repro, duplicate, stale Dec 23, 2024
@dosubot dosubot bot removed the stale Issue has not had recent activity or appears to be solved. Stale issues will be automatically closed label Dec 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant