On 09/21/2015 10:10 PM, sypwex wrote:
Thanks for the reply!
What does 'lsusb -v' show when you plug in the device?
the exactly `lsusb -v` out is here http://pastebin.com/raw.php?i=trmwPjGF
information only about 17cc:1110 (`sudo lsusb -D /dev/bus/usb/001/010`):
Device: ID 17cc:1110 Native Instruments Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x17cc Native Instruments idProduct 0x1110 bcdDevice 0.37 iManufacturer 1 Native Instruments iProduct 2 Maschine Mikro iSerial 6 677AC139 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 57 bNumInterfaces 2 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 450mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 0 No Subclass bInterfaceProtocol 0 None iInterface 4 Maschine Mikro HID
Yes, this device only offers HID and DFU (for firmware updates), so you'll have to parse the HID data it produces. Use the hidraw interface to get to the uncached information. Whether you can use an existing tool to do that depends on what you want to achieve with this device.
In either case, there is no hardware MIDI port on this device, so the firmware doesn't offer that as class compliant interface. NI's own software stack might offer that, but that's a pure virtual MIDI device then.
HTH, Daniel