Hey Raymond, We should probably take this off the list, but for the record the two alternatives you suggest are I think actually the same thing: rososc is written in Python and uses the Python OSC bindings. I created a ROS node in Python by extending rososc's OscInterface class. The node simply subscribed to the appropriate ROS topics and listened for OSC messages, and bridged only the interesting messages between the two. It worked really well, with less than 100 lines of code. The repo it is in is private, but I could send that class and my installation notes over if you'd like //Mike On Wed, 12 Nov, 2014 at 1:46 AM, Raymond Sheh wrote: > > I'm planning on using a chunk of Python to aggregate the ROS messages > I'm interested in and figure out what sounds to play. It's sounding > like Supercollider is the way to go to actually generate the > sounds. Would there be an advantage to keeping things in ROS and > using ROSOSC to talk to Supercollider, versus using Python's OSC > interface to talk out to Supercollider directly? -- Michael Gratton UNSW School of Computer Science and Engineering. _______________________________________________ ros-users mailing list ros-users@lists.ros.org http://lists.ros.org/mailman/listinfo/ros-users