3 ms·

I'm not an expert so I might be wrong but probably because one solution that fits for all can be a bad idea. Driver complexity is one of the reasons most device

I'm not an expert so I might be wrong but probably because one solution that fits for all can be a bad idea. Driver complexity is one of the reasons most devices are not compatible with all existing OSs by default.

jabl 8y ago
I sometimes wonder whether the ongoing USB-C trainwreck is partly due do trying to be everything for everybody. Leading to complex and flaky HW and SW.
- TheRealPomax 8y ago
  I'm not sure I understand your comment. USB-C is still just USB, which was already a universal messaging transport solution. Driver complexity hasn't gone up just because a new physical plug got invented, so presumably you're thinking of the increased number of devices that now use USB, with a C connector, but the fact that it can do "even more device types!" now makes literally zero difference when the spec was already designed to allow all devices: the only difference is that HW/SW is now finally capable of transmitting reliably enough to handle the massive loads those now-supported devices require (hdmi, ethernet, etc.)
  - DanBC 8y ago
    But now your USB-C cable can brick your device.
    - TheRealPomax 8y ago
      Sysex calls already allowed that since day 1.
mhh__ 8y ago
MIDI is - and should be with future standards - simple, slow and reliable: Musical Instruments don't need much/many volume/types of information, so writing the drivers should be fairly simple. Having said that, some midi to usb converters are still not up to full compliance with the 80s MIDI 1 standard
- gugagore 8y ago
  Does that mean that the converters implement the protocol themselves? I expected them to be roughly FTDI USB UART chips, tied to the MIDI baudrate.
  - mhh__ 8y ago
    I'm not entirely sure, but the fact that there are compatibility/compliance issues leads me to believe it's a mixture of both. Either way, the drivers may be the issue: Parsing the serial correctly etc.

jabl 8y ago

I sometimes wonder whether the ongoing USB-C trainwreck is partly due do trying to be everything for everybody. Leading to complex and flaky HW and SW.

TheRealPomax 8y ago
I'm not sure I understand your comment. USB-C is still just USB, which was already a universal messaging transport solution. Driver complexity hasn't gone up just because a new physical plug got invented, so presumably you're thinking of the increased number of devices that now use USB, with a C connector, but the fact that it can do "even more device types!" now makes literally zero difference when the spec was already designed to allow all devices: the only difference is that HW/SW is now finally capable of transmitting reliably enough to handle the massive loads those now-supported devices require (hdmi, ethernet, etc.)
- DanBC 8y ago
  But now your USB-C cable can brick your device.
  - TheRealPomax 8y ago
    Sysex calls already allowed that since day 1.

mhh__ 8y ago

MIDI is - and should be with future standards - simple, slow and reliable: Musical Instruments don't need much/many volume/types of information, so writing the drivers should be fairly simple. Having said that, some midi to usb converters are still not up to full compliance with the 80s MIDI 1 standard

gugagore 8y ago
Does that mean that the converters implement the protocol themselves? I expected them to be roughly FTDI USB UART chips, tied to the MIDI baudrate.
- mhh__ 8y ago
  I'm not entirely sure, but the fact that there are compatibility/compliance issues leads me to believe it's a mixture of both. Either way, the drivers may be the issue: Parsing the serial correctly etc.