OpenSoundControl.org implementation submission
You would like to let the world know about a software/device/etc. that implements Open Sound Control (whether or not you are not the implementor). To help you publish this implementation as a web page under
("the site"), this form asks a series of questions. Form responses go to the site's editors and you should hear back and/or see the new page appear within a month or so. All content submitted to the site will be given away freely to the world via the CC BY 4.0 license (
This will appear as "submitted by" on this implementation's page, and will also appear in the site-wide combined list of contributors (
). Please use the same name for all your contributions to the site.
Your personal website
If you would like your name in the site's list of contributors to be a link to your home page, enter the URL here.
Your email (as the person submitting this implementation) so that the site editors can contact you if necessary. This WILL NOT APPEAR ON THE SITE.
The name of this implementation, in other words, the name of the thing (hardware/software/product/etc.) that implements OSC. This will be the title of the site's new page for this implementation, and a portion of this name will be converted automatically to the URL of the new page.
Is this submission providing updated information about an implementation already listed on the site? "No" means this is an implementation not already on the site. "Yes" means that the site already has old information about this implementation, which is somehow incorrect or out-of-date, so you are supplying an update.
The main URL ("home page") of the thing that implements OSC.
URL of implementation's OSC documentation
A URL specifically documenting this thing's use of OSC, e.g., describing message names, expected types, semantics, etc.
What kind of thing is this?
Programming Language Library
One or two paragraphs about this thing. Line breaks will be discarded; use "<p>" if you want to separate your text into paragraphs.
"High Speed" means packet rate > 100 hz. "Stateless Interface" means the full state is reported in every packet.
Wildcard Matching Support
Which OSC types does the implementation support? (
m: MIDI message
r: RGBA color
To what extent does this implementation support OSC Bundles? (
Supports Nested Bundles
To what extent does this implementation support OSC Time Tags (
Generates "immediate" timestamp
Generates timestamped sequenced data
Performs scheduling on received timestamped data
Timestamps are UTC-synchronized
Which underlying mechanism(s) does this thing use to transport OSC Messages? (For example,
Bidirectional UDP (via sendto/recvfrom)
None / Transport Independent
Please include any publications about this thing, especially relating to its OSC implementation. First submit each one as a publication (
). This will eventually create a web page on the site for the publication (named according to these rules:
). Here on this form put the URLs of the pages on THIS SITE for the publication(s) about this implementation.
Please choose a reasonable number of images about this thing, especially relating to its OSC implementation. For each one give image caption text followed by the URL of the image. (If the URL is a Google Drive link then of course make sure it's public.). Use Markdown syntax, like so: ![Caption text](url), with <p> to separate multiple entries.
Links to Videos
Please include links to videos describing this OSC implementation. For each one give image caption text followed by the URL of the image. (If the URL is a Google Drive link then of course make sure it's public.). Use Markdown syntax, like so: ![Caption text](url), with <p> to separate multiple entries.
What is the status of this thing? "Alpha" and "Beta" refer to not-fully-released status. "Legacy" means that the thing might still work but nobody is still maintaining it. Defunct
alpha / experimental
beta / released for testing
Active / maintained
Any further explanation of the thing's current status, e.g., the last supported OS version.
Regarding the previous questions about "Status", as of when did the thing enter its current status?
Has this thing been superseded / replaced with something else, and if so, what? (If not, leave blank.) For example, if this is an old model of a product, you would list the current model. If it's a defunct software library, it would be nice to list one or more active libraries with similar features.
Anything else you'd like the site editors to know (will not automatically appear on the site page for this implementation).
Never submit passwords through Google Forms.
This form was created inside of Stanford University.