This used to and still happens to me too! Very frustrating! Instead of freezing, Try using 'Bounce to Track'. Either pre-create and label a destination audio track or simply bounce to a new track. You Must highlight the midi track AND the synth audio track for the audio to bounce. Once bounced you can right click on the synth in the synth rack and unload the synth to save resources and prevent hearing the doubling. You can always right click and reload it back if you need to rebounce or say bounce a different mic position of the same instrument e.g. piano close mic, player mic, room mic.. I haven't experienced anything changing in a synth that has been unloaded and then reloaded. I certainly have been burned by freezing and un-freezing though!! I also save the presets for future using and back up.

to come back to this thread... now it is effecting EVERY softsynth!   Every single one!  Same project, just been using it for a while with frozen tracks.  Seriously - a MAJOR problem...

SilverBlueMedallion
to come back to this thread... now it is effecting EVERY softsynth!   Every single one!  Same project, just been using it for a while with frozen tracks.  Seriously - a MAJOR problem...

Agreed. Of all of the 'quirks' of Sonar this one is a major PITA that has cost me lot of time. It's been around a while though, so I wouldn't hold my breath for a fix:(

i wonder if it's related to melodyne/freeze/crash http://forum.cakewalk.com/FindPost/3536840

so i made a post in the bakery about it, is that the place to get their attention now?  this is all too confusing.

what is interesting is that, i have another project where this is not an issue.
 
somewhere along the way, something screws up a project.  Wish i knew what.

SilverBlueMedallion
what is interesting is that, i have another project where this is not an issue.
 
somewhere along the way, something screws up a project.  Wish i knew what.

Yes - I have many new projects were it is not an issue, but I also have a large number (150 + ) that lost all of their patch assignments when re-saved with archived tracks containting disconnected vst synths. It was a group of projects that all had small changes made to them over a couple of days about 18 months ago just after an update release. A further quick fix was released a couple of days later to address issues, so I presumed at the time that it was caused by that particular release as I had never seen it previously. I have had it happen on a couple of projects since, though not to the same extent as that particular catastrophe. I posted problem reports etc but did not receive a response. 
 
The issue seems to occur in isolated cases, but with reasonable frequency. It happens upon saving projects with tracks that contain disconnected vst Synths, be they frozen or disconnected/archived,  however I have never found a method to consistently reproduce it. Now I am in the habit of including the patch name and number in the track name. It certainly doesn't make it any less annoying though!
 

tenfoot
The issue seems to occur in isolated cases, but with reasonable frequency. It happens upon saving projects with tracks that contain disconnected vst Synths, be they frozen or disconnected/archived,  however I have never found a method to consistently reproduce it.

Bitflipper is pretty sharp. His post above may be hitting the nail on the head...the act of disconnection itself may be in conflict with the VST spec.

Anderton

tenfoot
The issue seems to occur in isolated cases, but with reasonable frequency. It happens upon saving projects with tracks that contain disconnected vst Synths, be they frozen or disconnected/archived,  however I have never found a method to consistently reproduce it.

Bitflipper is pretty sharp. His post above may be hitting the nail on the head...the act of disconnection itself may be in conflict with the VST spec.

True, but I have been using the archive/disconnect method for many years without issue until the above incident. Even since then it does save the patch 99% of the time. Given the seemingly random nature of the problem, it seems to me that there must be some combination of variables that cause the patch save to fail. If it was just that it was outside of the vst spec and Cakewalk had not accounted for that, I would think it should fail consistently.

how do we get THIS thread to be seen by the bakers?