Skip to content

fix cartesia error when input text is empty #3080

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

Merged
merged 1 commit into from
Aug 5, 2025

Conversation

longcw
Copy link
Contributor

@longcw longcw commented Aug 5, 2025

cartesia tts returns an error {'type': 'error', 'context_id': '49c376fe1e6a', 'status_code': 400, 'done': True, 'error': 'transcript empty or contains only punctuation: first transcript for WS is empty or contains only punctuation'} when input text is empty.

ignore the error message if done is True.

fix #3084

@longcw longcw requested a review from a team August 5, 2025 04:20
@davidzhao
Copy link
Member

why would we push an empty string through the TTS? is it related to the TTS pacing change?

@longcw
Copy link
Contributor Author

longcw commented Aug 5, 2025

why would we push an empty string through the TTS? is it related to the TTS pacing change?

no, it's from LLM when it's a tool call without message. before we ignored this error message. I exposed the cartesia error in #3028 but it actually should check done first to ignore such cases.

@longcw longcw merged commit 26792f4 into main Aug 5, 2025
23 checks passed
@longcw longcw deleted the longc/fix-cartesia-error-on-empty-message branch August 5, 2025 15:13
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.

Cartesia TTS Error on function calls
3 participants