The MIDI USB Driver (Layer) for KPA MEDIA DEVICE.
-
-
-
+1
& class compliant, too, please!Any plans to develop something like this for us - the users? ...please
-
-
-
+1
About the class compliant thing...
Isn't it the device one wants to connect to the KPA that has to be class compliant? So it doesn't need an operating system to run its drivers? -
-
+1
About the class compliant thing...
Isn't it the device one wants to connect to the KPA that has to be class compliant? So it doesn't need an operating system to run its drivers?In other words class compliant(USB MIDI Device Class in this case ) means that you can use generic MIDI USB driver. But some extended functionality ( like RigManager communication) may not work with this driver.
http://www.usb.org/developers/docs/devclass_docs/midi10.pdfQuoteMac and Windows come with generic USB drivers; there are several types, known as
“classes,” such as USB Video Device Class, USB MIDI
Device Class, USB Mass Storage Class, etc. Peripherals that can work
with those class drivers are referred to as “class compliant.” Because
those “class” drivers are generic, they may not support product-specific
or proprietary features — to access those non-“class” features usually
requires a proprietary driver from the device’s manufacturer.So if you have some specific os with class compliant driver for USB MIDI Device - you don't need specific driver for midi communication. Just plug KPA to the host and you ready for MIDI communication.
But - maybe the RigManager is a problem to do this - maybe the communication with RM is the priority - and other MIDI commands may have influence on this communication.
Just guessing here - I know almost nothing about kernel drivers. -
In other words class compliant(USB MIDI Device Class in this case ) means that you can use generic MIDI USB driver. But some extended functionality ( like RigManager communication) may not work with this driver.
http://www.usb.org/developers/docs/devclass_docs/midi10.pdfThanks for cleaning that up. Very interesting and I think I've just learned something !
Cheers
Alex -
#import "op"
op.suggestion++; -
plus one lol
-
+1
About the class compliant thing...
Isn't it the device one wants to connect to the KPA that has to be class compliant? So it doesn't need an operating system to run its drivers?
No it's doesn't need an operating system, in the usual sense, like Linux, Windows, OSX, etc. Being "class compliant" has to do with the communication protocols the device supports as a baseline. There might be other technical reasons why Kemper can't easily (or at all) send MIDI over it's USB connection, but class compliance probably isn't one of them. "Class compliance" is relatively easy.For example, there are classes for Arduino/Teensy that make your device appears as a CC device upon connection over USB.
-
-
-
-
-
-
-
+1
And wile we're at it: Add support for a USB-Bluetooth dongle + Midi over Bluetooth. A first step to get a nice implementation of the Rig Manager on smartphones and tablets.[Blocked Image: https://images.duckduckgo.com/iu/?u=http%3A%2F%2Fxspace.talaweb.com%2Fgiatuancomputer%2Fhome%2Fusb-bluetooth-dongle-zqv1268275996.jpg&f=1]
-
-