• SONAR
  • X2 ACT Controller (Axiom 61) Conundrum!
2013/01/02 03:23:49
elsongs
Okay folks, first of all I have to apologize...ACT issues are sooo 2011 (Being that I've done a forum search, and no one has had any ACT/Axiom-related questions since 2011), and it's 2013 now, and I know I'm not supposed to be asking these kinds of questions...but...

I have a !@#$% time trying to get my M-Audio Axiom 61 (1st Gen)'s transport control to work in X2!

The thing worked fine in Sonar 7 (with the MMC controller set up)...I could even get some buttons to change mixer channel sets (1-8, 9-16, etc)


Then when I briefly, and all too lately, upgraded to X1 a few months ago, I finally got it to work (Had to modify it since MMC no longer works for transport)...
 
But on X2, I can't get it to work at all.

I know X2 properly copied my X1 settings; I created one custom ACT Controller preset on X1 that shows up on X2, and the keyboard and wheels and pedals work fine, but the transport controls do NOT work whatsoever. 

I even reset my Axiom to the factory presets and used the #17 and #20 ACT Controller preset provided by X2...nada.

YES, everything else in the X2 preferences settings is set up correctly. I octuple-checked.

Sorry for the outdated issue, but...HALP!

2013/01/02 06:35:46
deanx
Hi Elsongs
 
I too have spent many hours trying to do set up ACT with my Axiom 49 MK1. What a head ache. I've got most of the buttons working but I can only get mute, solo arm etc working via 2 button presses and not one. I've tried MMC, MIDI etc tetc but it's always the same.
 
To get the transport going I use the Cakewlak Generic Surface and NOT ACT. I believe a lot of users tend to have multiple surface configs to control Sonar even though only using one device.
 
Hope that makes sense
 
Thanks
Dean
2013/01/02 08:08:07
Grumbleweed_
This is an old post of mine that had a solution for my Axiom 49:
 
There isn't anything to do with the transport controls on an Axiom in the ACT Controller/Surface Properties page so this what you do:
 
Assign the pads (C23 to C28) to do loop, rewind, fast forward, stop, play and record (use ACT Options > Buttons > Pad # > Function).
 
Once done open the Enigma editing software, create a fresh user bank, copy the settings for Program 20 into a new Program in the new bank.
 
Double click on pad C23 and see what the editor says it transmits, double click on the loop button and change the data to match (i.e. Name: Loop, Midi CC: 147, Parameter: Note On/Off, Channel 10, On velocity: 127, Off velocity: 0, Note: 60, Comment: blank).
 
Do the same thing for all six buttons (just the note values change).
 
Save the preset.
 
Send the data to the Axiom.  
 
Choose the program on the Axiom (Program 1 in my case) and Robert is your dad's brother (Bob's your uncle). 
  
If you read through the post a few times it may make some sense...
 
Grum.
2013/01/02 08:20:26
Jeff Evans
I have the M Audio Axiom 61 also. Don't forget that in the manual it talks about setting data values that are being sent from the buttons either in Latch Mode or Trigger Mode

In Latch when you press a button once it sends a certain value and when you press it again it sends another value. In Trigger mode a button will send a certain value when pressed and another value when released. 
 
You need to consult the manual in order to set this up. Different data values can be sent for Trigger and Toggle Modes.  

Some transport buttons you want in latch mode eg Loop, Play, Stop , Record and you want it to send the same data value for both pressing once or twice etc.. But with the Rewind and Fast Forward buttons you can set them up so they send the rewind or wind data command on pressing but the stop command on release. That is how you want those to work.

Same with mute and solo. You want them to solo or mute when you press them once and release that on pressing again. (deanX will be interested in these modes)

First you need to set this all up in the Axiom before doing anything in the DAW. Then you need to set up in your DAW how to assign these data values to their various functions. In Sonar it is ACT and in Studio One it is called Control Link. 



2013/01/02 08:26:27
travismc1
Setting up the Axiom Series is a three part process.  The 1st step is the ACT Control Device.  Going through the steps are...

1.  Hit "P" to bring up preferences. 
2.  Under midi devices, make sure that you are telling sonar to look for Axiom Midi In (not direclink, direclink is buggy in sonar.)
3.  Hit apply.
4.  Under Control surfaces, Make sure you have 1 ACT Control Surface, and 1 Cakewalk Generic Surface. both should be using Axiom Midi in and out. 
5.  Make sure WAI is not checked for Cakewalk Generic Surface.
6.  Hit apply and get out of there (preferences).

Now 2nd step is to go into ACT Preferences for the ACT controller. 
The ACT control fields should be label r1, s1, b1 or such like.... you should have a label field like r1.  Then underneath it should say what is being controlled such as pan or volume, then another field before going to the next label.  click on the bottom field of each section.  The field above will display "midi learn...."  once you move the slider, rotary or button, the Midi learn message will disappear.  Repeat that for every field except the "shift + button" fields... those respond when hitting the button... and the shift button at the same time.

Now your Axiom Sliders (at least 8 of them), Rotaries and 8 buttons are programmed.

You still have to deal with those pesky transport controls. 

Now edit the preferences for the Cakewalk Generic Surface.  Make sure ACT learn is enabled...  On your screen click on the Play button... on your surface push the play button... then click "LEARN."  Go through every transport button want to control in the transport section...  when you are done...

save the work in what ever project you are working on and shut down sonar. 

Start sonar and your settings should have saved.  I've never used the "presets"  nor have I tried to use or change the keyboard presets. 

You still have that 1 slider and 1 button left... wouldn't you love to assign that to your master fader?  YOU CAN.

Open a project.  Right click on your master fader.  One of your options will be remote control...  click on that.... the third choice down is CONTROLLER.  Click beside that.  Slide the 9th fader back and forth and click learn.  In the box beside controller, a number should have appeared.  just for good measure, slide the fader 1 more time up and down... and hit learn again to make sure the number in the box doesnt change. 

Save that project.  Close down sonar.  Restart sonar and see if your master fader works in every project.

The 9th button can be used as a shift button, but you have to hit shift learn in the ACT Contoller edit page.  I usually use the "loop button" in the transport as my shift.



2013/01/02 17:38:53
elsongs
This is an old post of mine that had a solution for my Axiom 49: There isn't anything to do with the transport controls on an Axiom in the ACT Controller/Surface Properties page so this what you do: Assign the pads (C23 to C28) to do loop, rewind, fast forward, stop, play and record (use ACT Options > Buttons > Pad # > Function). Once done open the Enigma editing software, create a fresh user bank, copy the settings for Program 20 into a new Program in the new bank. Double click on pad C23 and see what the editor says it transmits, double click on the loop button and change the data to match (i.e. Name: Loop, Midi CC: 147, Parameter: Note On/Off, Channel 10, On velocity: 127, Off velocity: 0, Note: 60, Comment: blank). Do the same thing for all six buttons (just the note values change). Save the preset. Send the data to the Axiom. Choose the program on the Axiom (Program 1 in my case) and Robert is your dad's brother (Bob's your uncle). If you read through the post a few times it may make some sense... Grum.
Thanks, I did see your old post in a previous thread. My big problem with it is...how do I get the drum pads to show up in the ACT options menu in the first place?
2013/01/02 17:52:15
Beepster
Does any of this stuff apply to the Oxygen series? Gonna have to map mine soon.

Cheers.
2013/01/02 18:03:45
elsongs
travismc1


Setting up the Axiom Series is a three part process.  The 1st step is the ACT Control Device.  Going through the steps are...

1.  Hit "P" to bring up preferences. 
2.  Under midi devices, make sure that you are telling sonar to look for Axiom Midi In (not direclink, direclink is buggy in sonar.)
3.  Hit apply.
4.  Under Control surfaces, Make sure you have 1 ACT Control Surface, and 1 Cakewalk Generic Surface. both should be using Axiom Midi in and out. 
5.  Make sure WAI is not checked for Cakewalk Generic Surface.
6.  Hit apply and get out of there (preferences). 
Now 2nd step is to go into ACT Preferences for the ACT controller. 
The ACT control fields should be label r1, s1, b1 or such like.... you should have a label field like r1.  Then underneath it should say what is being controlled such as pan or volume, then another field before going to the next label.  click on the bottom field of each section.  The field above will display "midi learn...."  once you move the slider, rotary or button, the Midi learn message will disappear.  Repeat that for every field except the "shift + button" fields... those respond when hitting the button... and the shift button at the same time.

Now your Axiom Sliders (at least 8 of them), Rotaries and 8 buttons are programmed.

You still have to deal with those pesky transport controls. 

Now edit the preferences for the Cakewalk Generic Surface.  Make sure ACT learn is enabled...  On your screen click on the Play button... on your surface push the play button... then click "LEARN."  Go through every transport button want to control in the transport section...  when you are done...

save the work in what ever project you are working on and shut down sonar. 

Start sonar and your settings should have saved.  I've never used the "presets"  nor have I tried to use or change the keyboard presets. 

You still have that 1 slider and 1 button left... wouldn't you love to assign that to your master fader?  YOU CAN.

Open a project.  Right click on your master fader.  One of your options will be remote control...  click on that.... the third choice down is CONTROLLER.  Click beside that.  Slide the 9th fader back and forth and click learn.  In the box beside controller, a number should have appeared.  just for good measure, slide the fader 1 more time up and down... and hit learn again to make sure the number in the box doesnt change. 

Save that project.  Close down sonar.  Restart sonar and see if your master fader works in every project.

The 9th button can be used as a shift button, but you have to hit shift learn in the ACT Contoller edit page.  I usually use the "loop button" in the transport as my shift.
Okay, I followed everything you did to the letter. BTW I have the 1st-generation Axiom 61, not the Axiom Pro, so DirectLink doesn't show up on my menu.
But here's my results:

Sliders and rotaries map fine. They work (they were never a problem to begin with, but they work).


 Buttons...I am not able to MIDI-learn them whatsoever. Unlike the sliders/rotaries, I cannot click on the box to make it MIDI-learnable.


Transport Controls in the "Cakewalk Generic Surface" setup: I'm not quite sure if they are learned when I click on "Learn." I see a MIDI controller number pop up in the "Controller" window, and nothing else. It does not respond to anything. Same with any of the buttons.



9th Slider as master fader - Works.



So something seems to be wrong with the buttons on my Axiom 61 communicating with Sonar for some reason.
I also use Reason 6.5 (on both Mac and PC) and the Axiom communicates with it with no issues whatsoever, transport included.





2013/01/03 05:45:27
Frostysnake
Funny...I spent an hour trying to gey my A Pro 800 to work...NO DICE! I can use the interface in X2 to control the A Pro but using the A Pro  effects NOTHING in X2...any suggestions? I have uninstalled and all that numorous times, but still get the same problem. I alo set the A Pro back to factory and a few other ideas I truthfully knew would not work...??
2013/01/03 07:28:40
travismc1
Ok... Check to see is a midi message is going to the computer from the keyboard.  A symbol in the lower right corner usually lights up with 2 red dots.  Just push the buttons and see if the two dots light up back and forth.  If they do, some kind of midi message is coming through. 

On your screen, on the keyboard, it should tell you the midi message number.

http://www.bing.com/videos/search?q=oxygen+8+sonar+video&mid=AA1ABC36390EE6A8097EAA1ABC36390EE6A8097E&view=detail&FORM=VIRE2

This was the video that I used to follow for getting my axiom to work.  I also had an oxygen61 2nd gen... it worked using this procedure.

Now, just an FYI, I have tried programming the Axiom 49 as a Cakewalk Generic Surface without using the ACT surface at all.  On the left hand of the programming page, I had Volume, PAN, and MUTE chosen.  I was able to set those parameters following the Generic Surface procedure... but you have to tell how many "tracks" you want to set and which track you are currently programming.  It's time consuming but do-able.  I was able to set up an Akai APC 40 that way. 
12
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account