oscsend and oscdump are OSC tools that are built with the help of liblo. They can be used to control sound or multimedia applications through OSC messaging.
I recently came across Oscsend and Oscdump, two OpenSound Control (OSC) tools that use liblo. With Oscsend, you can transmit an OSC message based on the command line arguments specified, while Oscdump receives OSC messages and prints them to standard output. Both tools operate using User Datagram Protocol (UDP) for networking.
What's great about these tools is that they come included in the source tree of liblo. In addition, the next source tarball of liblo will officially include Oscsend and Oscdump. This means that version numbers of these tools will change to match that of liblo.
Installation is a breeze. Just run the following commands:
./configure
make
make install
By doing so, you can compile and install Oscsend and Oscdump into the right directories. By default, they will be stored in /usr/local/bin. However, you can opt to change the destination directory by passing a few options to the configure script. Check out the list of available options by running ./configure --help.
If you wish to review the usage instructions, simply call the command without any arguments. One thing to note, though, is that Oscsend and Oscdump aren't compatible with Matt Wright's commonly used sendOSC and dumpOSC tools.
All in all, I found that Oscsend and Oscdump are great additions to your toolkit if you're working with OSC. They're easy to install and function as advertised.
What's great about these tools is that they come included in the source tree of liblo. In addition, the next source tarball of liblo will officially include Oscsend and Oscdump. This means that version numbers of these tools will change to match that of liblo.
Installation is a breeze. Just run the following commands:
./configure
make
make install
By doing so, you can compile and install Oscsend and Oscdump into the right directories. By default, they will be stored in /usr/local/bin. However, you can opt to change the destination directory by passing a few options to the configure script. Check out the list of available options by running ./configure --help.
If you wish to review the usage instructions, simply call the command without any arguments. One thing to note, though, is that Oscsend and Oscdump aren't compatible with Matt Wright's commonly used sendOSC and dumpOSC tools.
All in all, I found that Oscsend and Oscdump are great additions to your toolkit if you're working with OSC. They're easy to install and function as advertised.
What's New
Version 1.0.0: N/A