You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently HyperDisKo depends on https://github.com/bgola/tcposcrouter as an outside dependency which simply distributes OSC messages to all connected clients.
Although sclang has not much network/server resources, sending, receiving and distributing OSC messages is one of sclangs features.
A benefit would be to simply start a HyperDisCo server completely form within sclang - something along
HyperDisKoServer();
// HyperDisKoServer listening on localhost:5555HyperDisKo("localhost:5555");
Con
Needs to be implemented (although not too complicated)
Should this replace the python implementation because supporting two interfaces is always a source of errors. On the other side making sclang run headless on a server can be painful and I am unsure about the security implications on running a sclang interpreter open on the internet (probably a thing one should avoid^^)
IPv6 is not implemented by sclang (but also not by python-osc) which makes a quick sync session via the internet w/o a server nearly impossible. Probably Python will adapt ipv6 for udp faster than sclang?
Pro
Makes a setup to share code really easily even when there is no connection to bgo.la (which requires port 5555 which is often blocked on bigger networks)
No Python runtime necessary
So - is it worth it taking a look onto it?
The text was updated successfully, but these errors were encountered:
Currently HyperDisKo depends on https://github.com/bgola/tcposcrouter as an outside dependency which simply distributes OSC messages to all connected clients.
Although sclang has not much network/server resources, sending, receiving and distributing OSC messages is one of sclangs features.
A benefit would be to simply start a HyperDisCo server completely form within sclang - something along
Con
Pro
So - is it worth it taking a look onto it?
The text was updated successfully, but these errors were encountered: