ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question

Revision history [back]

This is highly experimental code that just barely works -- really more a proof of concept than anything else. ROS doesn't have much in the way of audio support and so you won't find much that works with the output of this node (there is an example script in Python which might happen to play audio using the 'ao' library).

That said, this is designed to be a nodelet that you would add to your normal openni launch file. It would look something like:

<node pkg="nodelet" type="nodelet" name="driver" 
       args="load openni_audio/driver $(arg manager) $(arg bond)"
       respawn="$(arg respawn)">
    <param name="channel" value="0" />
 </node>

if you were to add it directly to the openni launch files. The important parameter is 'channel' which specifies which microphone to connect to. If you want to connect to both sides, you would spawn two nodelets, each serving a different channel.

This is highly experimental code that just barely works -- really more a proof of concept than anything else. ROS doesn't have much in the way of audio support and so you won't find much that works with the output of this node (there is an example script in Python which might happen to play audio using the 'ao' library).

That said, this is designed to be a nodelet that you would add to your normal openni launch file. It would look something like:

<node pkg="nodelet" type="nodelet" name="driver" 
       args="load openni_audio/driver openni_audio/AudioNodelet $(arg manager) $(arg bond)"
       respawn="$(arg respawn)">
    <param name="channel" value="0" />
 </node>

if you were to add it directly to the openni launch files. The important parameter is 'channel' which specifies which microphone to connect to. If you want to connect to both sides, you would spawn two nodelets, each serving a different channel.