Just opening the project in X3D produces the incorrect results here. I am also on Win7 64 all around and Waves VST3.

Guitarmech111
Just opening the project in X3D produces the incorrect results here. I am also on Win7 64 all around and Waves VST3.

Can you send me just a .cwp (no audio) and a screen shot of the desired settings? I can open it here and see if I can reproduce it with your project.

Another thought. FX-Chain (on track or bus) in Pro Channel or not. Or, simply FX-Bin?
 
I'm using FX-Bin.
 

Whatever you do don't try and do this - worse still, supply any useful information that you may have done this.
And yes rescan is what you do after the RESET ;) But I'm probably going too far now so I'll just disappear somewhere else.

FX bin only - you can repro a simple project like I outlined. It does the same thing. It opened funny when I tried to in X3D and he had zero presets for that plug setting. Kust tweak some settings and save the project. My buddy has the original project so I am not able to send it.

Guitarmech111
FX bin only - you can repro a simple project like I outlined. It does the same thing. It opened funny when I tried to in X3D and he had zero presets for that plug setting. Kust tweak some settings and save the project. My buddy has the original project so I am not able to send it.

Well, as I reported above that's what I have done and it works here.
 
The ONLY way I can make it fail (lose the tweaked value) is if I load a preset from the SONAR preset menu

Mo matter what I do to the values, after saving they revert back.
 
However if I simply load a WAVES plug (any plug) and tweak the values, after a save the tweaked values are retained.
 
Finally, if I load a preset from the WAVES menu (on ANY Waves plug)

and I tweak the values, after a save the values are retained.
 
See the difference?

But this just happens on waves plugins and some other third party (assuming you all did a VST reset). If it works with other plugins... well work it out for yourself... Has anybody contacted Waves and pointed them to this thread?

Alex,
What are you implying should be worked out?
A plugin works fine in X3c and then the same plugin, under the same circumstances, acts differently (doesn't work) in X3d. Are you implying this is the fault of the plugin? Just because *other* plugins work OK?
 
You would be a lot more helpful if you changed your default position from "Cakewalk software is perfect and bug free - because it works for me" and considered that there are other users here who know what they're talking about - and are experiencing real problems (and trying to work out solutions).

Yes that is my opinion and I'm entitled to it, I have stated my logic and you have stated your logic. You may have another opinion and that is fine, but please remember software is built up upon dependencies so just because it works on a patch but not on another patch this is no smoking gun, neither of us have the source code so argueing over this is futile and silly.

Still nobody has stated they have done a VST reset (so we are never allowed to ask this any more as this is the most obvious thing to do right? And to repeat again not a rescan, a reset) and my actual question was ... Has this been reported to waves etc? I can't see anything unreasonable about asking this as well other than this being 'too obvious'.

Thanks..

jbraner
You would be a lot more helpful if you changed your default position from "Cakewalk software is perfect and bug free - because it works for me" and considered that there are other users here who know what they're talking about - and are experiencing real problems (and trying to work out solutions).

http://forum.cakewalk.com...aspx?m=2952585&p=1