kb420
 
 
I agree.  Often,  on this forum,  many members take a "it's not Sonar, it must be the user" stance.  It creates a very combative environment where there really needn't be.

Maybe that's because the people who are trying to help the person in question are doing the very same thing with the very same software and not having the same problem ? Like it or not, that does tend to point to there being something different about the set-up / methods of the person having the problem. Not always, but in cases where the OP gives very little info about a peculiar problem, there is not much else to go on other than trying to recreate the problem. If you can't, stating that "I have just tried it and it works fine here" isn't combative, it's stating a fact which may help the person with the problem get to the cause of the problem quicker. I asked the OP if it affected his back up copy because I want to find out for my own purposes if that's what happens as I freeze synths and make back-ups all the time assuming that if the worst happens, my back up copies will be fine. 
 
It could be argued that chiming in on a post and having a go at the people trying to help without actually offering any insight or help yourself is in fact more likely to cause friction. I, of course, respect your right to that ! ;)
 
 

I didn't mean to cause any friction.  After 10 years of being a member of this forum,  I should have known better than to say anything.  There's nothing like a good Sonar forum beat down.  

When glitches happen and files go haywire.... it's usually the drivers not jiving right or the underlying OS windows platform screwing up.
 
Certainly Sonar can also create issues but I find that Sonar on my DAW is pretty solid.
 
In every FX and synth I own,  I am reasonably sure that there is an option to save a given patch or setting as a preset. I know this to be the case because I use it a bunch on the cakewalk EQ & reverbs as well as on Ozone and a number of other FX and VST's.... save the settings as a preset and you can instantly recall it from inside that plug in at any future time. I use them that way all the time and start 99% of the time from an existing custom preset.
 
If you're not using this function, you are missing out on a great way to work. I hate the thought of having to start every project from square one with the plugs...... saving the presets fixes that.
 
 

Developing a system of saving is really, really important.  Because, as the OP observes, things don't always work as one thinks they should.  A plug-in should save its state; so should SONAR.  Whether a bug or glitch, it doesn't always (and nice note about NI since Guitar Rig was one of the programs I did have problems with - I'd open a project and the guitar would sound wrong).
 
If you work at a studio or post house etc. that is the first thing you have to learn - even more important than the programs being used.
 
What I have been doing here at home is saving as Project>instrument>version.  So a file name might be "Walking with Mermaids guitars 2" after my guitarist does his thing over the rhythm tracks.  I try to remember to save all the effects if I've made changes.  For synths, I freeze but copy them to audio, so the synth can be unfrozen and then archived so the preset stays the same in case I need to go back and edit the midi or sound.  And I try to go back and change the track/channel/clip names to reflect the synths used and presets at the end of a session and save the whole thing.
 
I'm sure others have found a system that works and probably stick w/ it better than I do.  But the important thing is to have a system.  Maybe we should have a thread about file/naming conventions that we can share.  Craig had a thread about "how to" recently - I found it fascinating.  What we both did and didn't do.  It is one of those practical things that doesn't get enough attention until one gets caught out.
 
@ 

I didn't take anything in the thread as being a beat down.
 
I certainly meant no offense to the OP or anyone else, and I also did not discount whatever issue caused the data to get wiped out in the first place.
 
I did indicate empathy for the frustration the OP feels, and meant that.
 
All of those who posted on the idea of the backups meant that in a helpful way - no mocking or anything like that.  I think it is safe to say ALL of us have scar tissue from getting our selves scorched by failing to do our OWN backups, and it is from those collective experiences that we posted what we did.  :)
 
Bob Bone
 

It's like some foods…you can't eat them after freezing it for 2 months…they're gone!!!

aglewis723
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...

Autosave obviously has no relevance to the problem.  Why do people keep bringing it up?

brundlefly
Saving patches in progress as new presets is as important as saving projects.

Very true.  But how many of us bother to do this?  I save a patch whenever I believe I may later want to re-use it.  I don't save patches routinely though, but it would be wise to do so.

Kev999 - that was how I USED to be, until I lost a bunch of them and had to rebuild a bunch of Konakt multi-racks and redo all the assignments and midi channels and all of that.
 
Now, I simply create and save presets when I load things into projects and get the sounds dialed in.
 
It's just insulation against having to go through all of that other junk again.  :)
 
Bob Bone
 

 Im sorry you thought that freezing meant something else that it really does in Sonar. That sucks! 
Keybind the Letter 'S' on your QWERTY keyboard and use it often.
 
I press the hell out of my 'S', that I have had to replace QWERTY keyboards yearly in my DAW
 
CJ