-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Voice Experience Issue in Google Text to Speech (streaming_synthesize) #13405
Comments
Hi @AKSHILMY, I'm going to transfer this issue to the python-docs-samples repository which is the source of truth for the code sample Reference TTS Example. While running the code sample, I noticed that the response in Lines 789 to 792 in 8bdc5d2
Please can you confirm that the necessary header was created to play the audio file? Please can you share the specific code used to create the audio header? I created a code sample which contains the raw WAV file header (following the spec at https://docs.fileformat.com/audio/wav/) to help with debugging.
|
Googlers see b/391302662 |
I wasn't able to re-create the issue reported in #13405 (comment), however follow up issues (GoogleCloudPlatform/python-docs-samples#13080 and internal issue b/391302662) were created to improve the samples documentation, specifically the guidance around creating the necessary header for the I'm going to close this issue as not reproducible but please feel free to open a new issue if the problem is still present. |
The use of Journey voices in normal TTS gives an engaging voice that attracts a user.
But when I use the same Journey voice in a streaming text input -> streaming audio output kind of way, the audio I get is a less engaging voice that just speaks out the stuff.
Why is it such ?
I don't find any way to control that.
Reference TTS Example
The text was updated successfully, but these errors were encountered: