X3 - Voxengo Soniformer VST3 - Settings Not Retained

Make sure you are on the latest version of the plugin.
Install X3D, then please perform a VST reset.
Then see what happens I suggest...
Thanks.

Please let us know how the reset goes.

Ouch sorry about that... All I can really suggest myself is:
 
* Get the latest plugin update
* Check the behaviour with other VST3 plugins that come bundled with Sonar to see if this happens.
*Try running Sonar X3 as Administrator, if you are already try the opposite.
 
Thanks...

Hi.
I'm having the same problem with Fabfilter Mastering plugins VST3 version,
no problems with VST2.
Had to change the plugs to VST2 in order to keep the settings after saving and opening project.
 

Actually no that is out of context, full quote here:
 

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.

 
.. in that thread (I'll paste it in as it wasn't pasted):
http://forum.cakewalk.com...23699-m2976784-p4.aspx

... Noel identified specific plugin issues with Waves and DMAudio plugins (with their code), he has put in some workaround code however I'm not 100% sure how this would effect Voxengo plugins but it's probably along the lines of what I've highlighted in bold.
 
Probably best to inform Voxengo about this so they are in the loop, although it might not be the same as Waves or DMG, it's probably a similar problem though that needs fixing at their end...
 
I also suggest you point Voxengo to this:
http://forum.cakewalk.com/New-article-on-X3-VST-internals-m2976078.aspx
 
 
 
 

Noel Borthwick [Cakewalk

Guitarmech111
Alex, Logic would preclude that something broke X3D if it works as expected in X3C. I understand code and release processing of code as well as regression of code. I am waiting for feedback still on my trouble ticket. I know Waves and Cakewalk have a good communication established and we shall get an answer on this soon I hope.
Let's just agree to wait and find out what the bakers or Waves confirms and let this thread breathe a little. ;)

 
That logic is flawed. While it can be used as a thermometer for general troubleshooting, in the software world you cannot compare two different inter-operating components A and B and conclude that if a problem arises after a change in A it can be implied with certainty that the change in A is the root problem. In this case a change in A to add a new feature exposed a bug in B that causes the problem.
 
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
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.