3 ms·
OSC hasn't really been designed as a replacement for MIDI, I think. It is really a generic data communication protocol. They only specified the syntax and omitt
by spacechild1 5y ago
OSC hasn't really been designed as a replacement for MIDI, I think. It is really a generic data communication protocol. They only specified the syntax and omitted any semantics. As a consequence, each application has to specify their own OSC messages. And that's what digital mixing consoles, lighting consoles, DAWs like REAPER or computer music programs like SuperCollider do. There really is no common ground between how these applications use OSC.
To make OSC a suitable replacement for MIDI, you would have to come up with a set of OSC messages everyone can agree upon. That's not likely to happen...
- em3rgent0rdr 5y agoIt is a shame OSC didn't specify a minimum standard set of message names to use. I'm looking up and found a proposal for a standard namespace [1] though I'm not sure that even caught on. [1] https://github.com/fabb/SynOSCopy/wiki https://github.com/fabb/SynOSCopy/wiki
- em3rgent0rdr 5y agoMIDI Manufacturers Association should have come up with a standard "Official MIDI™" namespace for naming OSC messages and which works nicely with regular "MIDI" devices. Instead of trying to make their own new spec (that is unlikely to be widely adopted and which is not physically compatible with "MIDI" anyway).