User Tools

Site Tools


osc_backend

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
Next revision Both sides next revision
osc_backend [2010/09/11 03:03]
madjester created
osc_backend [2010/09/11 03:43]
madjester
Line 1: Line 1:
 +====== OSC: Open Sound Control ======
 +
 +OSC is an open protocol slated to replace MIDI.
 +
 +===== Summary and Rationale =====
 +
 +Add support for OSC. This should allow next generation programs and Monome controllers to work with Mixxx.
 +
 +===== Use Cases =====
 +
 +  * DJ Bill has a Monome Ohm and he wants to Mixxx!
 +  * Madjester just downloaded TouchOSC and he'd think it'd be k-rad to make his own TouchOSC mapping for Mixxx.
 +  * DJ SuperProgrammer decides he wants to hook up Mixxx with Pure Data
 +===== Design =====
 +
 OSC works by connecting to URLs. The standard is that conforming machines will send OSC messages to the URLs and the format that the server excepts. I base this assumption on [[http://​www.linuxjournal.com/​content/​introduction-osc]]. OSC works by connecting to URLs. The standard is that conforming machines will send OSC messages to the URLs and the format that the server excepts. I base this assumption on [[http://​www.linuxjournal.com/​content/​introduction-osc]].
  
 As such we could use this simple format: As such we could use this simple format:
  
-/​[Group]/​[Key]+/Control/​[Group]/​[Key]
  
 We of course would expect the typical floating point values or integer values. We of course would expect the typical floating point values or integer values.
Line 13: Line 28:
   * /​Channel1/​rate_temp_up   * /​Channel1/​rate_temp_up
  
-etc...+We prepend Control in the path so we can separate it from other possible entry points, ie: a direct to MIDI Script connectionThis MIDI Script connection would look something like: 
 + 
 +/​Script/​[Channel]/​ 
 + 
 +That's all I got for thatThe problems here are many: 
 + 
 +  * MIDI Script has no global state 
 +  * You can have duplicate machines hooked up 
 + 
 +One way around them would be to include the name of the device'​s instance itself in the path but that could be quite brittleI'm sure Sean can provide some insight here. 
 + 
 +===== Team ===== 
 + 
 +If you're interested in helping to code this feature, sign up your name below:
  
 +  * **YOU**
 +  * Phillip Whelan (Madjester)
osc_backend.txt · Last modified: 2014/05/23 15:02 by thinkbrown