Open Sound Control implementation is a mess and very hacky but has great potential to network together various systems. I use it to build instruments and controllers that can talk to each other over wifi but I rely on hard coded IP addresses and bring my own wifi network with me for a show. There's a guy who built a protocol called O2 that gives OSC features like a synced clock and discoverability, etc. You name your services rather than targeting IP/ports. This seems like a step in the right direction, but if I wanted to use O2 right now, I'd have to build everything myself because nothing supports it. TouchOSC doesn't support it. Ardour doesn't support it.
Comments
Open Sound Control implementation is a mess and very hacky but has great potential to network together various systems. I use it to build instruments and controllers that can talk to each other over wifi but I rely on hard coded IP addresses and bring my own wifi network with me for a show. There's a guy who built a protocol called O2 that gives OSC features like a synced clock and discoverability, etc. You name your services rather than targeting IP/ports. This seems like a step in the right direction, but if I wanted to use O2 right now, I'd have to build everything myself because nothing supports it. TouchOSC doesn't support it. Ardour doesn't support it.
It probably isn't missing what I'm working on.
What have professional sound makers told you?