Axiom 49 mapping basics

[mika]

Hi all, 

First, thanks for giving the opportunity to use such a powerful and user-friendly DAW for free. 

I am looking for a way to assign knobs and faders on my Axiom for 49 to those on the VSTs I'm using in Cakewalk, so I can control with a real thing and not just my mouse. 

I remember for instance, in another software, being able to assign by right-clicking on the knob  and just turning the one I wanted to on my midi controller.. But that doesn't seem to exist in CW. 

Maybe am I missing the whole thing?? 

 

Thanks for your help. 

 

Mika

[John Vere]

It’s all covered very well in the documentation 

https://www.cakewalk.com/Support/Knowledge-Base/2007013035/Setting-Up-a-MIDI-Device-as-a-Control-Surface-in-SONAR

 

[John Vere]

Actually everything is covered very well in the documentation. 

[Bill Eisner]

The instructions aren't clear in the beginning. i am able to get to an ACT screen and add my Axiom 49, but nothing is working. I have 2022.06.   I'm trying to follow the Cakewalk directions but:

1. What Options tab is being referred to in line 1 below?  The Options tab in Track view does not have a MIDI Devices selection.

2. which View tab is referred to in line 2 below? There is a Views tab in main header, and View selections in Track and Piano views, but none of these have  Control Surfaces as an option. 

 

[scook]

5 minutes ago, Bill Eisner said:

The instructions aren't clear in the beginning. i am able to get to an ACT screen and add my Axiom 49, but nothing is working. I have 2022.06.   I'm trying to follow the Cakewalk directions but:

1. What Options tab is being referred to in line 1 below?  The Options tab in Track view does not have a MIDI Devices selection.

2. which View tab is referred to in line 2 below? There is a Views tab in main header, and View selections in Track and Piano views, but none of these have  Control Surfaces as an option. 

 

The document in this link was created in 2007 using a DAW with a significantly different UI.

On 9/26/2021 at 2:48 PM, Cactus Music said:

It’s all covered very well in the documentation 

https://www.cakewalk.com/Support/Knowledge-Base/2007013035/Setting-Up-a-MIDI-Device-as-a-Control-Surface-in-SONAR

 

The current CbB documentation covers both setting up a control surface and how to setup/use ACT.

[Bill Eisner]

I guess it's covered very well if you know already how to do it. but my concerns are still valid. i have an Axiom 49. io can get to the point were a cell 'learns' but nothing happens on my DAW.

[user 905133]

Hope I am not derailing the discussion, but I am wondering what the advantages are of using either a Control Surface style setup or an ACT style setup over a more direct approach.  For software synths, I usually just right click on a parameter control in a VST (unless the VST requires an additional parameter mapping step), select MIDI Learn in the VST's UI (assuming the manufacturer implemented it), and move the desired hardware controller on my keyboard.

Edited October 25, 2022 by User 905133
fixed typo

[Bill Eisner]

Thanks for your answer. I'm a nubie. I'm using Opus with CW. I did as you suggested, but after Opus learned the control ( I tried several) , there was no response. I moved the learnt control but the parameter stayed constant.

[azslow3]

1 hour ago, User 905133 said:

Hope I am not derailing the discussion, but I am wondering what the advantages are of using either a Control Surface style setup or an ACT style setup over a more direct approach.  For software synths, I usually just right click on a parameter control in a VST (unless the VST requires an additional parameter mapping step), select MIDI Learn in the VST's UI (assuming the manufacturer implemented it), and move the desired hardware controller on my keyboard.

MIDI Learn inside VSTi:

• needs implemented in hardware "pages" to control more parameters then physical controls
• require MIDI input with controls routed to the track and echo enables
• VST(i) should support MIDI control
• rarely support encoders, almost no changes for feedback (plug-ins don't send current MIDI values back to device)
• can be recorded as MIDI

ACT approach (not only "ACT MIDI" Cakewalk surface plug-in, but all surface plug-ins in general):

• switching which parameter hardware control at given time is configured in software
• works independent from MIDI routing inside the project
• works on Automation level, also fro VST without MIDI input
• works with encoders, can provide feedback since current parameter value is known
• can be recorded and automation

So, if the goal is record performance, including changes in VSTi parameters together with notes, MIDI learn in plug-in the way to go as really "direct approach".