Open Sound Control: Difference between revisions

Revision as of 19:05, 14 December 2023

Revision as of 19:06, 14 December 2023

Line 2:

{{No footnotes|date=August 2010}}

'''Open Sound Control''' ('''OSC''') is a [[Communications protocol|protocol]] for networking [[Synthesizer|sound synthesizers]], computers, and other multimedia devices for purposes such as musical performance or [[show control]]. OSC's advantages include [[interoperability]], accuracy, flexibility and enhanced organization and documentation.<ref name="osc org">{{cite web |title=Introduction to OSC |url=http://opensoundcontrol.org/spec-1_0.html#introduction |website=opensoundcontrol.org |access-date=11 September 2021}}</ref> Its disadvantages include inefficient coding of information, increased load on [[Embedded system|embedded processors]],<ref name=":0">{{Cite web |last=Fraietta |first=Angelo |date=2008 |title=Open Sound Control: Constraints and Limitations |doi=10.5281/zenodo.1179537 |s2cid=5690441 |language=en}}</ref> and lack of standardized messages/interoperability.<ref>{{Cite web |title=Home · fabb/SynOSCopy Wiki |url=https://github.com/fabb/SynOSCopy |access-date=2022-12-31 |website=GitHub |language=en |quote=one of the reasons OSC has not replaced MIDI yet is that there is no connect-and-play … There is no standard namespace in OSC for interfacing e.g. a synth}}</ref><ref>{{Cite web |last=Supper |first=Ben |date=October 24, 2012 |title=We hate MIDI. We love MIDI. |url=https://focusritedevelopmentteam.wordpress.com/2012/10/24/we-hate-midi-we-love-midi/ |access-date=2023-01-01 |website=Focusrite Development |language=en |quote=OSC suffers from a superset of this problem: it’s anarchy, and deliberately so. The owners of the specification have been so eager to avoid imposing constraints upon it that it has become increasingly difficult for hardware to cope with it. … More severely, there is an interoperability problem. OSC lacks a defined namespace for even the most common musical exchanges, to the extent that one cannot use it to send Middle C from a sequencer to a synthesiser in a standardised manner}}</ref><ref>{{Cite web |title=OSC-Namespace and OSC-State: Schemata for Describing the Namespace and State of OSC-Enabled Systems |url=https://www.nime.org/proceedings/2014/nime2014_300.pdf |quote=OSC also introduces new obstacles. First, since there is no fixed set of messages, each participating server needs to know what messages it can send to the servers it intends to communicate with. Currently the OSC standard does not provide for a means of programmatically discovering all messages a server responds to}}</ref> The first specification was released in March 2002.

== Motivation ==