From: Daniel Mack <daniel@zonque.org>
To: sypwex@gmail.com
Cc: alsa-user@lists.sourceforge.net, alsa-devel@alsa-project.org,
Clemens Ladisch <cladisch@googlemail.com>
Subject: Re: [Alsa-user] snd-usb-caiaq (NI Maschine Mikro) device not recognised by alsa
Date: Tue, 22 Sep 2015 13:17:54 +0200 [thread overview]
Message-ID: <560138E2.3020300@zonque.org> (raw)
In-Reply-To: <CAGPstWuWNbYpveL56Tznr3TMVGVqprrfAT-F7bGbc5e3nJkCSg@mail.gmail.com>
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
next prev parent reply other threads:[~2015-09-22 11:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAGPstWvoprjRHN2+xZe5w+=pPkOqcqQdR4t7bYY_MgXwKbPD4A@mail.gmail.com>
[not found] ` <55EC7191.8020107@googlemail.com>
2015-09-19 9:20 ` [Alsa-user] snd-usb-caiaq (NI Maschine Mikro) device not recognised by alsa sypwex
2015-09-21 17:09 ` Daniel Mack
2015-09-21 20:10 ` sypwex
2015-09-22 11:17 ` Daniel Mack [this message]
2015-09-22 19:03 ` sypwex
2015-09-23 6:44 ` Daniel Mack
2015-09-24 9:04 ` sypwex
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=560138E2.3020300@zonque.org \
--to=daniel@zonque.org \
--cc=alsa-devel@alsa-project.org \
--cc=alsa-user@lists.sourceforge.net \
--cc=cladisch@googlemail.com \
--cc=sypwex@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.