Yeah - and I thought about that as well, but I would hate to see Cakewalk lose a potential sale from someone seeing the thread and just concluding that X3 is potentially destroying projects.
 
That would be unfair to Cakewalk, and really a bit unfair to the person who might have otherwise tried out the demo and bought X3 and find bliss.  :)
 
Bob Bone
 

Sorry but I find these "you should have backed up" replies off base and bit condescending.  If this happened to me I'd be pissed off as well.  Yes we should all back up frequently.  But if the error occurred as he described, and a simple freeze then unfreeze wiped out all of his changes, this speaks to a larger problem.  It is curious that others have not been able to replicate it.  But I have seen *many* instances where Sonar has an intermittent bug that takes a while to pin down the exact steps to replicate.  Just perhaps the OP found a real, and quite significant, bug that requires attention beyond backing up his files more frequently.

bitflipper

aglewis723
I could kill right now!!!!

Please don't kill yourself.

 
Or anyone else!

Hello Everyone,

I do use the auto-save feature, just that these synths were frozen about 2 months ago;  I just unfroze them now, so all backups when the synths were not frozen are gone :(
 
Anyway, it is all different synths, some NI, Z3TA, Korg, etc....
 
Sooo pissed right now.  It shouldn't work like this.    Anyway, thanks for all your support.
 
I wont kill myself Bitflipper :)
 
-Adam

aglewis723
Hello Everyone,

I do use the auto-save feature, just that these synths were frozen about 2 months ago;  I just unfroze them now, so all backups when the synths were not frozen are gone :(
 

 
So let me make sure I understand,
 you unfroze synths that was froze a while back and when you unfroze them, all old settings were gone?
 
If I understand your situation correctly, and the way I have seen/experienced things, this ain't suppose to happen.
 
So have you tried to open the old project? Have you tried Undo? Or have you just moved on?
 

I have noticed sometimes effects will lose their settings - but this was on some earlier versions of SONAR.  With earlier versions of X sometimes SONAR would freeze up or not open the last file I worked on.  I think that was some kind of interference from my interface.  A couple of songs I had to open the old version of the song.
 
The real trick is, of course, to save patches and effects settings as individual files, and save often, and then back up.  I can tell I don't do it enough.
 
Also, whether it is PC or Mac, computers belch.  Nature of the beast.  I know it doesn't help now, but stuff happens.  I'm actually surprised that it doesn't more often, or our complete virtual world doesn't just stop working someday.  When something doesn't work that should and there seems to be no reason it shouldn't, it calls into question this whole digital pyramid we balance on top of.
 
@

Do save frequently, do back up...Do save the preset you've spend a long time building...yes yes, but...'
But if we are expected to  make a backup copy and/or "save as" under different name before every freeze or similar function, it can get a little ridicilous IMO. There has also been so many threads about the uncomfortable sides of autosave, ( many of the veterans have said they don't wanna use it) that teacherlike stiff index fingers are not needed considering that either.
I don't find it unreasonable to expect some reliability of the software. I would be angry as well, and even if I'd be more careful next time, I'd find it a little unreasonable to be treated as if I had done something wrong. We all learn our lessons about not trusting the software, but the frustration is just and....frustrating, nevertheless.
 
Many comments above offer plain "saving" as the solution, allthough lack of saving is not the problem here, but that he had not saved under different name prior to freezing, or that he had not saved the preset.
 
In this particular case, I'm curious whether freezing the synth or the track makes any difference?? Also OP doesn't tell if the synth is in the synth rack or in the FX bin. It would also good to know what softsynth it is. There are dozens and dozens of VSTs that are known to have all kinds of imperfections. Blaming Cakewalk without giving closer info is, after all, a little hasty.

These were softsynths in the rack.  I am on Sonar X3e, everything is up to date.
 
I dont have a copy from 2 months ago before I froze the synths.   All diff synths from different manufacturers are effected.   

aglewis723
These were softsynths in the rack.  I am on Sonar X3e, everything is up to date.
 
I dont have a copy from 2 months ago before I froze the synths.   All diff synths from different manufacturers are effected.   

Sorry man! But I guess you already have come to the conclusion.
 
Again, sorry to hear it.

I do a lot of synth work and freezing in my projects. Here's what I do know:
 
1 Certain Native Instruments synths like Kontakt will not always retaine their presets after freezing. This applies to Guitar Rig also.
 
2. Some synths (KORG Legacy) can screw you if you select a preset and audition it from the browser before actually committing to that preset. Unfreezing will lose that preset.
 
As for X3e, I have had zero problems freezing synths knowing that two of those above mentioned soft synths will lose their data. Sorry this happened to you, it sucks to lose work with what you do in sound design.