The "Text To Speech" feature in “Audio” utilities has the "voice" parameter modified to be a customizable variable type #14546

Closed
opened 2026-02-21 19:17:44 -05:00 by yindo · 1 comment
Owner

Originally created by @FeyaM on GitHub (Jun 10, 2025).

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.

The current text-to-speech generation feature, whether using the "audio" tool in the workflow or directly calling the "text-to-speech" function, cannot customize the voice after the workflow is published. However, in dialogue workflows, it is often necessary to use different voice lines based on different personas of intelligent agents, so the "voice" parameter needs to be passed as an argument for each call. This also allows models with voice cloning capabilities to dynamically pass voice URL links to generate custom voices.

2. Additional context or comments

No response

3. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @FeyaM on GitHub (Jun 10, 2025). ### Self Checks - [x] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [x] I confirm that I am using English to submit this report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [x] [FOR CHINESE USERS] 请务必使用英文提交 Issue,否则会被关闭。谢谢!:) - [x] 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. The current text-to-speech generation feature, whether using the "audio" tool in the workflow or directly calling the "text-to-speech" function, cannot customize the voice after the workflow is published. However, in dialogue workflows, it is often necessary to use different voice lines based on different personas of intelligent agents, so the "voice" parameter needs to be passed as an argument for each call. This also allows models with voice cloning capabilities to dynamically pass voice URL links to generate custom voices. ### 2. Additional context or comments _No response_ ### 3. Can you help us with this feature? - [ ] I am interested in contributing to this feature.
yindo added the stt & ttsperformance labels 2026-02-21 19:17:44 -05:00
yindo closed this issue 2026-02-21 19:17:44 -05:00
Author
Owner

@dosubot[bot] commented on GitHub (Aug 19, 2025):

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

Issue Summary:

  • You requested the ability to customize the "voice" parameter dynamically in the "Audio" utilities' text-to-speech feature.
  • This would allow different voices for intelligent agent personas and support dynamic voice cloning via URLs after workflow publication.
  • Currently, voice customization is fixed once a workflow is published, limiting flexibility.
  • There has been no further activity or comments on this issue since it was opened.
  • The issue remains unresolved.

Next Steps:

  • Please let me know if this feature request is still relevant to the latest version of Dify by commenting on this issue.
  • If I do not hear back within 15 days, I will automatically close the issue.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Aug 19, 2025): Hi, @FeyaM. I'm [Dosu](https://dosu.dev), and I'm helping the Dify team manage their backlog and am marking this issue as stale. **Issue Summary:** - You requested the ability to customize the "voice" parameter dynamically in the "Audio" utilities' text-to-speech feature. - This would allow different voices for intelligent agent personas and support dynamic voice cloning via URLs after workflow publication. - Currently, voice customization is fixed once a workflow is published, limiting flexibility. - There has been no further activity or comments on this issue since it was opened. - The issue remains unresolved. **Next Steps:** - Please let me know if this feature request is still relevant to the latest version of Dify by commenting on this issue. - If I do not hear back within 15 days, I will automatically close the issue. Thank you for your understanding and contribution!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#14546