On Monday 04 October 2004, Chris Cannam wrote: > On Monday 04 Oct 2004 12:25, Emiliano Grilli wrote: > > So, they are at the same price, offer the same functionality, one is easy > > to setup and does not involve the use of proprietary software, the other > > is "more difficult to get working", why should I choose the m-audio? > > The MidiSport 2x2 doesn't involve the use of proprietary software, as there > is the GPL firmware (which Pedro mentioned) that works fine. Same goes for > the 1x1, but not I think the 4x4 or 8x8. Yes, thanks. That is exactly what I mean. I think that he is confused about the meaning of "firmware". It is not a synonym of proprietary things. Quoting the Wikipedia (http://en.wikipedia.org/wiki/Firmware): "In computing, firmware is software that is embedded in a hardware device." > Nitpicking aside, I agree with you -- I have a 2x2, and I've found the > firmware situation just awkward enough to recommend getting something else > instead. Twice now I've managed to take it with me on the road only to > remember, when miles from an internet connection, that I'd upgraded the > laptop OS more recently than I'd last used the MidiSport and that I no > longer have a copy of the firmware. You are right here. If mobility is your first requirement then a device that requires firmware is not a good choice. And the USB devices are suitable companions for laptops. But there are several advantages with the loadable firmware. You can upgrade the functionality without modifying the device phisically. A bug in the device's logic is not forever. And if you use a GPL firmware, you can even customize the firmware to suit your needs. For instance, these are some differences using the Midisport2x2 with the proprietary firmwares, compared to the ezusbmidi functionality. 1. ezusbmidi is designed and works following the USB-MIDI standard specification, so you can use the interface with the ALSA driver or the OSS driver, or any other driver conforming the specification without the need of specific quirks. The proprietary firmware is not conforming with the standards, and can be used only with the ALSA drivers, because it has a quirk for it. Look at the USB descriptors shown by `lsusb -v` after loading each firmware if you are curious about this. 2. The proprietary firmware turns on the green leds for every MIDI event received, including the "Active Sensing" events (0xfe). The ezusbmidi firmware doesn't switch on the lights for the received active sensing events (it does so only for the outcoming ones). It is trivial to modify the sources to ignore completely these (or other) kind of events if you want. Thats your freedom. Regards, Pedro
