paulo

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 :(
 

I don't share the love for autosave as I like to choose when saves are made and wouldn't want it to kick in when I had just messed something up. It also gives me the opportunity to just close a project without saving if I have screwed something up and revert back to how it was. That aside, I'm not quite following you here......are you saying that because you did an unfreeze on a synth in a project that it also affected your back up .cwp file of the same project ?
 
Once you realised something was wrong, I'm assuming that you tried the undo function or backing out of the project without saving ?

Have you tried out the "versioning" feature in Sonar.  This along with autosave is great, it means you can revert to previous versions without needing to save to a new file name manually every time.

robert_e_bone
@Sharke - With regard to the notion of NI software and volumes having a mind of their own and all that - I JUST had that happen in the current project I am working on - AND I finally figured it out.
 
What was happening was that for Battery 3, its master volume kept jumping back to some lower value than what I would set it to, as soon as I would hit play.  Drove me NUTS.
 
It turns out that it is tied to the MIDI track volume fader.  If I move the fader up or down while the Battery 3 UI is open, I can watch the master volume for Batter 3 rotate higher and lower.
 
This behavior does NOT go the other way around - in that if instead of moving the channel strip slider up or down to adjust volume, I rather go to the Battery 3 UI and rotate the master volume up or down, Sonar's midi track channel strip slider does NOT move with it.  The movement of the Battery 3 master volume ONLY occurs by itself when the channel strip slider is moved.
 
THIS is why the Battery 3 Master Volume appears to JUMP.  Because it is tied to the midi track channel strip slider, but does not move that slider when the master volume knob is rotated in Battery 3, as soon as Play is commenced, the Battery 3 UI Master Volume knob 'jumps' back to mirror the setting from the channel strip slider at the time Play was started.
 
Additionally, the Battery 3 UI Master Volume knob is operating at a different scale level than that of the channel strip slider.  The midi track channel strip slider represents midi parameter values of 0-127, and the Battery 3 master volume knob represents volumes between about -128 DB and about +12 DB.
 
SO, I have not figured out if this can be disconnected, or if that DOES get figured out, will the volume then behave as it should, but at least I now KNOW what is happening.
 
Bob Bone
 

That's very interesting Bob, and makes me wonder if anything MIDI related could be behind the problems I've had with NI plugin settings resetting themselves on playback. I always wondered if some kind of MIDI event on playback was making them do it. I just tried this with Battery 4 though (I don't have Battery 3 installed anymore) and I can't reproduce it. I take it you could just insert Battery 3 along with an audio/MIDI track pair, move the MIDI fader and the master volume in Battery moves with it?  

@Sharke - I hadn't seen that behavior with any other parameter within Battery 3.  Further, with the midi track channel strip's slider moved all the way up to a value of 127, the Battery 3 Master Volume knob still only goes to a maximum of -6 DB.  I would rather be able to set the gain higher in Battery 3 than have it lower there and have to turn up the gain in the channel strip.
 
Bob Bone
 

jb101

yevster

Cactus Music
What I see here is a simple case of using a flawed method of saving your work. If anything Calkwalk is at fault for offering the auto save function which 90% of us know is not reliable and we use "save as" instead. Sorry you trusted the auto save. 

I'm curious what beef you have with Autosave. Autosave is one of the few features in Sonar that has worked incredibly well for as long as I can remember. Try coming back from StudioOne, where autosave interval can be specified only in minutes, not changes, and autosave is modal and will lock out your controls while it happens, even during playback, Sonar's autosave may be the first feature one could really fall in love with.

+1 here.  Auto Save works flawlessly here.  Very grateful that it is there.
 
Always have it set up here, along with version-ing.

Same with me.  Auto save has helped me out a few times that was worth the price of admission.  I do save often and have offline backups as well, but a few BSOD in the XP days showed me that the auto save saved my bacon. 

Silicon Audio

paulo

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 :(
 

I don't share the love for autosave as I like to choose when saves are made and wouldn't want it to kick in when I had just messed something up. It also gives me the opportunity to just close a project without saving if I have screwed something up and revert back to how it was. That aside, I'm not quite following you here......are you saying that because you did an unfreeze on a synth in a project that it also affected your back up .cwp file of the same project ?
 
Once you realised something was wrong, I'm assuming that you tried the undo function or backing out of the project without saving ?

Have you tried out the "versioning" feature in Sonar.  This along with autosave is great, it means you can revert to previous versions without needing to save to a new file name manually every time.

I don't save to a new file name, I just save what I definitely want to save as I go along and if I screw anything up I close the project without saving, which is much the same thing as versioning as I see it. If I know I'm doing something that is a bit of a risk to the current state of the project, like sometimes when it's just not working for me and I reset the faders etc and start again from scratch, I "save as" before I start and reset the mix in that version, so the main project is still intact and the newer one becomes "alternate" mix until such time as I have convinced myself that it is better than the original, at which point it will replace it. Sometimes I can't decide and keep both. I back all this up to other drives, so I'm reasonably well covered and haven't lost anything more than a few minutes work since I got into this habit years ago. I'm reluctant to change routines now as the habit is just ingrained now and it seems to work well for me. On a per project level, none of it really matters anyway, it's just me messing around for my own interests.
 
I'm still interested to to know if/how the unfreezing affected the OP's back up copy though as I have always assumed that my back-ups were immune to any changes made in another copy of the project.

I think we all feel for the OP. I don't think I would be surprised if I were to unfreeze a track that no longer had the same version plugs loaded and it messed up. Other than that, I would think it should always work. But I'm learning here that may not always be true... Hopefully the OP didn't save over top of the busted project and still has his original version.
 
With that said, Ctrl S is a key sequence I've used for years regardless of the software I'm using. I learned that the hard way. I want to also mention that once I realize I'm deviating from the original project idea in a session, then I do a "Save As" for versioning. After then it's back to to the trusty Ctrl S and do that numerous times during the session.

musicroom
...Ctrl S is a key sequence I've used for years regardless of the software I'm using...

My left hand is habitually poised for this key combination.

My left hand is habitually poised for this and Ctrl-z (especially while recording).

It's handy that these three keys (Ctrl, S & Z) are all close together on the keyboard.
 

I'm one of those people with a V-Studio, and there's a dedicated Save button. I cut a red adhesive label to size and affixed it to the top of the button not just so I could hit it without thinking, but so that it would always scream at me "save me, dude!"
 
Also I'm not quite sure why, but it always seems that the projects where I save regularly don't crash. I wonder if saving does some kind of system flush or something that reduces the chance of glitches.