Steffan Andrews

My stance on integration hasn't changed. This PR can't be merged until the XLKit framework is thoroughly vetted in its entirety by a human, and I won't be in a...

Please keep individual features to their own PRs. I'd like to merge the Compressor profile, but I don't agree with the Markdown profile as-is. I am moving that to its...

Ideally it would mean one of two approaches: - add a mode parameter to the existing OSC classes that can determine their configuration as either UDP or TCP - introduce...

I like the notion of transport abstraction, but my initial thought is that there may be increasingly divergent identity and implementation requirements. For example, the concept of Client, Server, and...

Two implementations (user-selectable) would need to be implemented. ## OSC 1.0 - OSC 1.0 *has no defined TCP framing AFAIK* but typically uses packet length > The OSC 1.0 spec...

Initial implementation of TCP client and server classes with MVP unit tests is done. Now needs some cleanup, refactors, a few options added, and additional testing. I'm working through that...

Merged to main and will release 1.3.0 shortly. TCP client and server classes are implemented, tested, and documented, and a new example project is available.

Try using python3. I was able to run all the scripts without issue. I had to update syntax for 3 lines of one of the scripts. In `sbsc.py`, lines 38...40:...

The new tooling only came out this week, I haven't had a chance to check MarkersExtractor. But most of these warnings are relating to the Marker Data codebase. From the...

I've done the appropriate refactors and released MarkersExtractor 0.3.10. I have also pushed a PR with changes for Marker Data in response to the refactors: #107 I only touched Marker...