VST plugin settings keep resetting. -- Fixed. Viva la Sonar!

[class="post"]I've been using Sonar 7 Producer for a few months but mostly for pure audio track recording.  I recently finished a project with mostly audio and one VST - Addictive Drums (awesome drum VST!) - which I triggered with my TD6. No problems there.

Now I'm working on a project that's mostly VST midi tracks and I'm seriously considering switching to another DAW.  The problem is that the VST settings keep resetting to the VST default when I hit play.  I disabled the "Zero Controllers When Play Stops" option in the 'Project settings' and now it resets the VST's less often but it still does it very frequently, especially when I change the start point. 

One example of a VST I'm using where this is happening is the Pro-53.  This is a very commonly used synth so I know it's not just cheesy plugins.  Anyone else have this problem?  I've spent some time searching the Cakewalk forums and it seems these types of issues with VST's are somewhat common. 

If I can't resolve this I'm probably going to switch to Cubase.  I'd rather not have to spend $450 or learn a new DAW but ****.  This is such a simple problem and it's ri-goddamn-diculous that I'll have to abandon Sonar because of it, but it's a major issue. 

Tell me I'm overlooking something simple!  Any insights are HIGHLY appreciated.

This might be something that Sonar 8 producer has addressed. Perhaps you need to upgrade to Sonar 8 and then to the current version which is 8.3.1 If you look at the list of things that have been improved, VST instruments are certainly involved in that.

OK! So you saved settings in the VSTi. Now try saving it in CW presets  located at the upper left side edge of the plugin UI itself (it's a dropdown menu) and see how that goes.

The problem is that the VST settings keep resetting to the VST default when I hit play.

Which VST settings are you talking about? The whole AD setup, e.g. instrument selections, panning/mixing/EQ? Or SONAR-controlled parameters such as channel assignments, volume envelopes and routing?

Thanks for the suggestion.  This doesn't work either.  The most annoying thing is that it will hold the settings for a minute or so, and through a few presses of 'play', but then it reverts back to the default voice for the VSTi. 

One of the VSTi's I'm using had both a VST save and a Sonar save option, both located in the upper left corner of the plugin UI, with only the button with an 'X' between them.  The other had only a Sonar save option. 

Which VST settings are you talking about? The whole AD setup, e.g. instrument selections, panning/mixing/EQ? Or SONAR-controlled parameters such as channel assignments, volume envelopes and routing?

The only thing I'm focusing on at the moment is the instrument selection.  It keeps reverting back to the default, Instrument 1. 

After it reverts to Instrument 1, it will actually still show the instrument I've selected in the 'Presets:' field in the upper left corner of the plugin UI, even though the lower portion of the plugin UI where all the knobs and sliders and hoohas are will have reverted back to the settings for Instrument 1.  There's gotta be a solution to this!

For instance, in the SoHaSonata VSTi, I'll select preset 56:cygnus and cygnus will play as the voice on that track for a short while, then it will revert to preset 1:crystal pad, even though "56:cygnus" will still be displayed in the 'Presets:' field in the upper left of the plugin window.  And even though it will still say "56:cygnus" in the 'Presets:' field, all the settings in the plugin UI will be changed back to the settings for preset 1:crystal pad.

In the Pro-53 VSTi.  I'll select the preset "Analog Fretless" and Analog Fretless will play as the voice for a short while, then it will revert back to "Thin'n Cold" with all the Thin'n Cold settings, even though it still says "Analog Fretless" up in the 'Presets:' field.

I don't have this issue.  Are there program changes in your sequences?

Jim

Ahh, check the events list as you playback. I had a similiar issue and found an unintended event that was the culprit.

F@KKER

I was also just about to suggest there may be Program Changes
(or maybe midi controller commands) in your song somewhere.

If a VSTi keeps "resetting" something must be causing it.

Well I'll be...there were two patch change events, both specifying Patch 1, in the event list before the first note even sounds.  Don't know why those are in there but I changed it to specify the Patch I want.  I suppose I could even delete them.   I'm pretty new to midi so I'm not surprised I overlooked that.

I am really grateful to everyone who replied, that was really getting discouraging!  I knew it was something stupidly simple.  This is a great forum!

How about changing the title of your thread to reflect the fact that you love Sonar now?
 
Brian

Done!