If you Google "Sonar X3 give keystrokes to plugin" you'll find dozens of complaints of same, many on the CW forums. And a mid-page 44 post in this thread (by Gonga, and replied by Flugel45) is what brought me here through a search.
Thanks for the workarounds Pwal and JoseC! I'm aware of those ideas, but as a fairly active patch creator/modifier I find those processes a real hindrance to my workflow and concentration, as I tend to make several versions of patches as I develop them, and like to make fairly extensive notes about how to play or modify the patch in performance. All this cut and paste is ridiculous! Just fix these bugs CW!!! (but I appreciate the workaround mentions!)
Never had these problems in previous Sonar versions, even using other U-He plugins, including demos of Zebra2.
And to be honest, as loyal as I've been to Sonar through the years, my thrill over Zebra2 far surpasses my love for Sonar X3 (as most DAWs seem quite similar these days)! So if there is no fix for these issues (we are talking 2 issues!), I'd rather find a new DAW than play Zebra2 and other U-He plugins with one hand tied behind my back for the rest of my life with Sonar!
I asked Rob at U-He about this issue and he assures me it's "a well-known and long submitted bug with Cakewalk". And there must be some truth in that, because I see others complaining (with bug submissions) for years about the exact same problem with other developer's plugins, and on the CW forum too.
And regardless of who is dropping the ball on this bug fix - SOMEONE SOMEWHERE needs to work with all parties involved and fix it! I consider U-He to be a fairly major plugin developer, and if anyone complained my DAW wasn't working correctly with their products, I'd want to work it out and fix it ASAP.
And there's no way U-He is in any way responsible for the key-binding in Sonar X3 not working correctly! CW can step right up to the bar on that one! At least allow us to disable it completely.
