OpenOSC
The OpenOSC package contains common infrastructural code for your apps to communicate among computers, sound synthesizers, and other multimedia devices via OSC.
Architecture
Addresses
An address has a similar syntax to a URL and begins with the character “/”, followed by the names of all the containers, in order, along the path from the root of the tree to the method, separated by forward slash characters, followed by the name of the method. All types of addresses found in OpenOSC contain ASCII characters only, as specified in OSC 1.0.
OSC Address Pattern
An address pattern is an address to a potential destination of one ore more methods hosted by an “OSC Server”. A number of wildcard characters, such as “*”, can be used to allow for a single address pattern to invoke multiple methods.
let addressPattern = try? OSCAddressPattern("/open/osc/*")
Initialization of an OSCAddressPattern will throw if the format is incorrect or invalid characters are found in the given String.
A String can be evaluated to verify whether it is a valid address pattern by using the following:
let valid: Bool = OSCAddressPattern.evaluate("/open/osc/*")
OSC Address
An address is the path to a method hosted by an “OSC Server”. No wildcard characters are allowed as this address signifies the endpoint of an OSCMesage and the full path a message traverses to invoke the method associated with it.
let address = try? OSCAddress("/open/osc/method")
Initialization of an OSCAddress will throw if the format is incorrect or invalid characters are found in the given String.
A String can be evaluated to verify whether it is a valid address by using the following:
let valid: Bool = OSCAddress.evaluate("/open/osc/method")
Messages
An OSCMessage is a packet formed of an OSCAddressPattern that directs it towards one or more methods hosted by an “OSC Server” and arguments that can be used when invoking the methods. OpenOSC implements all required argument types as specified in OSC 1.1.
Initialization with an OSCAddressPattern:
let addressPattern = try! OSCAddressPattern("/open/osc/*")
let message = OSCMessage(with: addressPattern,
arguments: [Int32(1),
Float32(3.142),
"Open OSC",
OSCTimeTag.immediate,
true,
false,
Data([0x01, 0x01]),
OSCArgument.nil,
OSCArgument.impulse])
Initialization with a raw address pattern String:
let message = try? OSCMessage(with: "/open/osc/*",
arguments: [Int32(1),
Float32(3.142),
"Open OSC",
OSCTimeTag.immediate,
true,
false,
Data([0x01, 0x01]),
OSCArgument.nil,
OSCArgument.impulse])
Initialization of an OSCMessage will throw if the format is incorrect or invalid characters are found in the given String address pattern.
Bundles
An OSCBundle is a container for messages, but also other bundles and allows for the invokation of multiple messages atomically as well scheduling them to be invoked at some point in the future. For further information regarding the temporal semantics of bundles and their associated OSCTimeTags, please see OSC 1.0.
let message1 = try! OSCMessage(with: "/open/osc/1")
let message2 = try! OSCMessage(with: "/open/osc/2")
let message3 = try! OSCMessage(with: "/open/osc/3")
let bundle = OSCBundle([message1, message2, message3],
timetag: .immediate)
Address Spaces
An OSCAddressSpace is a set of methods hosted by an “OSC Server” that can be invoked by one or more OSCMessages. Think of it as a container for blocks of code, that can be dispatched when a message is received, with an address pattern that matches against a methods OSCAddress.
Methods
An OSCMethod is a struct that encapsulates a closure and the OSCAddress needed to invoke it. The idea is that if you wanted to make available control functionality within your application to “OSC Clients” you would begin by creating OSCMethods, adding them to an OSCAddressSpace and when an OSCMessage is received it would be passed to the address space to potentially invoke a method it contains.
For example:
let method = OSCMethod(with try! OSCAddress("object/coords"), invokedAction { [weak self] message, _ in
guard message.arguments.count == 2,
let x = message.argument[0] as? Float32,
let y = message.argument[1] as? Float32 else { return }
print("Received /object/coords, x: \(x), y: \(y)"
self?.object.x = x
self?.object.y = y
})
var addressSpace = OSCAddressSpace(methods: [method])
let message = try! OSCMessage("object/coords", arguments: [Float32(3), Float32(5)])
addressSpace.invoke(with: message)
print(object.x) // 3
print(object.y) // 5
Extensions
The following objects are not part of either OSC specification but have been developed after observation of implementations of OSC in the wild and aim to provide help and functionality for you to integrate with them.
Annotations
An OSC annotation is a script for writing an OSCMessage in a human readable format allowing you to enable your users to quickly create OSCMessages by typing them out as well as presenting them in logs.
There are two available styles of annotation found in OpenOSC. It is strongly recommended that OSCAnnotationStyle.spaces is used, rather than OSCAnnotationStyle.equalsComma as it will allow you
to use the valid “=” character in your OSCAddressPatterns.
A String can be evaluated to verify whether it is a valid annotation by using the following:
let annotation = "/open/osc 1 3.142 \"A string with spaces\" aString true false nil impulse"
let valid: Bool = OSCAnnotation.evaluate(annotation, style: .spaces)
An OSCMessage can be initialized from a valid OSC annotation.
let annotation = "/open/osc 1 3.142 \"a string with spaces\" aString true"
let message = OSCAnnotation.message(for: annotation, style: .spaces)
print(message) // OpenOSC.OSCMessage(addressPattern: OpenOSC.OSCAddressPattern(fullPath: "/open/osc", parts: ["open", "osc"], methodName: "osc"), arguments: [1, 3.142, "a string with spaces", "aString", true])
An OSC annotation can be initialized from an OSCMessage.
let message = try! OSCMessage(with: "/open/osc",
arguments: [Int32(1),
Float32(3.142),
"Open OSC",
true,
false,
OSCArgument.nil,
OSCArgument.impulse])
// Without argument type tags.
let annotation1 = OSCAnnotation.annotation(for: message,
style: .spaces,
type: false)
print(annotation1) // "/open/osc 1 3.142 "Open OSC" true false nil impulse"
// With argument type tags.
let annotation2 = OSCAnnotation.annotation(for: message,
style: .spaces,
type: true)
print(annotation2) // "/open/osc 1(i) 3.142(f) "Open OSC"(s) true(T) false(F) nil(N) impulse(I)"
Address Filters
An OSCAddressFilter is kind of the reverse of an OSCAddressSpace. Where an address space allows for an address pattern to invoke multiple pre defined methods. An address filter allows for a single method to be invoked by multiple loosly formatted address patterns by using a “#” wildcard character and omitting parts from the pattern matching. Think of an address filter as a container for blocks of code, that can be dispatched when a message is received, with an address pattern that matches against a filter methods OSCFilterAddress.
Filter Methods
An OSCFilterMethod is a struct that encapsulates a closure and the OSCFilterAddress needed to invoke it. The idea is that if you wanted to make available control functionality within your application to “OSC Clients” without the overhead of establishing an address space containing an OSCAddress and method for each control functionality you would begin by creating OSCFilterMethods, adding them to an OSCAddressFilter and when an OSCMessage is received it would be passed to the address filter to potentially invoke a method it contains.
For example:
let method = OSCFilterMethod(with try! OSCAddress("cue/#/fired"), invokedAction { [weak self] message, _ in
print("Received: \(message.addressPattern.fullPath)")
self?.logs.append("Cue \(message.addressPattern.parts[1])")
})
var addressFilter = OSCAddressFilter(methods: [method])
let message1 = try! OSCMessage(with: "cue/1/fired")
addressFilter.invoke(with: message1)
let message2 = try! OSCMessage(with: "cue/2/fired")
addressFilter.invoke(with: message2)
let message3 = try OSCMessage(with: "cue/3/fired")
addressFilter.invoke(with: message3)
print(logs) // ["Cue 1", "Cue 2", "Cue 3"]
⚠️ – An OSCFilterAddress uses the “#” character, which has been specifically chosen because it is invalid within an OSCAddressPattern. Under no circumstances should you attempt to create an OSCMessage using an OSCFilterAddress as its address pattern.
Refracting
An OSCRefractingAddress can be used to “refract” an OSCAddressPattern to something else. The core idea for this object is to allow an “OSC Server” to act as a router, taking an OSCMessage from one application and routing it to another with modifcations made to the address pattern. Refracting is made possible by using an “#” wildcard character suffixed by a part index number (not 0 indexed). Where a wildcard is used within the refracting address the part will be replaced by the part from the given address pattern. To be succesful at refracting the suffixed index number must be valid with regards to the given address patterns number of parts.
let refractingAddress = try? OSCRefractingAddress("/open/#2/#4")
let addressPattern = try? OSCAddressPattern("/open/osc/refracting/test")
let refractedAddress: OSCAddressPattern = try? refractingAddress.refract(address: addressPattern)
print(refractedAddress!.fullPath) // "/open/osc/test"
A String can be evaluated to verify whether it is a valid refracting address by using the following:
let valid: Bool = OSCRefractingAddress.evaluate("/open/#2/#4")
⚠️ – An OSCRefractingAddress uses the “#” character, which has been specifically chosen because it is invalid within an OSCAddressPattern. Under no circumstances should you attempt to create an OSCMessage using an OSCRefractingAddress as its address pattern.
To Do
- Enhance the regexes for all address objects:
OSCAddressPattern,OSCAddress,OSCRefractingAddress,OSCFilterAddress. - Enhance the
evaluate(:String)function for all address objects:OSCAddressPattern,OSCAddress,OSCRefractingAddress,OSCFilterAddress. - Develop an API for invoking
OSCMessages withinOSCBundles and respecting the bundlesOSCTimeTag. - Research and potentially implement OSCQuery.
- Explore mapping
OSCMethods within theOSCAddressSpaceto a tree like data structure.
Authors
Sammy Smallman – Initial Work – SammySmallman
Daniel Murfin – Fork – dsmurfin
See also the list of contributors who participated in this project.
