Setting up control surface for Arturia Keylab61

Discussion about: tracktion.com
Post Reply New Topic
RELATED
PRODUCTS

Post

Hi guys,

I have bought a midi controller! YAY :D I got it connected and I can play and record Midi with all right.

Now I would like to use all the buttons I have on the controller. With the midi-learn mode I was able to connect volume and pan to switches on the controller.

I have tried the same way to assign play/record etc from the transport window at the bottom right but this doesn't seem to work. I go into midi learn, click on the (play) button in waveform and then the play button on the controller. But nothing happens. No yellow brackets appear like with the one that worked.

Any ideas what this could be?

Chris

Post

Control is different from MIDI in spite of some keyboards having both together. Check out Settings -> Control Surfaces.

I believe you can also register your device as a Control Surface and set up the buttons (play, stop, record, etc) to map to Waveform's transport controls.
Surely there must be consensus by now...

Post

Yes, the control surfaces is just what I am talking about. I have it all setup there. Now when I go into midi learn mode I can register some (like the volume and pan) but not the transport (like play, stop, record). Just wondering if that is the way it is or I am doing something wrong. In the midi learn mode the transport buttons are also marked as "able-to-register" so I am guessing it's me doing something wrong :)

Post

I'm not sure what you mean by having it all set up in the Control Surfaces, but I had to use the Edit Control Mappings to get mine to work. After it's set up there, you don't really need to to anything while editing an Edit. The transport buttons just work.

However, anything that sends MIDI controller data needs to be set from within the Edit.

I can't tell you much regarding MIDI learn mode. I never use it. I have a keyboard for playing notes and a controller for transport controls. The former needs to be assigned as a track input. The latter controls Waveform so it is always working as long as it's been set up in the Control Surfaces settings page.

If you have set up your device as a Control Surface including the mappings and it still doesn't work, there much be something wrong that I can't help you with.
You do not have the required permissions to view the files attached to this post.
Surely there must be consensus by now...

Post

Thanks for this pic. I haven't looked at that yet. This looks like it could make the transport work. I'll check it out tonight!

Post

So I tried it via this screen but it basically is the same as the midi learn, so the transport is not targetable here.

What I found in the manual of the keyboard is that the transport section is using this.
Using the industry standard Mackie HUI data language, KeyLab Essential gives you direct access to the most frequently used commands in your recording software, including ... (listing the transport functions) ... The buttons in the DAW Command Center send set control messages to your software, and are not configurable. The output of the DAW Command Center can be toggled between MCU and HUI protocols within the MCC.
I have no idea what Mackie and HUI and MCU is but this could be a lead. Anyone knows how to set this in Waveform? I have found how to set this in the Arturia MCC but neither HUI nor Mackie setting made a change. I am assuming I have to set this somewhere within Waveform.

Post Reply

Return to “Tracktion”