Skip to content

feat(murf): default TTS to Falcon 2.1 and Gordon voice - #8707

Open
gaurav-murf wants to merge 1 commit into
livekit:mainfrom
gaurav-murf:main
Open

gaurav-murf wants to merge 1 commit into
livekit:mainfrom
gaurav-murf:main

Conversation

@gaurav-murf

Copy link
Copy Markdown
Contributor

No description provided.

@gaurav-murf
gaurav-murf requested a review from a team as a code owner November 20, 2026 19:30

@devin-ai-integration devin-ai-integration Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

Devin Review

@tinalenguyen tinalenguyen left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hi, thanks for the PR! left a question about the default style

TTSDefaultVoiceId = "en-US-matthew"
TTSDefaultVoiceStyle = "Conversation"
TTSDefaultVoiceId = "Gordon"
TTSDefaultVoiceStyle = "Conversational"

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

since this default applies whenever style isn't passed, users with their own voice now get Conversational sent too, but some voices (e.g. Matthew) only list Conversation. does the API fall back for those, or could we only use the default style with the default voice?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Murf TTS resolves unsupported styles to the closest matching style available for the selected voice. So Conversational should resolve to Conversation for voices like Matthew, and vice versa. This should not cause any issues with Matthew.

This branch has not been deployed

No deployments
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

Successfully merging this pull request may close these issues.

2 participants