• Home
  • History
  • Annotate
Name Date Size #Lines LOC

..03-May-2022-

cmake/H25-Apr-2021-6964

completions/H25-Apr-2021-3326

doc/H25-Apr-2021-662549

example/H25-Apr-2021-2,1061,682

include/rtosc/H25-Apr-2021-3,3501,592

src/H25-Apr-2021-8,2976,653

test/H25-Apr-2021-6,3244,803

.gitignoreH A D25-Apr-202110 31

.travis.ymlH A D25-Apr-2021983 3125

CTestConfig.cmakeH A D25-Apr-2021543 1412

Doxyfile.inH A D25-Apr-202175.4 KiB1,8091,311

LICENSEH A D25-Apr-20211.1 KiB2218

README.adocH A D25-Apr-20211.5 KiB4834

librtosc.pc.cmakeH A D25-Apr-2021345 1411

README.adoc

1RtOsc - Realtime safe OSC Messaging
2===================================
3
4image::https://travis-ci.org/fundamental/rtosc.svg?branch=master[alt="Build status", link="https://travis-ci.org/fundamental/rtosc"]
5
6A realtime safe library for handling OSC messages.
7This library is influenced by liblo and libmapper.
8
9Project Goals
10-------------
11
12* Provide a simple means of handling OSC messages within an application
13* Provide a flexible method of dispatching OSC messages payloads
14* Create a C library with C++ wrappers for ease of use
15* Allow legacy code to have readable RT safe messaging added on
16* Keep networking outside of project scope
17
18Why?
19----
20
21Well if an application is going to receive nice serialized messages in the OSC format,
22then it would be nice if these messages could be dispatched within a realtime
23thread.
24This is not possible with any observed C OSC implementation, so this is an
25attempt to alleviate this issue without creating an entirely hideous API.
26
27Status
28------
29
30- OSC 1.0 spec consistent implementation of all message types, and bundles
31- Lightly tested liblo based implementation verification
32- Working C++ based dispatch system
33- C++ Serialization System
34- C++ Syntax Sugar
35
36Documentation
37-------------
38
39- To see the guide, you can use `asciidoctor Guide.adoc` in the doc directory
40- To build doxygen docs, use `make rtosc-doc` in your build directory
41
42Todo
43----
44
45- Increase test coverage over C++ layer
46- Provide standard compliant path/pattern matching algorithms
47
48