Waveform 13 and Arturia KeyLab Essential mk3 - Anyone Successful?

[DaveL60]

I'm starting to think that I've chosen the wrong MIDI controller. I got a Keylab Essential mk3 for Christmas, as it's feature set seemed very well aligned with my needs and I'd seen plenty of positive reviews. While Waveform isn't on Arturia's list of specifically supported DAWs I naively assumed that at least the basic features should fall into place pretty readily. Alas, no: while I can use the controller to play instruments and the knobs and faders work great with their Analog Lab software instruments, so far I haven't been able to get basic transport control to work with Waveform.

Has anyone had success configuring KL MK3 and Waveform together? Should I start over with "what controllers work well with Waveform?" Any assistance would be appreciated.

[skipscada]

Hi there. I've had my ups and downs with the Keylab Essential (don't remember which make), and I have tried to document problems and solutions here at KVR for future reference. If you search "skipscada" "keylab" in the forum search, a couple of threads should show up. I'm not sure I've ever got it to work 100% as I'd wish, but pretty close. There are some unexpected settings you need to get right, and remember to use the pads on the keyboard to switch between "Analog lab" configuration and "DAW" configuration.

[DaveL60]

If you search "skipscada" "keylab" in the forum search, a couple of threads should show up.

Thanks. I'll take a look when I get some time to play with it again.

[cjayconrod]

I'm using a Keylab Essentials 61 MK3 and I can get transport buttons to work just fine. In Settings, I have all the inputs and outputs enabled under "MIDI Devices." Under "Control Surfaces," I selected "Mackie Control Universal," then "KL Essential 61 mk3 MCU/HUI" as the input and output devices.

[DaveL60]

If you search "skipscada" "keylab" in the forum search, a couple of threads should show up.

I found this thread and it got me over the basic hump so I now have transport, faders, and knobs controlling things within WF13. An oddity I haven't figured out is that the MK3 loop button is toggling click within WF and the MK3 metronome button isn't doing anything. I haven't figured out where it might be possible to edit those mappings (along similar lines the Save / Undo / Redo aren't mapped reasonably either). The thread also mentions MIDIIN2 (or something like that) as a relevant / desired setting but I don't know where / how to configure that; I'm not even sure if it's an KLE MK3 thing or a WF thing.

[skipscada]

The thread also mentions MIDIIN2 (or something like that) as a relevant / desired setting but I don't know where / how to configure that; I'm not even sure if it's an KLE MK3 thing or a WF thing.

In Settings > MIDI Devices i have the option to check/uncheck various devices as output/input. Thse devices include Arturia KeyLab Essential 61, which I have enabled as both input and output. In addition I have "MIDIOUT2 (Arturia KeyLab Essent" as an output option and "MIDIIN2 (Arturia KeyLab Essenti" as an input option. In my case, I have enabled the input, but not the output. I'm not very active in music making at the moment, so I can't tell you exactly how things work, but at least now you know where to find the settings so you can experiment.

[talby]

I am about to get my first keys connected by MIDI to my audio interface and then Waveform.
The Arturia KeyLab 61 Mk3 is one of my hottest candidates, mainly because of having a keyboard in this price range with aftertouch and release-sensitivity. The Analog Lab integration is not of importance for me, as I am Linux and will anyway only connect to the plugins available in the Linux ecosystem, which Arturia doesn't support. I would also configure the KL by its options presented on the hardware, because its MIDI config Windows app will also not be available to me.

I see that there is an entry in my WF 14 PRO for the KL, in the Control Surface section..., does it care nowadays for everything or are additional configurations necessary, besides switching the KL to DAW control mode and to MCU communication protocol?

Could you share your experience with it? Are you still using the KL after a year, or did you decide to switch to a different keyboard which integrates better with Waveform? Did you meanwhile get the transport button keys to control Waveform, and the mod wheels to connect correctly to the expected mod wheel parameters in plugin synths?

[Peter Widdicombe]

Typically mod wheel and pitch bend are sent from any keyboard "transparently", although in some cases they don't do what you expect (particularly mod wheel) - but that will be up to the VST to interpret.

Transport (basic play/stop/record/rewind) is easy enough to set up using Waveform's MidiLearn, if it doesn't work by default. Note you MAY have to select the keyboard's mode in sending DAW messages, as there are a number of common types; and then in Waveform select corresponding, or create a control surface definition with the mapping method above. If there are extra buttons, they can all trigger standard Waveform actions or macros.

Don't know if it's changed or not in WF14- if you get your keyboard to SELECT, mappings are pretty good, but are non-changeable. Custom, do what you want. I don't think you can COPY an existing one as a template and customize it...