Has anyone had the problem of their Waves plugins not retaining the adjustments they've made to a setting when opening a project in X3?
 
I have the Manny Maroquin bundle and Silver bundle and have saved presets for my effects chains in plugins such as the Mono MM Distortion and some MM delays. When I have finished a mix and save and close the project and re-open it, the settings have gone back to a default and I have to then manually go through all the plugins and reload my customised presets. It's quite time consuming!
 
I have had Waves tech support look at my computer remotely and they are sure that the plugins are working properly, and suspect that it's a Sonar issue. I haven't heard back from Cakewalk support as yet. 
 
What I need is for my projects to open in the state I last left them. I am using Windows 7 operating system, Sonar X3 Producer (32bit version), and the Waves plugins. I have installed all the X3 updates.
 
Any advice would be greatly appreciated :)

Hello Steve and welcome...
 
 
After a giant discussion on a previous thread here what you need to know; Waves should (hopefully) be working on a fix:
 

Noel Borthwick [Cakewalk

I have debugged this issue and the root problem is that the preset mechanism in several VST3 plugins is not fully implemented according to the VST3 spec. Presets can be changed in a bi-directional way - via the plugin UI or from the host UI. When the host sends a preset change request the plugin should change its preset and update its UI and internal state. Conversely when a preset is changed from the plugin UI it is up to the plugin to send a notification to the host to allow it to sync up its state and UI to the plugin. What is broken here is that the plugin's are not sending the notification back to SONAR and this puts it out of sync. Now when you save the project we save the state that SONAR knows about which is incorrect and when you load it back you get the incorrect state that you are seeing.
 
In the case of Waves plugins it appears that they never update the current program state when it is changed from their internal UI. I have reported this to their engineering team for review.
In the case of DMG plugins they do update the current state, but never notify the app so we don't know it was changed.
I have passed on information to both DMG and Waves about how to send back a preset change notification to the host.
See the section on Bi-Directional setting of programs here.
 
Additionally I have added some failsafe code for the next update to prevent settings being lost even if the preset is out of sync (the UI will display the wrong preset name but the plugin state will always be intact when you load a project). I've also added code to make the bidirectional communication work using a different method. This also translates to VST2 so its nice that VST2 plugins will also stay in sync when presets are changed from the plugin UI.

 

Noel Borthwick [Cakewalk
X3D implemented full support for VST3 factory preset management which is a new feature that didn't exist in X3C. When we did that it exposed problems with bi-directional support with some VST3 plugins.
I have already reported the issue to Waves with full details. Keep in mind that the workaround in SONAR will prevent the wrong settings being loaded but won't fix the problem with preset changes in the plugin not updating the host. So the preset picker will be out of sync until that is fixed from the plugin side.

 
Hope this helps...
 
Thanks..

So in the interim the way to manage your presets is to use the plugins own preset picker to open existing ones and save your own presets.

CakeAlexS
Hello Steve and welcome...
 
 
After a giant discussion on a previous thread here what you need to know; Waves should (hopefully) be working on a fix:
 

Noel Borthwick [Cakewalk

I have debugged this issue and the root problem is that the preset mechanism in several VST3 plugins is not fully implemented according to the VST3 spec. Presets can be changed in a bi-directional way - via the plugin UI or from the host UI. When the host sends a preset change request the plugin should change its preset and update its UI and internal state. Conversely when a preset is changed from the plugin UI it is up to the plugin to send a notification to the host to allow it to sync up its state and UI to the plugin. What is broken here is that the plugin's are not sending the notification back to SONAR and this puts it out of sync. Now when you save the project we save the state that SONAR knows about which is incorrect and when you load it back you get the incorrect state that you are seeing.
 
In the case of Waves plugins it appears that they never update the current program state when it is changed from their internal UI. I have reported this to their engineering team for review.
In the case of DMG plugins they do update the current state, but never notify the app so we don't know it was changed.
I have passed on information to both DMG and Waves about how to send back a preset change notification to the host.
See the section on Bi-Directional setting of programs here.
 
Additionally I have added some failsafe code for the next update to prevent settings being lost even if the preset is out of sync (the UI will display the wrong preset name but the plugin state will always be intact when you load a project). I've also added code to make the bidirectional communication work using a different method. This also translates to VST2 so its nice that VST2 plugins will also stay in sync when presets are changed from the plugin UI.

 

Noel Borthwick [Cakewalk
X3D implemented full support for VST3 factory preset management which is a new feature that didn't exist in X3C. When we did that it exposed problems with bi-directional support with some VST3 plugins.
I have already reported the issue to Waves with full details. Keep in mind that the workaround in SONAR will prevent the wrong settings being loaded but won't fix the problem with preset changes in the plugin not updating the host. So the preset picker will be out of sync until that is fixed from the plugin side.

 
Hope this helps...
 
Thanks..

Waves AND Cakewalk are both working on this.

This bit Cakewalk is working on is in bold, what Cake is doing is an enhancement to workaround buggy plugin code:
(it's all in Noel's quote anyway), it's unlikely to "fix" the full issue however.
 

Noel Borthwick [Cakewalk

I have debugged this issue and the root problem is that the preset mechanism in several VST3 plugins is not fully implemented according to the VST3 spec. Presets can be changed in a bi-directional way - via the plugin UI or from the host UI. When the host sends a preset change request the plugin should change its preset and update its UI and internal state. Conversely when a preset is changed from the plugin UI it is up to the plugin to send a notification to the host to allow it to sync up its state and UI to the plugin. What is broken here is that the plugin's are not sending the notification back to SONAR and this puts it out of sync. Now when you save the project we save the state that SONAR knows about which is incorrect and when you load it back you get the incorrect state that you are seeing.
 
In the case of Waves plugins it appears that they never update the current program state when it is changed from their internal UI. I have reported this to their engineering team for review.
In the case of DMG plugins they do update the current state, but never notify the app so we don't know it was changed.
I have passed on information to both DMG and Waves about how to send back a preset change notification to the host.
See the section on Bi-Directional setting of programs here.
 
Additionally I have added some failsafe code for the next update to prevent settings being lost even if the preset is out of sync (the UI will display the wrong preset name but the plugin state will always be intact when you load a project). I've also added code to make the bidirectional communication work using a different method. This also translates to VST2 so its nice that VST2 plugins will also stay in sync when presets are changed from the plugin UI.

 

Noel Borthwick [Cakewalk
X3D implemented full support for VST3 factory preset management which is a new feature that didn't exist in X3C. When we did that it exposed problems with bi-directional support with some VST3 plugins.
I have already reported the issue to Waves with full details. Keep in mind that the workaround in SONAR will prevent the wrong settings being loaded but won't fix the problem with preset changes in the plugin not updating the host. So the preset picker will be out of sync until that is fixed from the plugin side.

 
Hope this helps...
 
Thanks..

Alex, Cakewalk IS working on this regardless of what you try to say. They are trying to prevent issues from coming up in the future. I hope this helps...

By the look of it what I said in my last post is exactly the same as what you said in your follow up post :)
So we agree! (Anyway what Ryan said forget what we say).
 
Cheers!

good! I am not in for another marathon thread...
 
The only thing that bugged me was that you eluded to Waves being at fault when in reality, we do not know the total story. We do not know if CW informed Waves that the VST3 preset standard would be fully implemented in, or prior to, X3D or if Waves knew and chose not to have it fixed yet. That is why I said BOTH CW and Waves are working on it. I do not care to place blame, but I do think it is best to place the issue squarely on BOTH parties, not just Waves until we know different.

> until we know different.
 
Well what know is what Ryan said which is pretty clear cut as to where the fault lies. If there is a difference of opinion then I would expect Waves to speak up, somehow I doubt that is going to happen. Us being judge and jury about this is a little futile as none of us have the source code, and nor will we ever (well maybe in 30 years). We shall see what happens but speculating won't help matters, I'm listening to what has been said by Cake right now and I have no reason to doubt them.
 
> good! I am not in for another marathon thread
 
Anyway yes please no more last word thing.

ok