-
Notifications
You must be signed in to change notification settings - Fork 582
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
TextToSpeechLongAudioSynthesizeClient AudioConfig does not honour speakingRate
nor any settings
#4148
Comments
Hey @nickaws,
google-cloud-node/packages/google-cloud-texttospeech/protos/protos.d.ts Lines 786 to 790 in 94ea195
|
Hi @danielbankhead ! this actually made no difference, and even throws "'Request contains an invalid argument.'," with the code above (which worked sometimes) |
@nickaws to clarify, the request should look like this: const operation = await texttospeechClient.synthesizeLongAudio({
voice: {
name: "en-US-Wavenet-J",
languageCode: 'en-US'
},
input,
audioConfig: {
audioEncoding: "MP3",
speakingRate: 0.5,
// pitch: 1,
},
outputGcsUri: "gs://somebucket/file.mp3"
}); Does this request not work for you?
I'm not sure how a request parameter would fail sometimes; are there any additional details here? |
@danielbankhead I am very sorry for the cryptic message. The code I put when I opened the ticket, generated an mp3 but crashed with "Request contains an invalid argument.'" right now, the same code, with the new request works sometimes (it does generate the mp3, but just sometimes, i am varying the name of the mp3 file of course), sometimes fails with -- using latest sdk.
We also were looking at https://github.com/googleapis/google-api-nodejs-client/blob/main/discovery/texttospeech-v1.json#L175 seems there's a parameter missing, but what is funny, is that something it does generate the mp3. Full code nick@nick text-to-speech-node % node -v
|
Thanks for stopping by to let us know something could be better!
PLEASE READ: If you have a support contract with Google, please create an issue in the support console instead of filing on GitHub. This will ensure a timely response.
Please run down the following list and make sure you've tried the usual "quick fixes":
If you are still having issues, please be sure to include as much information as possible:
Environment details
Steps to reproduce
Please include any and all code and/or steps related to reproducing the bug.
Speaking rate nor pitch are honoured.
Making sure to follow these steps will guarantee the quickest resolution possible.
Thanks!
The text was updated successfully, but these errors were encountered: