• SONAR
  • Cakewalk, Is The Bug With Sonar Stealing Keystrokes From U-he Synths Going To Get Resolved (p.3)
2014/10/29 18:50:15
Anderton
swamptooth
thanks, craig.  having a load of fun with electronic guitars, btw.  nice work!

 
Thanks! I use it all the time myself. BTW I'm working on additional guitar-oriented expansion packs...being at Gibson gives me access to the World's Ultimate Lending Library for Guitars.
2015/01/26 15:42:48
Mitch_I
Good news. I think this is fixed.
 
I just installed the new Sonar, and I'm trying a few things out. Here's the procedure I tried in X3 and then in Sonar Platinum:
 
1. Open Zebra, Diva, or Bazille.
2. Open the patch browser.
3. Click the Give all Keystrokes to Plug-in icon.
4. Select a patch and click Save.
5. In the Enter Presetname box, type some letters and numbers.
 
In X3 the results depend on what you type. In other words, Sonar still owns most keystrokes.
In Platinum the text you type appears in the box as you type it. No surprises.
 
Thank you, Cakewalk!
2015/01/26 16:00:45
Splat
I have a feeling we are going to be seeing a lot more posts like this soon... Exciting times..
2015/01/26 22:32:21
skitch_84
Mitch_I
Good news. I think this is fixed.
 
I just installed the new Sonar, and I'm trying a few things out. Here's the procedure I tried in X3 and then in Sonar Platinum:
 
1. Open Zebra, Diva, or Bazille.
2. Open the patch browser.
3. Click the Give all Keystrokes to Plug-in icon.
4. Select a patch and click Save.
5. In the Enter Presetname box, type some letters and numbers.
 
In X3 the results depend on what you type. In other words, Sonar still owns most keystrokes.
In Platinum the text you type appears in the box as you type it. No surprises.
 
Thank you, Cakewalk!



I had the same issue when trying to register U-He's Satin plugin. I was able to workaround the issue by just copying and pasting the text as others have mentioned. I should add though, when you're naming presets or the like, it doesn't have to be even as complicated as opening Notepad, typing it there, and then copying and pasting the text. You can just type it anywhere in Windows and copy and paste it. If you're on Windows 8, just hit the "Windows" button on your keyboard, start typing the name of your preset and it will automatically enter what you're typing into the search bar. You can copy and paste it from that. I only requires you to press one button, type what you want, then CTRL+C, CTRL+V into the synth's text box :)

I'm glad to hear that the problem appears to have been fixed in Platinum though. Despite an easy workaround, it's still an annoying thing to have to deal with :)
2015/01/28 15:05:32
SFAM
Mitch_I
Good news. I think this is fixed.


I hope you're right, Mitch! 
 
I'd love to hear from a few more users saying this issue is fixed before I spend more money on this software!  In truth, I really don't feel like I should need to buy another version (in less than a year) simply to get a bug fix!!!  I REALLY think Cakewalk should apply this fix to the X Series!  I guess the Sonar X Series is going to be "Cakewalk's Vista"!
 
But, I have too many ongoing projects in Sonar to simply Walk Away (James Gang), so if this is ONLY going to be fixed in the NEW series, I'll probably sink more money into the beast, because it sure is a major workflow killer as it is now!  And unfortunately, I've lost my trust in the once mighty Sonar and Cakewalk over this long-standing issue (since X1 ferchristsake!) and its lack of attention, and already exploring new... (I almost said Vistas - but I have THAT!)  DAW software.
 
Any others seeing this issue (actually 2 issues!) fixed in the NEW Sonar versions?  Thanks!
 
 
And a big THANKS to Craig Anderton for a lifetime of fun and inspiration (back to the PAIA days)!  Following your project schematics was instrumental in my developing love of electro-modifying and general hardware mayhem!
2015/01/28 15:14:23
scook
Yes, it is fixed.
2015/02/04 18:01:34
SFAM
Thanks for the confirmation, scook!
 
Now, if Cakewalk would please provide a patch for the X3 line, so I don't have to spend more money to experience a well-known bug fix in their past product line(s)! 
 
 
2015/02/05 06:08:45
TabSel
NOW I'm pretty curious how Cakewalk will handle this warranty issue.
 
Please report back any news!
 
 
2015/02/05 07:44:24
mudgel
SFAM
Thanks for the confirmation, scook!
 
Now, if Cakewalk would please provide a patch for the X3 line, so I don't have to spend more money to experience a well-known bug fix in their past product line(s)! 
 
 

Cakewalk don't patch older versions. Once a new version is released that's it.
2015/02/05 10:16:37
Anderton
mudgel
SFAM
Thanks for the confirmation, scook!
 
Now, if Cakewalk would please provide a patch for the X3 line, so I don't have to spend more money to experience a well-known bug fix in their past product line(s)! 
 
 

Cakewalk don't patch older versions. Once a new version is released that's it.



True. Unfortunately, that's the way most software works. I've been told by other companies when I made the same inquiry that going back and doing regression testing on older versions for a subset of bug fixes (e.g., part of a bug fix update for a new version could cause problems with older versions where the feature being fixed didn't exist) is time-consuming and not factored into the initial cost of the software. I assume the answer from Cakewalk would be the same.
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account