Hello everybody,
 
This is first post, I hope to provide you with complete info about my problem. I am using a UMX610 Behringer as MIDI controller and as it has 8 buttons and knobs I am trying to use it also as a ACT MIDI Controller. It works like a charm with the rotatory controls but with the buttons not. I need to press twice the button for it to trigger the command. What is really strange is that if I assign the Shift Modifier function to a button, in that case I need to press that shift button only once to enable/disable the shift action (but in spite of this I still need to press twice the regular button, the non-shift button to trigger commands being the action "shifted" or not). 
 
I hope you understand because it is a little difficult to explain. 
 
Well, thank you so much for your attention and future help. 

I do not have the controller and the documentation has no required details...
 
You should check what your buttons are sending. They are configurable, so you can try to find the settings which works. The best is when the button sends 2 events, when it is pressed and when it is depressed. If the button is in "toggle" mode (each time you press it sends one event only) you can observe the effect you have. Shift button is processed differently, the first event switch the Shift on and the second switch it off.
 
If you have time:  http://www.azslow.com/index.php/topic,107.0.html
 

You can route the midi input from the controller to a midi track and record it. Then look in the event list for the events that were recorded. That's one way to discover what events occur when you do what physical actions on your controller.
 
It may be that your controller is sending an 'on' event and then an 'off' event you are only mapped to the 'on' event. This might explain why you are having to press it twice. If your soft synth or whatever is only watching for the 'off' even and you have to press the button twice to trigger the 'off' event once, then that would be your problem.
 

Thank you azslow3 and gswitz for the prompt answer.
 
azslow3, Your link is impressively complete about ACT, so I need some time to study it. I admire your dedication to create and provide us with such information. I followed the directions of gswitz (thank you) and recorded the MIDI events; the result was great: I discovered what those buttons were doing. Each time I press a button it triggers one action out of two (on/off), so I think that they are in toggle mode (azslow3). This is what I did (Screenshot: ), I pressed ONCE each of the 8 buttons sequentially, then ONCE AGAIN all the 8 and finally TWICE each one. 
 
After that test I agree with gswitz that the issue is the buttons enable and disable CC parameters, the problem is that each button has two actions and I need only one, e.g.: play/stop. The only two buttons with one action are the 7-Volume and the 10-Pan as they always prompt the same number (0 & 64 respectively). I mapped the 10-Pan button to play/stop and BIGNO!! it worked= one action per button. BUT, I mapped the 7-Volume to the same and nothing happened, I assume it is because it has a 0 Value. Well, how could I change this?
 
So my concern is how to convert the other six buttons to one "single-actioned" buttons. I tried to map the first action to record and the second to stop but it only recognizes the first one, and it is like if the other action did not exist somehow. Result? I still need to press twice to trigger only one action for button.
 
So, my kind people, what do you recommend?

Well I don't know what happened but it did not post the link for the screenshot. Here it is:  
http: //1drv.ms/THwMa0
 
Please remove the space between the http: and the /. I can't put it together because it disappears.

Yes, these buttons work in Toggle mode (one press - 127, another press - 0). CC10 and CC07 are different (see the manual for your device). I have not found how you can change the behavior, it looks like only CC number is configurable.
 
My guess your controller does not "fit" into ACT MIDI/Generic Surface schema. You are welcome to test my "AZ Controller". It can work with your device and it can do more then ACT MIDI. But it can be unstable since no one except myself is tested it...

I am starting to realize that the on/off or toggle buttons are dependent to the CC# assigned to them. I was reassigning my controller buttons (directly in the controller, not in Sonar) so all of them could become 10-Pan Buttons, thing which is possible in my controller although Sonar does not work with it, all I can hear when assigning two buttons to the same CC# is a little click in Sonar and it does nothing. 
 
My next question would be: what other CC# are not on/off controllers apart from #10 which is pan? I tried some at random like #2,3,4,5,6,(#7 is an exception and it always brings the velocity or number to 0 and not to 127),8,9,11, 16,20,42 but all I got was on/off functions. Here you can find a list of the CC from #0-#127 in page 13:  
http:(delete_this)//www.behringer.com/assets/UMX490_UMX610_M_EN.pdf
 
I am finding this experimenting experience great as I am learning a lot. Excuse me I am a rookie in these topics. 
 
azslow3, your AZ Controller looks very interesting. Let me try it and will let you know my results. Thank you.
-------
 
Progress so far: only the CC#10 (Pan) works fine with ACT as it is not an on/off function.

As you can see on the page 9 (just before 4.2.8), only CC07 and CC10 are special. You can save your time testing other...

Well, mmm, I guess you are right. I was really hoping to be able to fully use my UMX610 but I am afraid I can only do it with restrictions. 
 
Thank you all for your help.
 
This forum was really insightful and worthwhile.