[unsatchmo]

My main beef with OSC is that there is no “there” there. It is hyper flexible at the cost of you needing to design your own meta-protocol. Like every single instrument that supports OSC has a different API with a mess of docs you need to read. Doesn’t really get me in the mood for making music. The DAW manufacturers had a very hard time creating user interfaces that studio engineers could use to configure OSC, and I think that was a main reason nobody ever used it as a synthesizer control protocol.

[seandougall]

Very much so. It’s a useful layer to build an API on top of, but saying a device speaks OSC is like saying a backend service speaks HTTP.