Deleted to keep things simple.

Everything is working correctly now with 1 exception.
When I click on the EQ module the knobs don't detach from the strips.
When I was using the normal ACT controller (that had 8 tracks), the controls were completely 
contextual. - If I clicked on the EQ it controlled only EQ things. If I clicked on a track strip
it controlled only the fader and pan.
 
This controller appears NOT to be able to be used contextually.
If every time I adjust and EQ gain knob it destroys a track's pan settings, that is obviously useless to me.
 
I would appreciate someone clarifying why this is happening and/or telling me how to correct this.  

Please read the plugin documentation and watch ACT videos to understand how it works (may be several times). I am so stupid that I in fact could not realize the whole story till I have written my own DLL, I hope you are smarter then me 
 
There are just several tips for your problem:

• Strip parameters are bound to tracks (which are specified by WAI, bound to "BaseTrack" and "Number of Track Strips" in the configuration window). These parameters/controls are independent from what you currently select in the interface.
• ACT (lower part of the configuration window) controls current selection (plugin, pro-channel, fx)
• If "Both" is set, both assignments are applied. So if you use the same MIDI command for "Parameter 1" of Strip 1 and "ACT Controls" (1), both parameters will be changed simultaneously. That mode is only useful in case you do not unsigned one physical control to strip and ACT parameters. 
• If "Both" is unset, which parameters (stip or ACT) are controlled is specified by "ACT Enable"  (which is assignable to button on your surface, so you can fast switch). In that case you can assign the same physical control (fader,rotor,button) to some strip parameter AND ACT parameter.
• if "Lock Context" is set, ACT will control the context during which this flag was set. Again you can assign some button for this switch. Then, for example, you can select something in pro channel, "Lock" the selection, open some VST and still control parameters of that pro channel module.

Sorry for so long text, but I hope that can speedup a bit your learning curve...

azslow3, please read my last post (edited around the same time you posted).
 
So you know, I did watch many videos on how to use ACT. I was using and configuring it successfully before (just that I couldn't set it to only 4 tracks). 
There appears to be no configuration of settings in the generic controls that allow me to use it contextually though. - Gain knob in the EQ is still controlling Pan in the track. 
 
EDIT: Worst case scenario I could open the panel each time and check/uncheck the "both" box (when switching
from track to EQ). Obviously I would prefer not to have to do that though..
 
 

Edited... You should unset "Both" permanently and assign some (special, not shared!) button to "ACT Enable". May be my explanations/english are too bad. Sorry.

azslow3
Edited... You should unset "Both" permanently and assign some (special, not shared!) button to "ACT Enable". May be my explanations/english are too bad. Sorry.

IT'S WORKING!
I didn't realize that unchecking both ACTenable and Both was an option!

Thanks for the help!
 
I really need to go to bed now because its 4:30am here.
 
Again. Everything is working now.
 
Thanks. 

I kept playing around.
I can't get it to switch to the BUS area. 
Is there no way to do this?

*Going to bed, will come back after waking*
 
Thanks. 

justmebrah
Everything is working correctly now with 1 exception.
When I click on the EQ module the knobs don't detach from the strips.
When I was using the normal ACT controller (that had 8 tracks), the controls were completely 
contextual. - If I clicked on the EQ it controlled only EQ things. If I clicked on a track strip
it controlled only the fader and pan.
 
This controller appears NOT to be able to be used contextually.
If every time I adjust and EQ gain knob it destroys a track's pan settings, that is obviously useless to me.
 
I would appreciate someone clarifying why this is happening and/or telling me how to correct this.  

 
In the Cakewalk Generic Surface properties page, you have to have a check mark in the "both" box under Use ACT or Strip Params. Do you have that box check marked?
 
The problem I discovered is that my controller assignments are not remembered by SONAR, but they are supposed to be remembered. I have to keep re-assigning the knobs to the ProChannel EQ knobs every time I re-open a project.
 
Another couple of things to note:
 
You can still use the ACT Controller Plug in with your M-Audio control surface, even though the M-Audio CS only has 4 sliders. Just don't assign any controllers to 4 slider pads on the ACT Controller Plug In, leave them blank.
 
Also, the Cakewalk Generic Surface and the ACT Controller Plug In can both be used at the same time in the same project. Just make sure controllers assigned in one are not assigned in the other.
 
For example:
 
Your M-Audio controller has 12 rotors, you can assign 8 of them to cells on the ACT Controller, and assign the other 4 to fields on the Cakewalk Generic Surface  properties page.
 
There is a learning curb to using the Cakewalk Generic Surface and ACT Controller Plug In. It's really a good idea to read about using them both in the SONAR Reference Manual or SONAR Online Help.
 
As stated above, I've experienced a problem with the CGS and the ACT Controller, so my vote is in for an update for them both. However, the word around is that Cakewalk doesn't have it high on the list to update these plugins. Nevertheless, Cakewalk has released to the public the source code for the ACT Controller plug in and other SONAR software controller plug ins (see this thread: http://forum.cakewalk.com/Mackie-Control-protocol-source-now-available-scroll-to-p3-m2908006.aspx ), so that the SONAR community could adopt development for them and share progress with the community. That could possibly be good for us, but I hope Cakewalk will continue developing and updating controller plug ins, as well.
 
Hope that helps

OK I see azslow3 is helping you. He's a programmer. I reckon he knows more about this stuff than I do.
 
Goodluck on getting your control surface working like you want it to work.
 
Cya around.