I think this is exactly what O2 is doing — building on the OSC protocol ("interoperability with existing OSC libraries and applications”) and adding features that we often need in practice ("named services, automatic network address discovery, clock synchronization, and a reliable message delivery option”).
I’m definitely curious about this too; it could be an attractive option to avoid needing to cajole bigger and more disparate projects (thinking ableton link, zeroconf/bonjour, etc.). I have a lot of respect for Roger Dannenberg’s work, and the API looks clean.
Graham
> On Jun 25, 2019, at 6:57 PM, Craig Latta <lurk_at_netjam.org> wrote:
>
>
> Hoi Thor--
>
>> We’re looking into implementing O2 in a project we’re working on.
>>
>> Any comments, assessments, tips? Is this what might help us to
>> discover devices on networks, synchronise clocks, and get things
>> generally more swinging?
>>
>> https://github.com/rbdannenberg/o2
>
> A comment as a question... What keeps OSC from doing what O2 does,
> and/or what you need?
>
>
> -C
>
> --
> Craig Latta
> Black Page Digital
> Amsterdam :: San Francisco
> craig_at_blackpagedigital.com
> +31 6 2757 7177
> + 1 415 287 3547
> _______________________________________________
> Livecode mailing list -- livecode_at_we.lurk.org
> To unsubscribe send an email to livecode-leave_at_we.lurk.org
_______________________________________________
Livecode mailing list -- livecode_at_we.lurk.org
To unsubscribe send an email to livecode-leave_at_we.lurk.org
Received on Tue Jul 09 2019 - 03:31:33 BST