Unable to get any midi events from the device

[DanielCeregatti]

I have a Maschine Mikro MK2 R2 WHT HW. I'm using Debian testing, fully updated as of today, have compiled the code and run it with the device connected to /dev/hidraw2 set with perms 0666. Once the program runs, the display on the device goes blank and all the pads turn orange. At this point I was hoping amidi -l would show the device, but it doesn't. Since I use jack, I run qjackctl, which is setup to run a2jmidid once it starts jack. Once these are running, the device appears in qjackctl's midi tab. I open kmidimon and connect it to the device, but hitting pads does not send midi events nor do the pads change color or brightness.

I've confirmed the device functions in windows. It was quite a struggle getting the driver and software installed, but ultimately I was able to run Controller Editor, their software for managing the device, and there I can fully interact with it, e.g. set pad colors, assign CC codes to pads, etc.. I found that for it to function as a midi control surface that it has to be placed into "midi mode" by hitting shift+f1 on the device. When I do this, the board lights up and I can view events using midiview, a freeware windows midi inspection tool, as well as see that hitting keys cause the lights to react by increasing the brightness of the pad that was hit.

My goal is to simply use this device as a midi control surface for the Ardour DAW in Linux. Ideally, it'd work the same way it did in windows in midi mode, with all the colorful interactions and stuff.

One item of note was that when I ran the firmware updater for the device in windows, it reported it was on firmware version 9, yet 8 was listed as the latest by this program.

Any thoughts? Thanks!

[DanielCeregatti]

Since submitting this issue I've been told to use aseqdump -l to see this device one maschine.rs is running. It shows up there:

131:0 maschine.rs Pads MIDI

But aseqdump -p 131 shows no activity when any pad is hit.

I also compiled maschine support into Ardour 6.6 (./waf --maschine). When Ardour starts, the device's screen becomes corrupted, the pads all change to orange, but they light up when hit and CC events for the pads, and only the pads, are readable from Ardour using Ace Midi Monitor on a midi track.

I'm going to try figuring out if there's something to be gleaned from the Ardour code that can be helpful here. Any tips would be greatly appreciated.

[wrl]

i'm not convinced this is not your hardware.

midi dump tools are not going to be useful as the maschine does not communicate with the computer via midi. it uses its own bespoke USB HID protocol and i suspect that is either coming in corrupted from the device for some reason or the newer firmware version has a protocol that maschine.rs does not understand.

i do not presently have the capacity to spearhead this effort to get your device working. however, i suspect you will need to start with wireshark and usbmon.

[DanielCeregatti]

I agree to some extent, especially given what I saw with the firmware versions in windows.

I understand that midi tools only come into play once mashine.rs is running and that Ardour's integration will only be useful within Ardour. I was just hoping to denote that the code still detects and "initializes" the device, even if nothing more. Add to this the fact that Ardour can read the pads and light them up, and I feel that between the two code bases, something can be gleaned.

I will commence gleaning.