3 ms·
CV has zero semantics, and so it can't really be compared to MIDI. What a given CV "signal" does depends on its destination as much as its source, and in that
by PaulDavisThe1st 5y ago
CV has zero semantics, and so it can't really be compared to MIDI.
What a given CV "signal" does depends on its destination as much as its source, and in that respect, is somewhat similar to OSC, despite being more "universal" yet simultaneously "semantic free".
- eternityforest 5y agoSemantics seem to somerimes get in the way unless they are fully specified into well defined profiles. Which is amazing when they are, in the form of "Any port of this type can meaningfully connect to any other port and it does what you think it should". But a lot of the time you wind up with something that STILL needs config on both ends.... because programmers hate arbitrary choices and always like to leave room for omitting features or simplifying later. And of course, programmers also like to break things, so even if semantics DO work, they won't hesitate to make v2. As much as I really love modular pluggable systems, it seems like semantics free things are unfortunately easier to build an ecosystem around. Nobody gets excited for a chart of data types it seems. OSC has survived surprisingly well though.
- mxmilkiib 5y agoYou can assign a CC to control a value, or you can use CV to control a value, the latter gives more resolution, so one can compare them.
- PaulDavisThe1st 5y agoMany of the MIDI CC's have defined semantics, and another bunch do not. Many MIDI receivers choose to ignore those defined semantics (e.g. bind "volume control" messages to some arbitrary parameter). If you choose to ignore the semantics for the defined CC's, or only use the undefined ones, then MIDI CC does become more like CV. However, that's not the intention of the MIDI specification, and it certainly doesn't cover the rest of the MIDI specification, which dwarfs the CC part.