A-PRO won't 'focus'

Hi Guys,

I recently got my A-PRO to actually work as intended after much frustration. Then installed X2a update and still all good. I then created a new user on my DAW and stopped non required start up progs such as aniti virus, in doing this Sonar lost all midi devices and control surfaces (nothing listed in preferences).

I reset appropriately (in preferences selected all midi devices and set A-Pro up again in control surfaces - A-Pro control, A-PRO 2 in and A-PRO out. The settings are exactly the same as when working. Now however it will not bring anything into focus (soft synth, plug etc) and is stuck in track control 1 - 8 which I cant change (I do have track control from the A-Pro for 1 - 8 so I know that is working). 

The other strange thing is that it makes no difference if the ACT button is on or not on the A-PRO as it still controls tracks 1 - 8 on or not.

The LCD on the A-PRO just says ACT Enabled when the ACT button is on and does not change when I bring anything into focus within X2.

Thank you in advance for any help or suggestions you may have.

Jlien X - The A-Pro is as standard set to use the Sonar preset control surface (which is control prog 0). I have tried even tried using control prog 19 which is sonar control 2. After failure with both I then tried a factory reset of the A-Pro, no difference.

I believe an indicator of the problem is shown when I try to open the control surface within sonar. With ACT turned on when I open control surface within sonar the A-Pro does not connect - communicate with it (come into focus). However if I turn on ACT on the A-PRO this brings up a control surface that the A-PRO does relate to and focus on and I can change B1 - B4 and everything else. When closed however the A - PRO then reverts back to controlling tracks  1 - 8. It seems as though the A-PRO is not connecting properly.

When I have had a similar problem previously I found A-PRO midi in to be effectively blocking the control surface from communicating with sonar properly. This time however only A-PRO and VS100 are selected within control surface. Settings for A-PRO are correct at:

Control surface = A-PRO
In - A-PRO 2
Out - A-PRO

I have even tried deleting the VS as control leaving A-PRO only - no difference.

Have not come across refresh frequency value in preferences but will look at this now.

Thanks for your ideas, any and all help - suggestions welcome.

Yes, I know control map 0 and 19 are used for controlling Sonar (they are basically the same except for the A1-8 pads, aren't they?)

What I don't understand are (sorry I'm no native English speaker):

1. "With ACT turned on when I open control surface within sonar the A-Pro does not connect"
How do you turn on ACT in this case (without turning on the ACT switch on the A-PRO)? You mean the Enable button on the control surface?
When you launch Sonar, the control surface automatically sends the Sonar control map (0 or 19) to A-PRO, so the ACT switch gets automatically turned on and the display says "Receiving...", in your case this doesn't happen?

2. Do you connect your VS100 to the Midi In of A-PRO or your audio/Midi interface? Does the Merge switch on the A-PRO have anything to do with your problem? 

3. What does it mean it still doesn't work fully? When you click a plugin window you should be able to control its parameters in a second or two, if the right preset is used in the control surface ("Tracks/FX/Synths/Utility (Default)" doesn't control anything, for example).

Hi Jlien X, thank you for your time and help.

I have a few midi dependent bits of outboard and therefore was trying to use both VS-100 and A-PRO as midi in (makes routing a lot of midi items much easier). Unfortunately I have found that if I have both A-PRO and VS-100 selected as midi devices within preferences then I lose A - PRO as a control surface.

For now I will simply re-route midi and keep the A-PRO as a control surface. I still believe there is something I am doing wrong somewhere. It does not make sense that I can have two control surfaces working at the same time yet am restricted to one midi in source.

Thanks again for your interest.