You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Feature description
A feature request regarding sample rate:
When receiving audios from the TTS node using googleTTS, the audios come with a sample rate of 24'000 Hz. My devices receive audios (not only tts) from several sources and cannot switch between sample rates. Therefore it would be great to be able to set the sample rate either in the node or as input parameter.
Expected behavior
Either a field in the node setup called 'sample rate' or a parameter in a msg would be great. Though I think a setting in the node would suffice.
TTS-Ultimate Version
2.0.7
Are you running node-red behind homematic, docker or anything similar?
standalone on small linux server
Thanks for considering!
Cheers
JR
The text was updated successfully, but these errors were encountered:
Hi Giovane!
Feature description
A feature request regarding sample rate:
When receiving audios from the TTS node using googleTTS, the audios come with a sample rate of 24'000 Hz. My devices receive audios (not only tts) from several sources and cannot switch between sample rates. Therefore it would be great to be able to set the sample rate either in the node or as input parameter.
On the google TTS REST API reference I found that it is generally possible:
https://cloud.google.com/text-to-speech/docs/reference/rest/v1/AudioConfig
The parameter
sampleRateHertz
in theAudioConfig
needs to be set for this. TheAudioConfig
ist part of the request body according to:https://cloud.google.com/text-to-speech/docs/reference/rest/v1/text/synthesize
Expected behavior
Either a field in the node setup called 'sample rate' or a parameter in a msg would be great. Though I think a setting in the node would suffice.
TTS-Ultimate Version
2.0.7
Are you running node-red behind homematic, docker or anything similar?
standalone on small linux server
Thanks for considering!
Cheers
JR
The text was updated successfully, but these errors were encountered: