Freddie, folks overreact to things.  It is just as incorrect to think we are all like the folks who overreacted to whatever you had posted earlier.
 
I have agreed with you on things in the past, and have disagreed with you too.  At no time did I bash you or anything like that.  And I am not taking your comments to have been directed at me - I am just using that as an example for a larger point.
 
I believe most folks in the forum express themselves in a civil manner, regardless of agreement/disagreement with individuals.  There are of course exceptions, but I believe those are few and far between.
 
Bob Bone

Keni
Hi Freddie...

No, you are appreciated as well... You just get a bit over zealous at times as do I...

I re-write many of my psts before actually posting them to keep watch on myself...

Keni

Thanks Keni!
 
I'm glad you like me. I like you too!  
Thanks for the tips. I think I will follow your "hint" re-write before post.  to eliminate this kind of misunderstandings in the future.
 
 
Have a great week my friend!
Best Regards
Freddie
 

Freddy Fwi I mean no disrespect .. I'm just bustin chops about your fonts size .

Dear Freddie,
You've taken enough abuse for your sales pitch.  But I have to honestly ask:
If you are done with Sonar, and "wont look back," why are you still posting in Sonar forums?
 
I imagine you still feel burned by Cakewalk's communication black out, and letting you go as a long-time customer?  I understand, trust me I'm with you.  But we're all aware of the alternatives, and if someone posts here, they are trying to make the best of Sonar specifically.
 
All said, I don't think it's out-of-bounds to post your impressions of Cubase 7 in the SOFTWARE forum, which exists for "Discussion focused on non-Cakewalk audio software."  And I hope you do:  I for one am very interested in your experience!
 
Cheers!

I left for Cubase after over 10 years with Sonar....and I could not be happier. I still visit occasionally. ..hoping that my old love will come back to me. I just dont see it right now. Cubase is incredible. ...for what ist worth.

Also...I dont write this kind of a post on a whim. Check out my profile....been here a minute. Heck, i bought the v studio (both units) when it was released....how many can say that? And...even though I have moved on to Cubase, I still pop in to keep up with Sonar....it's my first love.

Ive seen Freddie over on the Cubase forum recently. He's a good dude.

Sharke, I've had problems with Waves stuff for years but always seemed to figure out a way to make them work. One thing that is super important when using Sonar or any other DAW that allows you to choose plugin directories....keep 'em separated.
 
One of the biggest issues I've had with the later releases in Sonar, was using the Sonar default folders for all my VST plugins. This has worked for years without a problem until the X series. I've NEVER had 32 bit versions open in 64. So I had to change my directories so that everything is clean and clear. From there, Ryan's instructions fixed me. Reset, rescan and you should be ok. The Xray thing he mentioned didn't work for me though. My Waves GUI in Sonar has been jacked since Waves 6 or 7. The fix for me is to turn the knobs/faders/modules slowly.
 
As for your plug reset thing...uggh, I can't fathom what that must be like. One thing I have noticed that is sort of close to what you're saying is, none of my plug presets ever load up with names. I've just started seeing this in Sonar X and never remember this happening in 8.5. For example, save a plug setting in that plug's VST window, save the project and close it. Reopen open the plug which is on the track and the name I saved is not in the plug. BUT....the preset I saved IS there and can be seen in the menu of the presets window. It just doesn't show the name as THAT loaded preset. I've seen this with plugs I've used in the past that I haven't installed again yet. Open a project in X, the plug isn't there but that fake plug window is and it usually says the name of the preset used even though the plug is not loaded. In the X series, it doesn't say anything.
 
I know you're frustrated. I think stuff like this is harder for a hobbiest to handle than someone that makes an income from it. The reason being, this is your vice...you work all day and can't wait to get into your studio and create music or mix something....only to be faced with more stress and angst than you had at work today because things just aren't working right. I don't have time to be upset. The client is sitting right here next to me with confidence that I will take care of the problem.
 
Sort of like when you'd be with your dad when you were a little kid, and something scary would be happening....your dad always kept his cool and told you "stop worrying, daddy's here" and sure enough, all was well. He never showed fear eventhough he may have been poo'in his pants and it made you stronger to where you didn't worry. LOL! That's how I have to make my clients feel, so I don't have the time to get upset when something happens in "the field" so to speak. By the time I get done with things and have time to be mad, I'm usually too tired to care and would rather sleep. LOL! :)
 
With me thankfully, I can just switch over to another DAW to keep things moving if I have problems. Most times I save .OMF files of my client projects in the event there is a problem, I'm covered. OR I have back up work files that can just be opened on another machine that has another version of Sonar on it if need be. So thank God, it's pretty hard for me to lose any time or work other than if I have to trouble shoot something. But I'm blessed to have several computers and other DAWs if need be to just go with until I find out what the deal is.
 
Anyway, I hope you sort out your issues man. Good luck.
 
-Danny

I did understand from Waves that they are in communication with Cakewalk about resolving the Waves issues. Steinberg has similar issues in Wavelab 7-64bit, where it may not even recognize 32-bit plug-ins at all, maybe to cope with the Waves problem. I think it's a partnered issue, in that Waves decided to use one shell for all plug-ins vs. loading them each as separate .dll's. I believe this is why the install has all software from Waves to install, and you check/tick the plug-ins you want to license. Sonar, on the other hand, and this has been the case with X1 as well, seems to hold a specific Waves plug-in version hostage, preventing itself from locating updated plug-ins, should you download a later sub-version install of the WaveShell.
 
I'm hoping Waves will ditch the WaveShell (I sincerely hope so), and for Cakewalk to build a bit more flexibility in code versions of plug-ins, instead of creating or reading some detailed signature for each plug-in that cannot be changed or Sonar will puke. It's a ROYAL pain to try and update Waves plug-ins because of this.

Danny Danzi
Sharke, I've had problems with Waves stuff for years but always seemed to figure out a way to make them work. One thing that is super important when using Sonar or any other DAW that allows you to choose plugin directories....keep 'em separated. One of the biggest issues I've had with the later releases in Sonar, was using the Sonar default folders for all my VST plugins. This has worked for years without a problem until the X series. I've NEVER had 32 bit versions open in 64. So I had to change my directories so that everything is clean and clear. From there, Ryan's instructions fixed me. Reset, rescan and you should be ok. The Xray thing he mentioned didn't work for me though. My Waves GUI in Sonar has been jacked since Waves 6 or 7. The fix for me is to turn the knobs/faders/modules slowly. As for your plug reset thing...uggh, I can't fathom what that must be like. One thing I have noticed that is sort of close to what you're saying is, none of my plug presets ever load up with names. I've just started seeing this in Sonar X and never remember this happening in 8.5. For example, save a plug setting in that plug's VST window, save the project and close it. Reopen open the plug which is on the track and the name I saved is not in the plug. BUT....the preset I saved IS there and can be seen in the menu of the presets window. It just doesn't show the name as THAT loaded preset. I've seen this with plugs I've used in the past that I haven't installed again yet. Open a project in X, the plug isn't there but that fake plug window is and it usually says the name of the preset used even though the plug is not loaded. In the X series, it doesn't say anything. I know you're frustrated. I think stuff like this is harder for a hobbiest to handle than someone that makes an income from it. The reason being, this is your vice...you work all day and can't wait to get into your studio and create music or mix something....only to be faced with more stress and angst than you had at work today because things just aren't working right. I don't have time to be upset. The client is sitting right here next to me with confidence that I will take care of the problem. Sort of like when you'd be with your dad when you were a little kid, and something scary would be happening....your dad always kept his cool and told you "stop worrying, daddy's here" and sure enough, all was well. He never showed fear eventhough he may have been poo'in his pants and it made you stronger to where you didn't worry. LOL! That's how I have to make my clients feel, so I don't have the time to get upset when something happens in "the field" so to speak. By the time I get done with things and have time to be mad, I'm usually too tired to care and would rather sleep. LOL! :) With me thankfully, I can just switch over to another DAW to keep things moving if I have problems. Most times I save .OMF files of my client projects in the event there is a problem, I'm covered. OR I have back up work files that can just be opened on another machine that has another version of Sonar on it if need be. So thank God, it's pretty hard for me to lose any time or work other than if I have to trouble shoot something. But I'm blessed to have several computers and other DAWs if need be to just go with until I find out what the deal is. Anyway, I hope you sort out your issues man. Good luck. -Danny

Thanks for the advice Danny, I might actually reinstall and reorganize them to make a fresh start so to speak.

Turning X-Ray off didn't work for me either, but do you know what did? A graphics card driver update. I updated my Radeon drivers the first time I had the Waves GUI problems and it didn't improve, but when I updated them again last night it seemed to fix the problem completely, even on the dreaded SuperTaps delay plug with the screwed up tap sliders. So if you're using a Radeon card and haven't updated for a while, might be worth trying. It feels so good to use my Waves plugs and have all the knobs and parameters moving smoothly!

You're totally right about technical problems stinging more as a hobbyist. Yeah I often only have a couple yof hours in the afternoon or evening, and it's so frustrating to have to spend half of that time Googling issues & solutions.

brconflict
I did understand from Waves that they are in communication with Cakewalk about resolving the Waves issues. Steinberg has similar issues in Wavelab 7-64bit, where it may not even recognize 32-bit plug-ins at all, maybe to cope with the Waves problem. I think it's a partnered issue, in that Waves decided to use one shell for all plug-ins vs. loading them each as separate .dll's. I believe this is why the install has all software from Waves to install, and you check/tick the plug-ins you want to license. Sonar, on the other hand, and this has been the case with X1 as well, seems to hold a specific Waves plug-in version hostage, preventing itself from locating updated plug-ins, should you download a later sub-version install of the WaveShell. I'm hoping Waves will ditch the WaveShell (I sincerely hope so), and for Cakewalk to build a bit more flexibility in code versions of plug-ins, instead of creating or reading some detailed signature for each plug-in that cannot be changed or Sonar will puke. It's a ROYAL pain to try and update Waves plug-ins because of this.

Isn't there a way of decoupling the Waves .dll's from the shell? I could swear I read about an app which does that some time ago.

Freddie, I can understand why Cakewalk would be miffed about you posting a Cubase promotion on the Sonar forum, and it's probably best to keep that stuff to the software forum, but I appreciate your points about Cubase and will definitely be checking it out in the future, maybe after I've upgraded my machine (which is the next step). Don't get me wrong I love Sonar in so many ways, and I'll never forget how much easier I found it to get a good sounding mix in Sonar than I was getting with Pro Tools, but I find Sonar lacking a little in comparison with Cubase, Abelton etc with respect to the kind of features which producers of EDM and other forms of electronic music would find useful. Especially when it comes to organizing project arrangements and implementing complex automation etc. I've toyed with the idea of ReWiring Abelton into Sonar as well, or even using Maschine. I just it wasn't so much hassle to road test other products!