I have had the Keylab 61 MkII for a few weeks now, and I am finally posting something since I can’t seem to find any other info or reviews addressing some of my questions and concerns. Sorry this is super long; there was no product review page on Gearslutz for me to put this in. But it is relevant to this thread.
So I never owned the previous Keylab (MkI I guess you would call it now), but I was impressed with the Ableton integration that goes a step beyond what you get from basic user remote scripts for unsupported controllers. I did not like the feel of the MkI keys in the store, however, but the MkII advertised even better integration but with a much better key bed. Well, it turns out that the integration is deeper in only a few ways, and falls far short in others:
1. Session control: A key feature I wanted was to be able to navigate and control more than just the first 8 tracks (which is what you get using user remote scripts). The MkII can do that, but it doesn’t give very useful feedback as to how you navigate. The 3 buttons next to the faders change this behavior in ways that I literally cannot figure out. The knobs and faders control 8 tracks at a time, but I can’t really tell which 8 are active, and so I end up using the mouse anyway.
2. Solo/mute/record buttons: These are not as easy to use as they should be. You have to first select an active track (and as noted above, which track it will jump to is not very clear), and then press one of those buttons to solo/mute/record that track. The button row below the faders only selects the track to be active. It would have been easier if the solo/mute/record buttons made that bottom row switch to do one of those functions for all tracks, but instead it takes multiple button presses to navigate, select, and then solo/mute/arm a track. Also, there is no way to do affect multiple tracks, as each new selection unselects the last one. Again, the result is going back to the mouse.
3. Knobs: Unlike the MkI and most keyboards, the knobs in Ableton DAW mode only control track panning. They DO NOT take control of the 8 macro controls for a selected track device, ever, which is basically a deal-breaker for me. They can’t even be used for track sends. This is not “deep DAW integration” by any measure. I actually tried to set up a user-remote script anyway but couldn't get it to recognize anything. This is just super disappointing for a $500 controller.
4. Pads: In Ableton DAW mode the pads do some kind of clip triggering, but it doesn't seem to map in any logical way. I literally can't figure it out. There are 4 rows of 4 pads but clips only appear in the top two rows, and scrolling with the jog wheel and arrows will move the active cell but it does not move the zone controlled by the pads. Also, the pads in this DAW mode don't transmit notes, so if you want to control a drum kit like you would with, say, Push, you actually have to switch out of Live mode (which is not editable) to one of the customizable user modes. The pads themselves are OK, but not great, certainly not on par with Push or even my Akai MPK Mini and LPD. But they are not terrible like the original Akai MPK49/61 keyboards either.
5. Keys: The key action is okay, certainly much better than the MkI, but not great. One annoyance that I notice constantly is that I feel the bottom edge of the keys scratch my fingers whenever I press a key from a slight angle. I am a piano player, so basically any chord will result in this happening. If the keys were just one or two millimeters deeper this would probably not be an issue. The keys are also perhaps a bit on the light side for being semi weighted, but I'm not an expert there. I have a Roland System-8 with its shorter semi-weighted keys, and they do not have these same problems. I also tried the Nektar LX88+ and returned it when I heard the announcement of the Keylab MkII. Its keys didn’t have edges, and it has all 88 of course, but the semi-weighted key action was probably pretty comparable.
6. MIDI: One feature I also wanted on the MkII was 5-pin MIDI in and out for my outboard gear. Well, it turns out that MIDI thru only works with USB MIDI. So you if wanted to use this as a master keyboard for outboard gear in a DAW-less rig, it will have to the first device in your chain, which seems completely bonkers to me. Also, the USB MIDI thru has a lot of issues that appear to be firmware bugs. It does have a super convenient way to change the MIDI channel, which was another feature I wanted, and that does work super well. It also remembers these settings when you power back up, including which mode you left it in, so that's really nice too.
Ironically I was frustrated that the Nektar LX88+, which also boasts deep integration for almost every DAW, does not offer anything for Ableton beyond the basic user remote script features. After seeing the Keylab MkI I was expecting so much more from this MkII, and now I see that the Nektar could do most of what I wanted while the Keylab MkII cannot. I think will have to return this as well and wait and see if Arturia ever push a firmware update to fix some of these obvious oversights. I have been in contact with their tech support (which is excellent, by the way) several times already, and they confirmed some of these issues since the manual is very vague on a lot of the above points. They said they would pass it along, but who knows if a patch will ever be issued. For the price, I don't know how they can afford not to at least make it do what the MkI could do.