No version for distro humble showing github. Known supported distros are highlighted in the buttons above.

Package Summary

Tags No category tags.
Version 0.3.3
License BSD
Build type CATKIN
Use RECOMMENDED

Repository Summary

Description This ROS workspace is created on Raspbian OS. Here I have installed ROS Kinetic from source using cross-compilation and worked on projects like Surveilling Robot.
Checkout URI https://github.com/iamrajee/roskinetic_catkin_ws.git
VCS Type git
VCS Version master
Last Updated 2022-03-04
Dev Status UNKNOWN
Released UNRELEASED
Tags cmake ros raspbian catkin raspberry-pi-3 realsense ros-kinetic gmapping-slam realsense-camera
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

sound_play provides a ROS node that translates commands on a ROS topic (

Additional Links

Maintainers

  • Austin Hendrix

Authors

  • Blaise Gassend

sound_play

Dependencies

  • python-pygame
  • festival
  • festvox-don
  • alsa-base
  • alsa-tools

Checking that the speaker/sound card is recognized by the kernel

cat /proc/asound/cards

Your card should be in the list. Make note of the number in front of the card, it will be used to tell alsa where to play sound from.

If your sound device does not show up, your kernel may not support it, or the module may not be loaded. For usb speakers, you may want to try:

modprobe snd-usb-audio

(not sure if this list is exhaustive)

Telling alsa which sound card/speaker to use

Run (replace 75 with the number of the sound device to use):

asoundconf set-default-card 75

This will create .asoundrc.asoundconf in your home directory. To make alsa use these settings, add the following line to ~/.asoundrc

include ".asoundrc.asoundconf"

To set this default to all users, copy this to the system-wide alsa configuration file:

mv ~/.asoundrc.asoundconf /etc/asound.conf

Getting started

Start the sound play node, and have a look at the scripts in the scripts directory that exercise the node’s functionality.

Specify Device via ROS Param

Besides setting default device as system wide settings, you can also specify audio device via rosparam:

<launch>
  <node name="soundplay_node" pkg="sound_play" type="soundplay_node.py">
    <param name="device" value="hw:1,0" />
  </node>
</launch>

or simply run: rosrun sound_play soundplay_node.py _device:="hw:1,0"

In the launch file above, ~device parameter is set to hw:1,0, which tells soundplay_node to use audio device No. 0 connected to audio card No.1. To find card/device number which you want to use, execute:

sudo aplay -l

CHANGELOG

Changelog for package sound_play

0.3.3 (2018-05-22)

  • Fix gstreamer errors. Fixes #108
  • Contributors: trainman419

0.3.2 (2018-05-02)

  • [sound_play] add option to select audio device to play / record (#87)

    • [sound_play] add option to select audio device to play
    • [sound_play] reformat README to markdown; add usage to set device via rosparam
    • audio_capture: add option for selecting device to use
    • audio_play: add option to select device for playing audio

    * add device argument to launch files Conflicts: audio_capture/launch/capture.launch audio_capture/launch/capture_to_file.launch audio_capture/src/audio_capture.cpp audio_play/launch/play.launch sound_play/scripts/soundplay_node.py

  • Merge pull request #95 from yujinrobot/volume_check [sound_play] volume check for cached sounds

  • [sound_play] checks if sound's Gst instance's volume has changed and resets it

  • Contributors: Austin, Naveed Usmani, Yuki Furuta

0.3.1 (2016-08-28)

  • Update to new gstreamer rosdeps
  • Update sound_play to gstreamer 1.0
  • remove chance of uninitialised variable being called in a subscriber callback.
  • Add changelogs
  • Issue: The error checks for missing publisher/action client in sendMsg were inverted. The non-blocking brach tested the action client while the blocking branch tested the publisher. Fix: Inverted the blocking boolean for both branchs.
  • sound_play: Fix build with -DCATKIN_ENABLE_TESTING=OFF. https://bugs.gentoo.org/show_bug.cgi?id=567466
  • [soundplay_node] fix resources not being released on dict cleanup This was resulting in the number of sink inputs reaching the maximum threshold, (32 on ubuntu 14.04 with pulseaudio 4.0) after which no more sounds could be played by the node. It would only happen if the rate of sounds being played was slower than the dictionary cleanup.
  • depend on actionlib.
  • Introduce unit test to ensure soundclient is started correctly.
  • Example of using the explicit blocking parameter to override the class setting.
  • SoundClient can also explicitly specify whether or not to block while playing the sound. Each play/repeat/say/... method can take an option blocking=True|False argument (using **kwargs), which over-rides the class-wide setting.
  • Merge pull request #62 from felixduvallet/set_queue_size Set queue_size in soundplay_node Publisher
  • do both in same script.
  • Added script showing the various blocking/non-blocking ways of using SoundClient.
  • removed trailing whitespace only
  • loginfo -> logdebug.
  • Slightly more condensed version of thresholding.
  • Enable blocking calls inside libsoundplay's SoundClient. This makes use of the actionlib interface provided by soundplay_node, by ensuring SoundClient receives a response before returning. Turn this on by: SoundClient(blocking=true).
  • Use new-style python classes (inherits from object).
  • removed trailing whitespace.
  • Set the volume in each of the sound_play actionlib tests. This makes the script actually play the sounds it requests.
  • Specify queue size explicitly. Removed warning message printed each time soundplay_node was started.
  • remove trailing whitespace only.
  • Change wiki urls
  • Fix test target name collision. Fixes #49
  • sound_play: cpp header conforms to the style guide
  • sound_play: update scripts to allow volume to be set
  • sound_play: updated tests to include volume changes
  • sound_play: add ability to specify volume at which to play sounds Also changed error to warning as per todo
  • sound_play: fix indentation and comment inconsistencies
  • sound_play: remove some raw prints cluttering output
  • sound_play: added queue_size to SoundClient init Should prevent warning being displayed whenever the client is created. Fixes issue #43
  • add simple-actionlib functionality to sound_play
  • sound_play: Added functions to play files relative to a package path
  • Update maintainer email
  • Contributors: Alexis Ballier, Austin, Daniel Stonier, David V. Lu, Felix Duvallet, Matthias Nieuwenhuisen, Michal Staniaszek, Neowizard, aginika, trainman419

0.2.11 (2016-02-16)

File truncated at 100 lines see the full file

Launch files

  • soundplay_node.launch
    • This launch file starts soundplay_node.py, which is the node that plays sounds based on messages on the robotsound topic.
      • device [default: ]
  • test.launch
    • This launch file runs the sound_play node and a test script that excersises most of its functionality.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged sound_play at Robotics Stack Exchange

No version for distro jazzy showing github. Known supported distros are highlighted in the buttons above.

Package Summary

Tags No category tags.
Version 0.3.3
License BSD
Build type CATKIN
Use RECOMMENDED

Repository Summary

Description This ROS workspace is created on Raspbian OS. Here I have installed ROS Kinetic from source using cross-compilation and worked on projects like Surveilling Robot.
Checkout URI https://github.com/iamrajee/roskinetic_catkin_ws.git
VCS Type git
VCS Version master
Last Updated 2022-03-04
Dev Status UNKNOWN
Released UNRELEASED
Tags cmake ros raspbian catkin raspberry-pi-3 realsense ros-kinetic gmapping-slam realsense-camera
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

sound_play provides a ROS node that translates commands on a ROS topic (

Additional Links

Maintainers

  • Austin Hendrix

Authors

  • Blaise Gassend

sound_play

Dependencies

  • python-pygame
  • festival
  • festvox-don
  • alsa-base
  • alsa-tools

Checking that the speaker/sound card is recognized by the kernel

cat /proc/asound/cards

Your card should be in the list. Make note of the number in front of the card, it will be used to tell alsa where to play sound from.

If your sound device does not show up, your kernel may not support it, or the module may not be loaded. For usb speakers, you may want to try:

modprobe snd-usb-audio

(not sure if this list is exhaustive)

Telling alsa which sound card/speaker to use

Run (replace 75 with the number of the sound device to use):

asoundconf set-default-card 75

This will create .asoundrc.asoundconf in your home directory. To make alsa use these settings, add the following line to ~/.asoundrc

include ".asoundrc.asoundconf"

To set this default to all users, copy this to the system-wide alsa configuration file:

mv ~/.asoundrc.asoundconf /etc/asound.conf

Getting started

Start the sound play node, and have a look at the scripts in the scripts directory that exercise the node’s functionality.

Specify Device via ROS Param

Besides setting default device as system wide settings, you can also specify audio device via rosparam:

<launch>
  <node name="soundplay_node" pkg="sound_play" type="soundplay_node.py">
    <param name="device" value="hw:1,0" />
  </node>
</launch>

or simply run: rosrun sound_play soundplay_node.py _device:="hw:1,0"

In the launch file above, ~device parameter is set to hw:1,0, which tells soundplay_node to use audio device No. 0 connected to audio card No.1. To find card/device number which you want to use, execute:

sudo aplay -l

CHANGELOG

Changelog for package sound_play

0.3.3 (2018-05-22)

  • Fix gstreamer errors. Fixes #108
  • Contributors: trainman419

0.3.2 (2018-05-02)

  • [sound_play] add option to select audio device to play / record (#87)

    • [sound_play] add option to select audio device to play
    • [sound_play] reformat README to markdown; add usage to set device via rosparam
    • audio_capture: add option for selecting device to use
    • audio_play: add option to select device for playing audio

    * add device argument to launch files Conflicts: audio_capture/launch/capture.launch audio_capture/launch/capture_to_file.launch audio_capture/src/audio_capture.cpp audio_play/launch/play.launch sound_play/scripts/soundplay_node.py

  • Merge pull request #95 from yujinrobot/volume_check [sound_play] volume check for cached sounds

  • [sound_play] checks if sound's Gst instance's volume has changed and resets it

  • Contributors: Austin, Naveed Usmani, Yuki Furuta

0.3.1 (2016-08-28)

  • Update to new gstreamer rosdeps
  • Update sound_play to gstreamer 1.0
  • remove chance of uninitialised variable being called in a subscriber callback.
  • Add changelogs
  • Issue: The error checks for missing publisher/action client in sendMsg were inverted. The non-blocking brach tested the action client while the blocking branch tested the publisher. Fix: Inverted the blocking boolean for both branchs.
  • sound_play: Fix build with -DCATKIN_ENABLE_TESTING=OFF. https://bugs.gentoo.org/show_bug.cgi?id=567466
  • [soundplay_node] fix resources not being released on dict cleanup This was resulting in the number of sink inputs reaching the maximum threshold, (32 on ubuntu 14.04 with pulseaudio 4.0) after which no more sounds could be played by the node. It would only happen if the rate of sounds being played was slower than the dictionary cleanup.
  • depend on actionlib.
  • Introduce unit test to ensure soundclient is started correctly.
  • Example of using the explicit blocking parameter to override the class setting.
  • SoundClient can also explicitly specify whether or not to block while playing the sound. Each play/repeat/say/... method can take an option blocking=True|False argument (using **kwargs), which over-rides the class-wide setting.
  • Merge pull request #62 from felixduvallet/set_queue_size Set queue_size in soundplay_node Publisher
  • do both in same script.
  • Added script showing the various blocking/non-blocking ways of using SoundClient.
  • removed trailing whitespace only
  • loginfo -> logdebug.
  • Slightly more condensed version of thresholding.
  • Enable blocking calls inside libsoundplay's SoundClient. This makes use of the actionlib interface provided by soundplay_node, by ensuring SoundClient receives a response before returning. Turn this on by: SoundClient(blocking=true).
  • Use new-style python classes (inherits from object).
  • removed trailing whitespace.
  • Set the volume in each of the sound_play actionlib tests. This makes the script actually play the sounds it requests.
  • Specify queue size explicitly. Removed warning message printed each time soundplay_node was started.
  • remove trailing whitespace only.
  • Change wiki urls
  • Fix test target name collision. Fixes #49
  • sound_play: cpp header conforms to the style guide
  • sound_play: update scripts to allow volume to be set
  • sound_play: updated tests to include volume changes
  • sound_play: add ability to specify volume at which to play sounds Also changed error to warning as per todo
  • sound_play: fix indentation and comment inconsistencies
  • sound_play: remove some raw prints cluttering output
  • sound_play: added queue_size to SoundClient init Should prevent warning being displayed whenever the client is created. Fixes issue #43
  • add simple-actionlib functionality to sound_play
  • sound_play: Added functions to play files relative to a package path
  • Update maintainer email
  • Contributors: Alexis Ballier, Austin, Daniel Stonier, David V. Lu, Felix Duvallet, Matthias Nieuwenhuisen, Michal Staniaszek, Neowizard, aginika, trainman419

0.2.11 (2016-02-16)

File truncated at 100 lines see the full file

Launch files

  • soundplay_node.launch
    • This launch file starts soundplay_node.py, which is the node that plays sounds based on messages on the robotsound topic.
      • device [default: ]
  • test.launch
    • This launch file runs the sound_play node and a test script that excersises most of its functionality.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged sound_play at Robotics Stack Exchange

No version for distro kilted showing github. Known supported distros are highlighted in the buttons above.

Package Summary

Tags No category tags.
Version 0.3.3
License BSD
Build type CATKIN
Use RECOMMENDED

Repository Summary

Description This ROS workspace is created on Raspbian OS. Here I have installed ROS Kinetic from source using cross-compilation and worked on projects like Surveilling Robot.
Checkout URI https://github.com/iamrajee/roskinetic_catkin_ws.git
VCS Type git
VCS Version master
Last Updated 2022-03-04
Dev Status UNKNOWN
Released UNRELEASED
Tags cmake ros raspbian catkin raspberry-pi-3 realsense ros-kinetic gmapping-slam realsense-camera
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

sound_play provides a ROS node that translates commands on a ROS topic (

Additional Links

Maintainers

  • Austin Hendrix

Authors

  • Blaise Gassend

sound_play

Dependencies

  • python-pygame
  • festival
  • festvox-don
  • alsa-base
  • alsa-tools

Checking that the speaker/sound card is recognized by the kernel

cat /proc/asound/cards

Your card should be in the list. Make note of the number in front of the card, it will be used to tell alsa where to play sound from.

If your sound device does not show up, your kernel may not support it, or the module may not be loaded. For usb speakers, you may want to try:

modprobe snd-usb-audio

(not sure if this list is exhaustive)

Telling alsa which sound card/speaker to use

Run (replace 75 with the number of the sound device to use):

asoundconf set-default-card 75

This will create .asoundrc.asoundconf in your home directory. To make alsa use these settings, add the following line to ~/.asoundrc

include ".asoundrc.asoundconf"

To set this default to all users, copy this to the system-wide alsa configuration file:

mv ~/.asoundrc.asoundconf /etc/asound.conf

Getting started

Start the sound play node, and have a look at the scripts in the scripts directory that exercise the node’s functionality.

Specify Device via ROS Param

Besides setting default device as system wide settings, you can also specify audio device via rosparam:

<launch>
  <node name="soundplay_node" pkg="sound_play" type="soundplay_node.py">
    <param name="device" value="hw:1,0" />
  </node>
</launch>

or simply run: rosrun sound_play soundplay_node.py _device:="hw:1,0"

In the launch file above, ~device parameter is set to hw:1,0, which tells soundplay_node to use audio device No. 0 connected to audio card No.1. To find card/device number which you want to use, execute:

sudo aplay -l

CHANGELOG

Changelog for package sound_play

0.3.3 (2018-05-22)

  • Fix gstreamer errors. Fixes #108
  • Contributors: trainman419

0.3.2 (2018-05-02)

  • [sound_play] add option to select audio device to play / record (#87)

    • [sound_play] add option to select audio device to play
    • [sound_play] reformat README to markdown; add usage to set device via rosparam
    • audio_capture: add option for selecting device to use
    • audio_play: add option to select device for playing audio

    * add device argument to launch files Conflicts: audio_capture/launch/capture.launch audio_capture/launch/capture_to_file.launch audio_capture/src/audio_capture.cpp audio_play/launch/play.launch sound_play/scripts/soundplay_node.py

  • Merge pull request #95 from yujinrobot/volume_check [sound_play] volume check for cached sounds

  • [sound_play] checks if sound's Gst instance's volume has changed and resets it

  • Contributors: Austin, Naveed Usmani, Yuki Furuta

0.3.1 (2016-08-28)

  • Update to new gstreamer rosdeps
  • Update sound_play to gstreamer 1.0
  • remove chance of uninitialised variable being called in a subscriber callback.
  • Add changelogs
  • Issue: The error checks for missing publisher/action client in sendMsg were inverted. The non-blocking brach tested the action client while the blocking branch tested the publisher. Fix: Inverted the blocking boolean for both branchs.
  • sound_play: Fix build with -DCATKIN_ENABLE_TESTING=OFF. https://bugs.gentoo.org/show_bug.cgi?id=567466
  • [soundplay_node] fix resources not being released on dict cleanup This was resulting in the number of sink inputs reaching the maximum threshold, (32 on ubuntu 14.04 with pulseaudio 4.0) after which no more sounds could be played by the node. It would only happen if the rate of sounds being played was slower than the dictionary cleanup.
  • depend on actionlib.
  • Introduce unit test to ensure soundclient is started correctly.
  • Example of using the explicit blocking parameter to override the class setting.
  • SoundClient can also explicitly specify whether or not to block while playing the sound. Each play/repeat/say/... method can take an option blocking=True|False argument (using **kwargs), which over-rides the class-wide setting.
  • Merge pull request #62 from felixduvallet/set_queue_size Set queue_size in soundplay_node Publisher
  • do both in same script.
  • Added script showing the various blocking/non-blocking ways of using SoundClient.
  • removed trailing whitespace only
  • loginfo -> logdebug.
  • Slightly more condensed version of thresholding.
  • Enable blocking calls inside libsoundplay's SoundClient. This makes use of the actionlib interface provided by soundplay_node, by ensuring SoundClient receives a response before returning. Turn this on by: SoundClient(blocking=true).
  • Use new-style python classes (inherits from object).
  • removed trailing whitespace.
  • Set the volume in each of the sound_play actionlib tests. This makes the script actually play the sounds it requests.
  • Specify queue size explicitly. Removed warning message printed each time soundplay_node was started.
  • remove trailing whitespace only.
  • Change wiki urls
  • Fix test target name collision. Fixes #49
  • sound_play: cpp header conforms to the style guide
  • sound_play: update scripts to allow volume to be set
  • sound_play: updated tests to include volume changes
  • sound_play: add ability to specify volume at which to play sounds Also changed error to warning as per todo
  • sound_play: fix indentation and comment inconsistencies
  • sound_play: remove some raw prints cluttering output
  • sound_play: added queue_size to SoundClient init Should prevent warning being displayed whenever the client is created. Fixes issue #43
  • add simple-actionlib functionality to sound_play
  • sound_play: Added functions to play files relative to a package path
  • Update maintainer email
  • Contributors: Alexis Ballier, Austin, Daniel Stonier, David V. Lu, Felix Duvallet, Matthias Nieuwenhuisen, Michal Staniaszek, Neowizard, aginika, trainman419

0.2.11 (2016-02-16)

File truncated at 100 lines see the full file

Launch files

  • soundplay_node.launch
    • This launch file starts soundplay_node.py, which is the node that plays sounds based on messages on the robotsound topic.
      • device [default: ]
  • test.launch
    • This launch file runs the sound_play node and a test script that excersises most of its functionality.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged sound_play at Robotics Stack Exchange

No version for distro rolling showing github. Known supported distros are highlighted in the buttons above.

Package Summary

Tags No category tags.
Version 0.3.3
License BSD
Build type CATKIN
Use RECOMMENDED

Repository Summary

Description This ROS workspace is created on Raspbian OS. Here I have installed ROS Kinetic from source using cross-compilation and worked on projects like Surveilling Robot.
Checkout URI https://github.com/iamrajee/roskinetic_catkin_ws.git
VCS Type git
VCS Version master
Last Updated 2022-03-04
Dev Status UNKNOWN
Released UNRELEASED
Tags cmake ros raspbian catkin raspberry-pi-3 realsense ros-kinetic gmapping-slam realsense-camera
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

sound_play provides a ROS node that translates commands on a ROS topic (

Additional Links

Maintainers

  • Austin Hendrix

Authors

  • Blaise Gassend

sound_play

Dependencies

  • python-pygame
  • festival
  • festvox-don
  • alsa-base
  • alsa-tools

Checking that the speaker/sound card is recognized by the kernel

cat /proc/asound/cards

Your card should be in the list. Make note of the number in front of the card, it will be used to tell alsa where to play sound from.

If your sound device does not show up, your kernel may not support it, or the module may not be loaded. For usb speakers, you may want to try:

modprobe snd-usb-audio

(not sure if this list is exhaustive)

Telling alsa which sound card/speaker to use

Run (replace 75 with the number of the sound device to use):

asoundconf set-default-card 75

This will create .asoundrc.asoundconf in your home directory. To make alsa use these settings, add the following line to ~/.asoundrc

include ".asoundrc.asoundconf"

To set this default to all users, copy this to the system-wide alsa configuration file:

mv ~/.asoundrc.asoundconf /etc/asound.conf

Getting started

Start the sound play node, and have a look at the scripts in the scripts directory that exercise the node’s functionality.

Specify Device via ROS Param

Besides setting default device as system wide settings, you can also specify audio device via rosparam:

<launch>
  <node name="soundplay_node" pkg="sound_play" type="soundplay_node.py">
    <param name="device" value="hw:1,0" />
  </node>
</launch>

or simply run: rosrun sound_play soundplay_node.py _device:="hw:1,0"

In the launch file above, ~device parameter is set to hw:1,0, which tells soundplay_node to use audio device No. 0 connected to audio card No.1. To find card/device number which you want to use, execute:

sudo aplay -l

CHANGELOG

Changelog for package sound_play

0.3.3 (2018-05-22)

  • Fix gstreamer errors. Fixes #108
  • Contributors: trainman419

0.3.2 (2018-05-02)

  • [sound_play] add option to select audio device to play / record (#87)

    • [sound_play] add option to select audio device to play
    • [sound_play] reformat README to markdown; add usage to set device via rosparam
    • audio_capture: add option for selecting device to use
    • audio_play: add option to select device for playing audio

    * add device argument to launch files Conflicts: audio_capture/launch/capture.launch audio_capture/launch/capture_to_file.launch audio_capture/src/audio_capture.cpp audio_play/launch/play.launch sound_play/scripts/soundplay_node.py

  • Merge pull request #95 from yujinrobot/volume_check [sound_play] volume check for cached sounds

  • [sound_play] checks if sound's Gst instance's volume has changed and resets it

  • Contributors: Austin, Naveed Usmani, Yuki Furuta

0.3.1 (2016-08-28)

  • Update to new gstreamer rosdeps
  • Update sound_play to gstreamer 1.0
  • remove chance of uninitialised variable being called in a subscriber callback.
  • Add changelogs
  • Issue: The error checks for missing publisher/action client in sendMsg were inverted. The non-blocking brach tested the action client while the blocking branch tested the publisher. Fix: Inverted the blocking boolean for both branchs.
  • sound_play: Fix build with -DCATKIN_ENABLE_TESTING=OFF. https://bugs.gentoo.org/show_bug.cgi?id=567466
  • [soundplay_node] fix resources not being released on dict cleanup This was resulting in the number of sink inputs reaching the maximum threshold, (32 on ubuntu 14.04 with pulseaudio 4.0) after which no more sounds could be played by the node. It would only happen if the rate of sounds being played was slower than the dictionary cleanup.
  • depend on actionlib.
  • Introduce unit test to ensure soundclient is started correctly.
  • Example of using the explicit blocking parameter to override the class setting.
  • SoundClient can also explicitly specify whether or not to block while playing the sound. Each play/repeat/say/... method can take an option blocking=True|False argument (using **kwargs), which over-rides the class-wide setting.
  • Merge pull request #62 from felixduvallet/set_queue_size Set queue_size in soundplay_node Publisher
  • do both in same script.
  • Added script showing the various blocking/non-blocking ways of using SoundClient.
  • removed trailing whitespace only
  • loginfo -> logdebug.
  • Slightly more condensed version of thresholding.
  • Enable blocking calls inside libsoundplay's SoundClient. This makes use of the actionlib interface provided by soundplay_node, by ensuring SoundClient receives a response before returning. Turn this on by: SoundClient(blocking=true).
  • Use new-style python classes (inherits from object).
  • removed trailing whitespace.
  • Set the volume in each of the sound_play actionlib tests. This makes the script actually play the sounds it requests.
  • Specify queue size explicitly. Removed warning message printed each time soundplay_node was started.
  • remove trailing whitespace only.
  • Change wiki urls
  • Fix test target name collision. Fixes #49
  • sound_play: cpp header conforms to the style guide
  • sound_play: update scripts to allow volume to be set
  • sound_play: updated tests to include volume changes
  • sound_play: add ability to specify volume at which to play sounds Also changed error to warning as per todo
  • sound_play: fix indentation and comment inconsistencies
  • sound_play: remove some raw prints cluttering output
  • sound_play: added queue_size to SoundClient init Should prevent warning being displayed whenever the client is created. Fixes issue #43
  • add simple-actionlib functionality to sound_play
  • sound_play: Added functions to play files relative to a package path
  • Update maintainer email
  • Contributors: Alexis Ballier, Austin, Daniel Stonier, David V. Lu, Felix Duvallet, Matthias Nieuwenhuisen, Michal Staniaszek, Neowizard, aginika, trainman419

0.2.11 (2016-02-16)

File truncated at 100 lines see the full file

Launch files

  • soundplay_node.launch
    • This launch file starts soundplay_node.py, which is the node that plays sounds based on messages on the robotsound topic.
      • device [default: ]
  • test.launch
    • This launch file runs the sound_play node and a test script that excersises most of its functionality.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged sound_play at Robotics Stack Exchange

Package Summary

Tags No category tags.
Version 0.3.3
License BSD
Build type CATKIN
Use RECOMMENDED

Repository Summary

Description This ROS workspace is created on Raspbian OS. Here I have installed ROS Kinetic from source using cross-compilation and worked on projects like Surveilling Robot.
Checkout URI https://github.com/iamrajee/roskinetic_catkin_ws.git
VCS Type git
VCS Version master
Last Updated 2022-03-04
Dev Status UNKNOWN
Released UNRELEASED
Tags cmake ros raspbian catkin raspberry-pi-3 realsense ros-kinetic gmapping-slam realsense-camera
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

sound_play provides a ROS node that translates commands on a ROS topic (

Additional Links

Maintainers

  • Austin Hendrix

Authors

  • Blaise Gassend

sound_play

Dependencies

  • python-pygame
  • festival
  • festvox-don
  • alsa-base
  • alsa-tools

Checking that the speaker/sound card is recognized by the kernel

cat /proc/asound/cards

Your card should be in the list. Make note of the number in front of the card, it will be used to tell alsa where to play sound from.

If your sound device does not show up, your kernel may not support it, or the module may not be loaded. For usb speakers, you may want to try:

modprobe snd-usb-audio

(not sure if this list is exhaustive)

Telling alsa which sound card/speaker to use

Run (replace 75 with the number of the sound device to use):

asoundconf set-default-card 75

This will create .asoundrc.asoundconf in your home directory. To make alsa use these settings, add the following line to ~/.asoundrc

include ".asoundrc.asoundconf"

To set this default to all users, copy this to the system-wide alsa configuration file:

mv ~/.asoundrc.asoundconf /etc/asound.conf

Getting started

Start the sound play node, and have a look at the scripts in the scripts directory that exercise the node’s functionality.

Specify Device via ROS Param

Besides setting default device as system wide settings, you can also specify audio device via rosparam:

<launch>
  <node name="soundplay_node" pkg="sound_play" type="soundplay_node.py">
    <param name="device" value="hw:1,0" />
  </node>
</launch>

or simply run: rosrun sound_play soundplay_node.py _device:="hw:1,0"

In the launch file above, ~device parameter is set to hw:1,0, which tells soundplay_node to use audio device No. 0 connected to audio card No.1. To find card/device number which you want to use, execute:

sudo aplay -l

CHANGELOG

Changelog for package sound_play

0.3.3 (2018-05-22)

  • Fix gstreamer errors. Fixes #108
  • Contributors: trainman419

0.3.2 (2018-05-02)

  • [sound_play] add option to select audio device to play / record (#87)

    • [sound_play] add option to select audio device to play
    • [sound_play] reformat README to markdown; add usage to set device via rosparam
    • audio_capture: add option for selecting device to use
    • audio_play: add option to select device for playing audio

    * add device argument to launch files Conflicts: audio_capture/launch/capture.launch audio_capture/launch/capture_to_file.launch audio_capture/src/audio_capture.cpp audio_play/launch/play.launch sound_play/scripts/soundplay_node.py

  • Merge pull request #95 from yujinrobot/volume_check [sound_play] volume check for cached sounds

  • [sound_play] checks if sound's Gst instance's volume has changed and resets it

  • Contributors: Austin, Naveed Usmani, Yuki Furuta

0.3.1 (2016-08-28)

  • Update to new gstreamer rosdeps
  • Update sound_play to gstreamer 1.0
  • remove chance of uninitialised variable being called in a subscriber callback.
  • Add changelogs
  • Issue: The error checks for missing publisher/action client in sendMsg were inverted. The non-blocking brach tested the action client while the blocking branch tested the publisher. Fix: Inverted the blocking boolean for both branchs.
  • sound_play: Fix build with -DCATKIN_ENABLE_TESTING=OFF. https://bugs.gentoo.org/show_bug.cgi?id=567466
  • [soundplay_node] fix resources not being released on dict cleanup This was resulting in the number of sink inputs reaching the maximum threshold, (32 on ubuntu 14.04 with pulseaudio 4.0) after which no more sounds could be played by the node. It would only happen if the rate of sounds being played was slower than the dictionary cleanup.
  • depend on actionlib.
  • Introduce unit test to ensure soundclient is started correctly.
  • Example of using the explicit blocking parameter to override the class setting.
  • SoundClient can also explicitly specify whether or not to block while playing the sound. Each play/repeat/say/... method can take an option blocking=True|False argument (using **kwargs), which over-rides the class-wide setting.
  • Merge pull request #62 from felixduvallet/set_queue_size Set queue_size in soundplay_node Publisher
  • do both in same script.
  • Added script showing the various blocking/non-blocking ways of using SoundClient.
  • removed trailing whitespace only
  • loginfo -> logdebug.
  • Slightly more condensed version of thresholding.
  • Enable blocking calls inside libsoundplay's SoundClient. This makes use of the actionlib interface provided by soundplay_node, by ensuring SoundClient receives a response before returning. Turn this on by: SoundClient(blocking=true).
  • Use new-style python classes (inherits from object).
  • removed trailing whitespace.
  • Set the volume in each of the sound_play actionlib tests. This makes the script actually play the sounds it requests.
  • Specify queue size explicitly. Removed warning message printed each time soundplay_node was started.
  • remove trailing whitespace only.
  • Change wiki urls
  • Fix test target name collision. Fixes #49
  • sound_play: cpp header conforms to the style guide
  • sound_play: update scripts to allow volume to be set
  • sound_play: updated tests to include volume changes
  • sound_play: add ability to specify volume at which to play sounds Also changed error to warning as per todo
  • sound_play: fix indentation and comment inconsistencies
  • sound_play: remove some raw prints cluttering output
  • sound_play: added queue_size to SoundClient init Should prevent warning being displayed whenever the client is created. Fixes issue #43
  • add simple-actionlib functionality to sound_play
  • sound_play: Added functions to play files relative to a package path
  • Update maintainer email
  • Contributors: Alexis Ballier, Austin, Daniel Stonier, David V. Lu, Felix Duvallet, Matthias Nieuwenhuisen, Michal Staniaszek, Neowizard, aginika, trainman419

0.2.11 (2016-02-16)

File truncated at 100 lines see the full file

Launch files

  • soundplay_node.launch
    • This launch file starts soundplay_node.py, which is the node that plays sounds based on messages on the robotsound topic.
      • device [default: ]
  • test.launch
    • This launch file runs the sound_play node and a test script that excersises most of its functionality.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged sound_play at Robotics Stack Exchange

No version for distro galactic showing github. Known supported distros are highlighted in the buttons above.

Package Summary

Tags No category tags.
Version 0.3.3
License BSD
Build type CATKIN
Use RECOMMENDED

Repository Summary

Description This ROS workspace is created on Raspbian OS. Here I have installed ROS Kinetic from source using cross-compilation and worked on projects like Surveilling Robot.
Checkout URI https://github.com/iamrajee/roskinetic_catkin_ws.git
VCS Type git
VCS Version master
Last Updated 2022-03-04
Dev Status UNKNOWN
Released UNRELEASED
Tags cmake ros raspbian catkin raspberry-pi-3 realsense ros-kinetic gmapping-slam realsense-camera
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

sound_play provides a ROS node that translates commands on a ROS topic (

Additional Links

Maintainers

  • Austin Hendrix

Authors

  • Blaise Gassend

sound_play

Dependencies

  • python-pygame
  • festival
  • festvox-don
  • alsa-base
  • alsa-tools

Checking that the speaker/sound card is recognized by the kernel

cat /proc/asound/cards

Your card should be in the list. Make note of the number in front of the card, it will be used to tell alsa where to play sound from.

If your sound device does not show up, your kernel may not support it, or the module may not be loaded. For usb speakers, you may want to try:

modprobe snd-usb-audio

(not sure if this list is exhaustive)

Telling alsa which sound card/speaker to use

Run (replace 75 with the number of the sound device to use):

asoundconf set-default-card 75

This will create .asoundrc.asoundconf in your home directory. To make alsa use these settings, add the following line to ~/.asoundrc

include ".asoundrc.asoundconf"

To set this default to all users, copy this to the system-wide alsa configuration file:

mv ~/.asoundrc.asoundconf /etc/asound.conf

Getting started

Start the sound play node, and have a look at the scripts in the scripts directory that exercise the node’s functionality.

Specify Device via ROS Param

Besides setting default device as system wide settings, you can also specify audio device via rosparam:

<launch>
  <node name="soundplay_node" pkg="sound_play" type="soundplay_node.py">
    <param name="device" value="hw:1,0" />
  </node>
</launch>

or simply run: rosrun sound_play soundplay_node.py _device:="hw:1,0"

In the launch file above, ~device parameter is set to hw:1,0, which tells soundplay_node to use audio device No. 0 connected to audio card No.1. To find card/device number which you want to use, execute:

sudo aplay -l

CHANGELOG

Changelog for package sound_play

0.3.3 (2018-05-22)

  • Fix gstreamer errors. Fixes #108
  • Contributors: trainman419

0.3.2 (2018-05-02)

  • [sound_play] add option to select audio device to play / record (#87)

    • [sound_play] add option to select audio device to play
    • [sound_play] reformat README to markdown; add usage to set device via rosparam
    • audio_capture: add option for selecting device to use
    • audio_play: add option to select device for playing audio

    * add device argument to launch files Conflicts: audio_capture/launch/capture.launch audio_capture/launch/capture_to_file.launch audio_capture/src/audio_capture.cpp audio_play/launch/play.launch sound_play/scripts/soundplay_node.py

  • Merge pull request #95 from yujinrobot/volume_check [sound_play] volume check for cached sounds

  • [sound_play] checks if sound's Gst instance's volume has changed and resets it

  • Contributors: Austin, Naveed Usmani, Yuki Furuta

0.3.1 (2016-08-28)

  • Update to new gstreamer rosdeps
  • Update sound_play to gstreamer 1.0
  • remove chance of uninitialised variable being called in a subscriber callback.
  • Add changelogs
  • Issue: The error checks for missing publisher/action client in sendMsg were inverted. The non-blocking brach tested the action client while the blocking branch tested the publisher. Fix: Inverted the blocking boolean for both branchs.
  • sound_play: Fix build with -DCATKIN_ENABLE_TESTING=OFF. https://bugs.gentoo.org/show_bug.cgi?id=567466
  • [soundplay_node] fix resources not being released on dict cleanup This was resulting in the number of sink inputs reaching the maximum threshold, (32 on ubuntu 14.04 with pulseaudio 4.0) after which no more sounds could be played by the node. It would only happen if the rate of sounds being played was slower than the dictionary cleanup.
  • depend on actionlib.
  • Introduce unit test to ensure soundclient is started correctly.
  • Example of using the explicit blocking parameter to override the class setting.
  • SoundClient can also explicitly specify whether or not to block while playing the sound. Each play/repeat/say/... method can take an option blocking=True|False argument (using **kwargs), which over-rides the class-wide setting.
  • Merge pull request #62 from felixduvallet/set_queue_size Set queue_size in soundplay_node Publisher
  • do both in same script.
  • Added script showing the various blocking/non-blocking ways of using SoundClient.
  • removed trailing whitespace only
  • loginfo -> logdebug.
  • Slightly more condensed version of thresholding.
  • Enable blocking calls inside libsoundplay's SoundClient. This makes use of the actionlib interface provided by soundplay_node, by ensuring SoundClient receives a response before returning. Turn this on by: SoundClient(blocking=true).
  • Use new-style python classes (inherits from object).
  • removed trailing whitespace.
  • Set the volume in each of the sound_play actionlib tests. This makes the script actually play the sounds it requests.
  • Specify queue size explicitly. Removed warning message printed each time soundplay_node was started.
  • remove trailing whitespace only.
  • Change wiki urls
  • Fix test target name collision. Fixes #49
  • sound_play: cpp header conforms to the style guide
  • sound_play: update scripts to allow volume to be set
  • sound_play: updated tests to include volume changes
  • sound_play: add ability to specify volume at which to play sounds Also changed error to warning as per todo
  • sound_play: fix indentation and comment inconsistencies
  • sound_play: remove some raw prints cluttering output
  • sound_play: added queue_size to SoundClient init Should prevent warning being displayed whenever the client is created. Fixes issue #43
  • add simple-actionlib functionality to sound_play
  • sound_play: Added functions to play files relative to a package path
  • Update maintainer email
  • Contributors: Alexis Ballier, Austin, Daniel Stonier, David V. Lu, Felix Duvallet, Matthias Nieuwenhuisen, Michal Staniaszek, Neowizard, aginika, trainman419

0.2.11 (2016-02-16)

File truncated at 100 lines see the full file

Launch files

  • soundplay_node.launch
    • This launch file starts soundplay_node.py, which is the node that plays sounds based on messages on the robotsound topic.
      • device [default: ]
  • test.launch
    • This launch file runs the sound_play node and a test script that excersises most of its functionality.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged sound_play at Robotics Stack Exchange

No version for distro iron showing github. Known supported distros are highlighted in the buttons above.

Package Summary

Tags No category tags.
Version 0.3.3
License BSD
Build type CATKIN
Use RECOMMENDED

Repository Summary

Description This ROS workspace is created on Raspbian OS. Here I have installed ROS Kinetic from source using cross-compilation and worked on projects like Surveilling Robot.
Checkout URI https://github.com/iamrajee/roskinetic_catkin_ws.git
VCS Type git
VCS Version master
Last Updated 2022-03-04
Dev Status UNKNOWN
Released UNRELEASED
Tags cmake ros raspbian catkin raspberry-pi-3 realsense ros-kinetic gmapping-slam realsense-camera
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

sound_play provides a ROS node that translates commands on a ROS topic (

Additional Links

Maintainers

  • Austin Hendrix

Authors

  • Blaise Gassend

sound_play

Dependencies

  • python-pygame
  • festival
  • festvox-don
  • alsa-base
  • alsa-tools

Checking that the speaker/sound card is recognized by the kernel

cat /proc/asound/cards

Your card should be in the list. Make note of the number in front of the card, it will be used to tell alsa where to play sound from.

If your sound device does not show up, your kernel may not support it, or the module may not be loaded. For usb speakers, you may want to try:

modprobe snd-usb-audio

(not sure if this list is exhaustive)

Telling alsa which sound card/speaker to use

Run (replace 75 with the number of the sound device to use):

asoundconf set-default-card 75

This will create .asoundrc.asoundconf in your home directory. To make alsa use these settings, add the following line to ~/.asoundrc

include ".asoundrc.asoundconf"

To set this default to all users, copy this to the system-wide alsa configuration file:

mv ~/.asoundrc.asoundconf /etc/asound.conf

Getting started

Start the sound play node, and have a look at the scripts in the scripts directory that exercise the node’s functionality.

Specify Device via ROS Param

Besides setting default device as system wide settings, you can also specify audio device via rosparam:

<launch>
  <node name="soundplay_node" pkg="sound_play" type="soundplay_node.py">
    <param name="device" value="hw:1,0" />
  </node>
</launch>

or simply run: rosrun sound_play soundplay_node.py _device:="hw:1,0"

In the launch file above, ~device parameter is set to hw:1,0, which tells soundplay_node to use audio device No. 0 connected to audio card No.1. To find card/device number which you want to use, execute:

sudo aplay -l

CHANGELOG

Changelog for package sound_play

0.3.3 (2018-05-22)

  • Fix gstreamer errors. Fixes #108
  • Contributors: trainman419

0.3.2 (2018-05-02)

  • [sound_play] add option to select audio device to play / record (#87)

    • [sound_play] add option to select audio device to play
    • [sound_play] reformat README to markdown; add usage to set device via rosparam
    • audio_capture: add option for selecting device to use
    • audio_play: add option to select device for playing audio

    * add device argument to launch files Conflicts: audio_capture/launch/capture.launch audio_capture/launch/capture_to_file.launch audio_capture/src/audio_capture.cpp audio_play/launch/play.launch sound_play/scripts/soundplay_node.py

  • Merge pull request #95 from yujinrobot/volume_check [sound_play] volume check for cached sounds

  • [sound_play] checks if sound's Gst instance's volume has changed and resets it

  • Contributors: Austin, Naveed Usmani, Yuki Furuta

0.3.1 (2016-08-28)

  • Update to new gstreamer rosdeps
  • Update sound_play to gstreamer 1.0
  • remove chance of uninitialised variable being called in a subscriber callback.
  • Add changelogs
  • Issue: The error checks for missing publisher/action client in sendMsg were inverted. The non-blocking brach tested the action client while the blocking branch tested the publisher. Fix: Inverted the blocking boolean for both branchs.
  • sound_play: Fix build with -DCATKIN_ENABLE_TESTING=OFF. https://bugs.gentoo.org/show_bug.cgi?id=567466
  • [soundplay_node] fix resources not being released on dict cleanup This was resulting in the number of sink inputs reaching the maximum threshold, (32 on ubuntu 14.04 with pulseaudio 4.0) after which no more sounds could be played by the node. It would only happen if the rate of sounds being played was slower than the dictionary cleanup.
  • depend on actionlib.
  • Introduce unit test to ensure soundclient is started correctly.
  • Example of using the explicit blocking parameter to override the class setting.
  • SoundClient can also explicitly specify whether or not to block while playing the sound. Each play/repeat/say/... method can take an option blocking=True|False argument (using **kwargs), which over-rides the class-wide setting.
  • Merge pull request #62 from felixduvallet/set_queue_size Set queue_size in soundplay_node Publisher
  • do both in same script.
  • Added script showing the various blocking/non-blocking ways of using SoundClient.
  • removed trailing whitespace only
  • loginfo -> logdebug.
  • Slightly more condensed version of thresholding.
  • Enable blocking calls inside libsoundplay's SoundClient. This makes use of the actionlib interface provided by soundplay_node, by ensuring SoundClient receives a response before returning. Turn this on by: SoundClient(blocking=true).
  • Use new-style python classes (inherits from object).
  • removed trailing whitespace.
  • Set the volume in each of the sound_play actionlib tests. This makes the script actually play the sounds it requests.
  • Specify queue size explicitly. Removed warning message printed each time soundplay_node was started.
  • remove trailing whitespace only.
  • Change wiki urls
  • Fix test target name collision. Fixes #49
  • sound_play: cpp header conforms to the style guide
  • sound_play: update scripts to allow volume to be set
  • sound_play: updated tests to include volume changes
  • sound_play: add ability to specify volume at which to play sounds Also changed error to warning as per todo
  • sound_play: fix indentation and comment inconsistencies
  • sound_play: remove some raw prints cluttering output
  • sound_play: added queue_size to SoundClient init Should prevent warning being displayed whenever the client is created. Fixes issue #43
  • add simple-actionlib functionality to sound_play
  • sound_play: Added functions to play files relative to a package path
  • Update maintainer email
  • Contributors: Alexis Ballier, Austin, Daniel Stonier, David V. Lu, Felix Duvallet, Matthias Nieuwenhuisen, Michal Staniaszek, Neowizard, aginika, trainman419

0.2.11 (2016-02-16)

File truncated at 100 lines see the full file

Launch files

  • soundplay_node.launch
    • This launch file starts soundplay_node.py, which is the node that plays sounds based on messages on the robotsound topic.
      • device [default: ]
  • test.launch
    • This launch file runs the sound_play node and a test script that excersises most of its functionality.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged sound_play at Robotics Stack Exchange

Package symbol

sound_play package from audio_common repo

audio_capture audio_common audio_common_msgs audio_play sound_play

ROS Distro
melodic

Package Summary

Tags No category tags.
Version 0.3.18
License BSD
Build type CATKIN
Use RECOMMENDED

Repository Summary

Description Common code for working with audio in ROS
Checkout URI https://github.com/ros-drivers/audio_common.git
VCS Type git
VCS Version master
Last Updated 2024-08-13
Dev Status MAINTAINED
Released RELEASED
Tags No category tags.
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

sound_play provides a ROS node that translates commands on a ROS topic (

Additional Links

Maintainers

  • Austin Hendrix
  • Shingo Kitagawa

Authors

  • Blaise Gassend

sound_play

Dependencies

  • python-pygame
  • festival
  • festvox-don
  • alsa-base
  • alsa-tools

Checking that the speaker/sound card is recognized by the kernel

cat /proc/asound/cards

Your card should be in the list. Make note of the number in front of the card, it will be used to tell alsa where to play sound from.

If your sound device does not show up, your kernel may not support it, or the module may not be loaded. For usb speakers, you may want to try:

modprobe snd-usb-audio

(not sure if this list is exhaustive)

Telling alsa which sound card/speaker to use

Run (replace 75 with the number of the sound device to use):

asoundconf set-default-card 75

This will create .asoundrc.asoundconf in your home directory. To make alsa use these settings, add the following line to ~/.asoundrc

include ".asoundrc.asoundconf"

To set this default to all users, copy this to the system-wide alsa configuration file:

mv ~/.asoundrc.asoundconf /etc/asound.conf

Getting started

Start the sound play node, and have a look at the scripts in the scripts directory that exercise the node’s functionality.

Specify Device via ROS Param

Besides setting default device as system wide settings, you can also specify audio device via rosparam:

<launch>
  <node name="soundplay_node" pkg="sound_play" type="soundplay_node.py">
    <param name="device" value="hw:1,0" />
  </node>
</launch>

or simply run: rosrun sound_play soundplay_node.py _device:="hw:1,0"

In the launch file above, ~device parameter is set to hw:1,0, which tells soundplay_node to use audio device No. 0 connected to audio card No.1. To find card/device number which you want to use, execute:

sudo aplay -l

CHANGELOG

Changelog for package sound_play

0.3.18 (2024-08-13)

  • Merge pull request #249 from peci1/patch-1 festival_plugin: add support for different encodings
  • festival_plugin: add support for different encodings
  • Contributors: Martin Pecka, Shingo Kitagawa

0.3.17 (2023-06-08)

  • Merge pull request #231 from knorth55/no-wait-mode
  • dont wait when rospy.Duration(0) is set for timeout
  • Merge pull request #229 from furushchev/flite-plugin-lazy-load FlitePlugin: Lazy loading default voice path
  • FlitePlugin: Lazy loading default voice path
  • Contributors: Shingo Kitagawa, Yuki Furuta

0.3.16 (2022-12-23)

  • Merge pull request #203 from nakane11/timeout
  • refactor libsoundplay.py
  • Add timeout to wait_for_server and wait_for_result
  • Contributors: Aoi Nakane, Shingo Kitagawa

0.3.15 (2022-08-29)

  • Merge pull request #200 from knorth55/yaml-missing
  • show error and skip loading when plugin yaml is missing
  • Merge pull request #199 from knorth55/install-plugin-yaml
  • fix missing install in CMakeLists.txt
  • Contributors: Shingo Kitagawa

0.3.14 (2022-08-18)

  • Merge pull request #193 from knorth55/refactor-soundplay-node
  • refactor soundplay_node.py
  • Merge pull request #192 from knorth55/fix-file-open-issue
  • fix typo causing file open issue
  • Merge pull request #191 from knorth55/flite-default-voice-dir
  • add default voice dir for flite_plugin
  • Merge pull request #190 from ros-drivers/knorth55-patch-1
  • Update soundplay_node.py
  • Merge pull request #187 from knorth55/fix-typo
  • fix typo in soundplay_node.py
  • Merge pull request #185 from knorth55/sound-play-flite-plugin add flite plugin for sound_play
  • Merge pull request #183 from knorth55/sound-play-plugin add soundplay plugin feature
  • add flite in sound_play dependency
  • refactor FestivalPlugin
  • add flite plugin
  • change default_voice to None
  • add plugin arg in soundplay_node.launch
  • refactor codes
  • add output screen in soundplay_node.launch
  • add soundplay plugin attribute
  • Merge pull request #184 from knorth55/default-voice
  • add default_voice in soundplay_node.launch
  • Merge pull request #182 from iory/is-speaking
  • Improve is_speaking by checking goal status
  • Merge pull request #181 from knorth55/refactor-is-speaking
  • refactor is_speaking.py
  • Contributors: JSK fetch user, Shingo Kitagawa, iory

0.3.13 (2022-04-07)

  • Merge pull request #176 from iory/is-speeching
  • Add is_speaking.py to catkin_install_python

File truncated at 100 lines see the full file

Launch files

  • soundplay_node.launch
    • This launch file starts soundplay_node.py, which is the node that plays sounds based on messages on the robotsound topic.
      • device [default: ]
      • loop_rate [default: 100]
      • default_voice [default: ]
      • plugin [default: sound_play/festival_plugin]
  • test.launch
    • This launch file runs the sound_play node and a test script that excersises most of its functionality.

Services

No service files found

Plugins

Recent questions tagged sound_play at Robotics Stack Exchange

Package symbol

sound_play package from audio_common repo

audio_capture audio_common audio_common_msgs audio_play sound_play

ROS Distro
noetic

Package Summary

Tags No category tags.
Version 0.3.18
License BSD
Build type CATKIN
Use RECOMMENDED

Repository Summary

Description Common code for working with audio in ROS
Checkout URI https://github.com/ros-drivers/audio_common.git
VCS Type git
VCS Version master
Last Updated 2024-08-13
Dev Status MAINTAINED
Released RELEASED
Tags No category tags.
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

sound_play provides a ROS node that translates commands on a ROS topic (

Additional Links

Maintainers

  • Austin Hendrix
  • Shingo Kitagawa

Authors

  • Blaise Gassend

sound_play

Dependencies

  • python-pygame
  • festival
  • festvox-don
  • alsa-base
  • alsa-tools

Checking that the speaker/sound card is recognized by the kernel

cat /proc/asound/cards

Your card should be in the list. Make note of the number in front of the card, it will be used to tell alsa where to play sound from.

If your sound device does not show up, your kernel may not support it, or the module may not be loaded. For usb speakers, you may want to try:

modprobe snd-usb-audio

(not sure if this list is exhaustive)

Telling alsa which sound card/speaker to use

Run (replace 75 with the number of the sound device to use):

asoundconf set-default-card 75

This will create .asoundrc.asoundconf in your home directory. To make alsa use these settings, add the following line to ~/.asoundrc

include ".asoundrc.asoundconf"

To set this default to all users, copy this to the system-wide alsa configuration file:

mv ~/.asoundrc.asoundconf /etc/asound.conf

Getting started

Start the sound play node, and have a look at the scripts in the scripts directory that exercise the node’s functionality.

Specify Device via ROS Param

Besides setting default device as system wide settings, you can also specify audio device via rosparam:

<launch>
  <node name="soundplay_node" pkg="sound_play" type="soundplay_node.py">
    <param name="device" value="hw:1,0" />
  </node>
</launch>

or simply run: rosrun sound_play soundplay_node.py _device:="hw:1,0"

In the launch file above, ~device parameter is set to hw:1,0, which tells soundplay_node to use audio device No. 0 connected to audio card No.1. To find card/device number which you want to use, execute:

sudo aplay -l

CHANGELOG

Changelog for package sound_play

0.3.18 (2024-08-13)

  • Merge pull request #249 from peci1/patch-1 festival_plugin: add support for different encodings
  • festival_plugin: add support for different encodings
  • Contributors: Martin Pecka, Shingo Kitagawa

0.3.17 (2023-06-08)

  • Merge pull request #231 from knorth55/no-wait-mode
  • dont wait when rospy.Duration(0) is set for timeout
  • Merge pull request #229 from furushchev/flite-plugin-lazy-load FlitePlugin: Lazy loading default voice path
  • FlitePlugin: Lazy loading default voice path
  • Contributors: Shingo Kitagawa, Yuki Furuta

0.3.16 (2022-12-23)

  • Merge pull request #203 from nakane11/timeout
  • refactor libsoundplay.py
  • Add timeout to wait_for_server and wait_for_result
  • Contributors: Aoi Nakane, Shingo Kitagawa

0.3.15 (2022-08-29)

  • Merge pull request #200 from knorth55/yaml-missing
  • show error and skip loading when plugin yaml is missing
  • Merge pull request #199 from knorth55/install-plugin-yaml
  • fix missing install in CMakeLists.txt
  • Contributors: Shingo Kitagawa

0.3.14 (2022-08-18)

  • Merge pull request #193 from knorth55/refactor-soundplay-node
  • refactor soundplay_node.py
  • Merge pull request #192 from knorth55/fix-file-open-issue
  • fix typo causing file open issue
  • Merge pull request #191 from knorth55/flite-default-voice-dir
  • add default voice dir for flite_plugin
  • Merge pull request #190 from ros-drivers/knorth55-patch-1
  • Update soundplay_node.py
  • Merge pull request #187 from knorth55/fix-typo
  • fix typo in soundplay_node.py
  • Merge pull request #185 from knorth55/sound-play-flite-plugin add flite plugin for sound_play
  • Merge pull request #183 from knorth55/sound-play-plugin add soundplay plugin feature
  • add flite in sound_play dependency
  • refactor FestivalPlugin
  • add flite plugin
  • change default_voice to None
  • add plugin arg in soundplay_node.launch
  • refactor codes
  • add output screen in soundplay_node.launch
  • add soundplay plugin attribute
  • Merge pull request #184 from knorth55/default-voice
  • add default_voice in soundplay_node.launch
  • Merge pull request #182 from iory/is-speaking
  • Improve is_speaking by checking goal status
  • Merge pull request #181 from knorth55/refactor-is-speaking
  • refactor is_speaking.py
  • Contributors: JSK fetch user, Shingo Kitagawa, iory

0.3.13 (2022-04-07)

  • Merge pull request #176 from iory/is-speeching
  • Add is_speaking.py to catkin_install_python

File truncated at 100 lines see the full file

Launch files

  • soundplay_node.launch
    • This launch file starts soundplay_node.py, which is the node that plays sounds based on messages on the robotsound topic.
      • device [default: ]
      • loop_rate [default: 100]
      • default_voice [default: ]
      • plugin [default: sound_play/festival_plugin]
  • test.launch
    • This launch file runs the sound_play node and a test script that excersises most of its functionality.

Services

No service files found

Plugins

Recent questions tagged sound_play at Robotics Stack Exchange