Releases: orchetect/OSCKit
Releases · orchetect/OSCKit
0.5.4
0.5.3
0.5.2
0.5.1
0.5.0
New
- Added new
OSCSocket
class that combines server and client using a single local UDP port - Added
OSCKitSocketExample
project to demonstrateOSCSocket
OSCClient
- Added ability to specify local port with
init(localPort:)
- Added
isPortReuseEnabled
property - Added
isIPv4BroadcastEnabled
property
- Added ability to specify local port with
OSCServer
- Added
isPortReuseEnabled
property - Added
isIPv4BroadcastEnabled
property - Now defaults to main queue using default QoS if not specified
- Added
- Added native support for
CGFloat
as an OSC message value type
Improvements
- Full DocC documentation available online, and buildable within Xcode
- Thinned external dependencies from 4 to 2
- Minor cleanup, unit test updates, and API clarification
0.4.3
0.4.2
0.4.1
- Added ability to optionally store a closure for each OSC method that is registered with
OSCAddressSpace
.
Invokingdispatch(_: OSCMessage)
will execute the closure (on current queue or on a specified queue) for each method that matches the OSC message address pattern. - Added an example project demonstrating the use of OSC method closures
0.4.0
Welcome to OSCKit 0.4.0!
0.4.0 is a complete refactor and overhaul from the ground up.
- OSC address pattern matching and dispatch
- Convenient OSC message value type masking, validation and strong-typing
- Modular: use the provided UDP network layer by default, or use your own
- Support for custom OSC types by way of protocol adoption
- Thread-safe
- Fully unit tested
Check out the example projects to see it in action, and browse the README for an overview of functionality.
Note
Swift 5.7+ and Xcode 14+ are minimum requirements. OSCKit 0.3.1 can be used with Xcode 13.
0.3.1
- Added full OSC time tag support with NTP era rollover
OSCServer
now hastimeTagMode
parameter to set scheduling behaviorOSCServer
receivehandler
closure now forwards time tag information- Updated example project
- Updated documentation
Note: This will be the last release before a major refactor in release 0.4.0 to improve how OSC values are handled.
Note: 0.4.0 will require Xcode 14+ and Swift 5.7+