Open Sound Control (OSC) is a content format, though it is often though of as a protocol for the transmission of data over a network. Its main use and origin is that of a replacement for MIDI as a network-protocol for the exchange of musical control data between soft- and hardware over a UDP-IP network. Applications like SuperCollider, Max/MSP, and Reaktor (among others) use OSC for network communication. Nowadays it is also used in other fields, for example in robotics.
JavaOSC is a library that gives Java programs the capability of sending and receiving OSC. It is not, in itself, a usable program.
The latest release version of the library is available on Maven central or the project homepage.
Latest development sources can be found on github.
modules/core/src/main/java/
JavaOSC core sourcesmodules/ui/src/main/java/
JavaOSC UI sourcesmodules/core/src/main/resources/puredata/
PureData file for the PD examplemodules/core/src/main/resources/supercollider/
SuperCollider files for the examplesmodules/*/target/
where build files end up
JavaOSC is not a standalone application, but designed to be used in other applications. Though, there is a very basic application, created by John Thompson, for demonstration purposes.
To run the demo app, make sure you have all parts packaged and installed:
mvn install
Then start the UI:
cd modules/ui
mvn exec:java
Next, launch SuperCollider, open the file located in the
modules/core/src/main/resources/supercollider/
directory,
and load the synthdef into SuperCollider.
Start the SC local server.
In the JavaOSC Demo UI, click the "All On" button and start moving the sliders.
You should hear the sounds change.
To see what messages the UI is sending, run either the CNMAT dumpOSC,
or turn on dumpOSC in SuperCollider.
There is also a PureData patch created by Alexandre Quessy, available here.
To try the demo UI with PureData,
launch (this is important!) pd-extended and open the file
modules/core/src/main/resources/puredata/javaosc.pd
.
Turn down the volume a bit at first, as it might be very loud.
Click the "All On" button, and start moving the sliders.
You should hear the sounds change.
To see what messages the UI is sending, just look in the PD window or
in the terminal.
The classes that deal with sending OSC data are located in the com.illposed.osc
package.
The core classes are com.illposed.osc.OSCPort{In, Out}
,
com.illposed.osc.OSCMessage
and com.illposed.osc.OSCBundle
.
The common way to use the library is to instantiate an OSCPort
connected to the receiving machine and then call the send()
method
on the port with the packet to send as the argument.
There are some associated JUnit tests, which also contain code that may illustrate
how to use the library.
They can be run with mvn test
.
mvn clean deploy
To release a development version to the Sonatype snapshot repository only.
mvn release:clean
JAVA_HOME=${JAVA6_HOME} mvn -DdryRun=true release:prepare
JAVA_HOME=${JAVA6_HOME} mvn -DdryRun=false release:prepare
This does the following:
- Important for backwards compatibility: use the oldest possible JDK version to compile (currently 1.6)
- asks for the release and new snapshot versions to use (for all modules)
- packages
- signs with GPG
- commits
- tags
git push origin master <release-tag>
JAVA_HOME=${JAVA6_HOME} mvn release:perform
This does the following:
- pushes to origin
- checks-out the release tag
- builds
- deploy into Sonatype staging repository
git checkout <release-tag>
mvn clean site
git checkout master
This does the following:
- generates the site
- pushes the site to the GitHub
gh-pages
branch, which is visible underhttp://hoijui.github.com/JavaOSC/
Use one of these methods:
-
default: using the Nexus staging plugin
mvn nexus:staging-close mvn nexus:staging-release
-
alternative: using the web-interface
- firefox https://oss.sonatype.org
- login
- got to the "Staging Repositories" tab
- select "com.illposed..."
- "Close" it
- select "com.illposed..." again
- "Release" it
This moves the artifact from the Sonatype staging to the main Sonatype repository. From there, it will automatically be copied to Maven Central, which happens at least every four hours.
Thanks to John Thompson for writing the UI (demo application), Alexandre Quessy for the PD demo, and to Martin Kaltenbrunner and Alex Potsides for their contributions.