-
Notifications
You must be signed in to change notification settings - Fork 60
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
[voice_text] Call rosservice from python instead of bash #166
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@itohdak nice work, could you rewrite text2wave
which python?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
btw, did anyone have some trouble with this? I do not think you're only one user for voice_text package.
@k-okada I rewrote |
The trouble around this is a little bit complex as I commented in #167. About two weeks ago, @Affonso-Gui and @708yamaguchi told me that the don't-speak issue had been occurring with the Fetch robot too. I'm not sure for the PR2 robot. @knorth55 |
@itohdak both issue does not happen in PR2. |
@knorth55 Sorry. We have not discussed online, so I have no link I can show you. @furushchev first found the gstreamer issue and taught us the workaround. On Fetch, the gstreamer issue was actually solved with applying this solution. My version of gstreamer is as below.
|
rosservice call
with bash command sometimes gets stuck when executed one after another.Instead of using
rosservice call
with bash command, this PR calls the service through Python node.