it worked pre-x-series, and steps to reproduce are included above :-)

eta, the specific issue is that "Give All Keystrokes To Plugin" doesn't work with all plugins ;-)
 

Well, there are 2 clear issues, both all too easily reproducible, as I explained above.
 
The main problem for me is the "Give All Keystrokes To Plugin" button function doesn't work correctly with at least U-He Zebra2, but I see many other plugins listed in other queries on the general subject.  In the 11 years or so I've been using Sonar 6, I never had to touch the "Give All Keystrokes To Plugin" button even using various U-He offerings including Z2 demo, and in fact I was not even aware this button existed until this issue in X3E.  And I would LOVE to experience the same workflow with X3E, and beyond, as I had with v6!  I've just purchased Z2 and there must be 10k soundsets for it, and as an avid patch modifier/creator/explorer, the inability to rename and add performance info notes to patches is extremely frustrating, and a real workflow killer! (yes, I realize I can work-around using Notepad or Sonar text entry areas - but what a pointless pain!!!)
 
Then the second issue that kills a decent work-around is Sonar X3E's inability to unbind all Sonar key-bindings, as explained in my original post.  And I've fought and researched this situation for hours and hours!  BUT, I wouldn't be surprised if I found out I was doing something wrong somewhere, as both X3 and Z2 are new to me, and a little confusing in their complexity and options, so that brings me here...    :)
 
The two issues together are just a nightmare!
 
Thanks for any and all help!
 

The question I would ask is why does it work with the vast majority of plugins and relatively few others. The standard conclusion would be in this scenario that it is a third party coding issue (the VST does something in a non standard way perhaps). However as I don't have the Sonar or third party plugin code in front of me I can't say I am entirely correct (nor can anybody).

Also it may be wrong to say all the third party plugins are suffering the same problem (maybe the same symptoms).

BTW none of these are VST3 plugins? If so try VST2.

My recommendation would be to ring Cakewalk support.

I agree with your basic POV, Alex, and that's the first thought that came to my mind.  But by the same token one might say; all U-He plugins worked perfectly before the X series, and now don't, and the U-He plugins haven't changed - the Sonar app has. 
 
But whomever is to blame for these situations (there's no way to blame U-He for the Sonar key-binding being unbindable!), I would think Cakewalk would want to contact and resolve this U-He issue ASAP, as I consider them a fairly major developer.  And from what I hear no replies have been received by anyone reporting such problems and/or submitting said bugs, since the X series began.
 
And to be honest, my thrill of Zebra2 far exceeds my dedication to Sonar, at this point (I mean most quality DAWs seem quite similar these days)!  It's a definite deal-breaker for me, I'm sorry to say.
 
Maybe a call to Customer Support is in order, but a trip to a backwoods dentist sounds less painful!  
 
 

I think it would be worth trying to perhaps CALL Cakewalk technical support on this one, if you can at all do that.  It's a pain to take time out of the day to do so, but perhaps some real-time discussion with them might shed some light on what is happening, since you can reproduce this.
 
Question - are these particular plugs 32-bit or 64-bit, and are you running Sonar Xe3, and if so, is Sonar 32-bit or 64-bit?
 
Thanks, 
 
I'll also do some digging later on this morning, and I will post back if I can come up with any more questions or info.  Hang in there, 
 
Please Bakers - can someone jump in on this one - it may affect multiple folks out there.
 
Bob Bone
 

I have just checked that with TyrellN6 and X2 32bit (under Linux). My observations (with "Give All Keystrokes To Plugin" activated):

• when I am simply focusing Tyrell, all keys I have tried produce no effect for SONAR ( 'P', 'W', 'Space')
• if I open "Save preset" dialog, 'Space' and 'W' has no effect, but 'P' has (opens SONAR property)

If "Give All Keystrokes To Plugin" is deactivated, all keys are processed by SONAR (as expected).
 
I can think about possible reason in case either all keys are blocked or all keys are not blocked. But I have no idea why the blocking can be "selective".

FWIW this also happens with cakewalk synths that have popup windows.  For example: insert rapture, bring up the rapture ui, enable give all keystrokes to plugin, open rapture's modulation matrix window, double-click on depth field, type 5.  Sonar switches to screenset 5.

swamptooth
FWIW this also happens with cakewalk synths that have popup windows.  For example: insert rapture, bring up the rapture ui, enable give all keystrokes to plugin, open rapture's modulation matrix window, double-click on depth field, type 5.  Sonar switches to screenset 5.

 
Good catch! But as far as I can tell that happens only in the mod matrix window. On the main page, if you double-click on a field, you can type in a parameter value regardless of whether "give all keystrokes to plug-in" is enabled or disabled. I never noticed  because I always use the scroll wheel.

thanks, craig.  having a load of fun with electronic guitars, btw.  nice work!