Any command can now be assigned to any MIDI CC message.

Can someone explain how this works? Its not the macro feature its it?

I would like to know also. Could not find any info about it.

I assume this refers to the fact that you can right-click on a control button, choose "Assign Command" and then select actions from the list (including Macros).

Aaah, ofcourse! I was searching in the macrobar.

I'll try it tonight.

^Yep!

Loving it. This help with the ensuing controller support debate! Only issue is that there are certain controller buttons that don't send MIDI.... but it should definitely help improve functionality.

There's still a few functions in the list that need to be added, like "add instrument". I can't wait til I can press a button and add the instrument without a mouse stroke!

This message was edited 1 time. Last update was at 19/04/2012 15:12:59

I'm going to try this tonight. let me get this straight, do I need to know the cc numbers sent from my midi device in order to map them to a function in studio one?

CubaseUser wrote:I'm going to try this tonight. let me get this straight, do I need to know the cc numbers sent from my midi device in order to map them to a function in studio one?

I don't believe so, no. The button "learns" the CC message and then you assign the button to something.

So I right click the parameter in studio one, "assign command" and press the button on my hardware?

This message was edited 1 time. Last update was at 19/04/2012 16:31:04

CubaseUser wrote:So I right click the parameter in studio one, "assign command" and press the button on my hardware?

"Assign Command" there (I think) works just like the macro toolbar buttons, to assign a command directly to a button. IIRC, hardware buttons are "learned" there (on external devices) when you go into "Midi learn" mode on the device panel. So it's two different things...

1. "Learn" the message by hitting the button on the hardware ("Midi Learn")
2. Assign that button that has learned the message to a macro.

I think that's how it works anyway. Sounds like maybe a good video tutorial for Johnnie. He has a bunch of hardware controllers.

I shall sit and mess with this tonight. I'm going to try to map send levels to thefaders on my midi keyboard.

CubaseUser wrote:I shall sit and mess with this tonight. I'm going to try to map send levels to thefaders on my midi keyboard.

I'd be mapping all kinds of stuff on my d8b except that it died... won't boot up.

Now I gotta go contact Mackie for a replacement boot disk.

I'm hoping that it will work in conjunction with the Mackie hui mode that I have my tascam device set to

I am very interested in the findings of this as well as perfecting this myself. I am going to be seeing what I can do with Lemur and my iPad with this functionality.

Here's how you do it.

1) Click the External Devices tab on the mixer, and double click your controller to pull up it's map.
2) Click "Midi Learn" in S1 and learn whatever controls you want.
3) Make sure your control is marked as a "button". It won't work for a knob or fader.
4) Right click it and hit "assign command"

Then you assign whatever key command you want. Macros is a separate folder in the key command list! That's kinda cool how they incorporated it nicely into the fabric of S1. It doesn't really feel like a "add-on". It feels like what they call it... an extension. Dope.

Mmm, this doesn't quite work right for me. Using my nocturnI can click midi learn and see 8 buttons that can be assigned yet when I assign a parameter pressing one of there nocturn buttons on the hardware doesn't do anything, yet clicking the on screen button performs the command that I assigned.