We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
text2wave reads speaking_rate at first and sample launch file gives speaking_rate https://github.com/jsk-ros-pkg/jsk_3rdparty/blob/master/3rdparty/google_cloud_texttospeech/launch/google_cloud_texttospeech.launch#L46 . However, it seems that this speaking_rate cannot be given correctly.
text2wave
speaking_rate
The text was updated successfully, but these errors were encountered:
However, it seems that this speaking_rate cannot be given correctly.
this line does not have the effect?
jsk_3rdparty/3rdparty/google_cloud_texttospeech/bin/text2wave
Line 10 in 2776781
Sorry, something went wrong.
text2wave is not a rosnode. It is called from os.system in sound play node. Unfortunately, the ros namespace is not carried over to text2wave.
os.system
sound play node
The output for these change (https://github.com/iory/jsk_3rdparty/blob/268/3rdparty/google_cloud_texttospeech/bin/text2wave#L11-L12 ) is as follows.
$ roslaunch google_cloud_texttospeech google_cloud_texttospeech.launch japanese_speed:=0.25 [INFO] [1626085226.732977]: sound_play node is ready to play sound [Text2Wave] Speaking rate is 1.0 [Text2Wave] namespace "/"
@knorth55 in order to solve this issue, we need to make the tts module as plugin in sound_play.
sound_play
knorth55
No branches or pull requests
text2wave
readsspeaking_rate
at first and sample launch file givesspeaking_rate
https://github.com/jsk-ros-pkg/jsk_3rdparty/blob/master/3rdparty/google_cloud_texttospeech/launch/google_cloud_texttospeech.launch#L46 .
However, it seems that this
speaking_rate
cannot be given correctly.The text was updated successfully, but these errors were encountered: