S.Wallis


I don't use the drum pads (A1-A8) as drum pads, i use them as control buttons. For example, this is one of my set ups:
A1 = Mute selected track
A2 = Solo selected track
A3 = Arm selected track for recording
A4 - Write enable selected track
A5 = Select previous track
A6 = Select next track
A7 = Bounce to track
A8 = Undo

 

I have just recently bought an A-500 and the only thing I'm having an issue with is getting the drum pads to trigger keyboard shortcuts.

Clicking on their graphic in the control surfaces window causes the assigned shortcut to function, but once I close this window & hit a pad it stops working and produces a midi note instead.



I'm assuming I need to edit the control map in the A-Pro Editor but it only lists maps 1-19, and not 0?




And I've also noticed that my A-500 has all 4 'B' buttons permanently lit up when the ACT button is enabled.


Shouldn't only 1 be lit - i.e whatever function bank I'm currently in?

Finally fixed the above problems I was having...

Classic case of PEBKAC ( Problem Exists Between Keyboard And Chair  )

Didn't have the proper midi output port set in the controller / surfaces panel.

Once that was set correctly, the drum pads work fine as shortcut buttons for X1 functions.

Thanks S Wallis.  Wish you had written the manual for A Pro--- it is sadly lacking.  Love this forum!!

Thanks for this walk through SW which I have followed on trying to set up my A800 tonight - with no luck. I originally did not install the second driver and thought that was my problem but when I try to use the APRO settings suggested it blanks out the controller drop down menu - any thoughts - I see another poster on another thread had the same problem & gave up.

Oh I should say I am using Sonar LE - I was hoping it would work out of the box!

Shortly after writing the above I realised that I should have installed the 32 bit version of the control software with Sonar LE. Seems to be working now - though I imagine I will be back for more advice along the line!

Does anyone know how to split the keyboard and run 2 different soft synths.

I know I'm bumping a 3 year old thread, but the information here saved me a lot of frustration and it's still relevant for Sonar X2.  I spent a couple of hours last night trying to figure out why the A-PRO wasn't controlling transport in Sonar and figured it out in minutes after reading this post.  Wallis, you should be writing the Cakewalk manuals.  Thanks.

This definitely needs another bump....so here it is.