Kalle Rantaaho
If you open in safe mode, edit the project and save, what happens?
Do the original VSTs remain in the project, or is it just the opened version that is saved, or does SONAR automatically save a special "safe-version"??

That's a very good point.

If you open in safe mode, edit the project and save, what happens?
Do the original VSTs remain in the project, or is it just the opened version that is saved, or does SONAR automatically save a special "safe-version"??
 
i think that you will loose  the fx that you not load in safe-mode
 
martin
 
 

Kalle Rantaaho
If you open in safe mode, edit the project and save, what happens?
Do the original VSTs remain in the project, or is it just the opened version that is saved, or does SONAR automatically save a special "safe-version"??

Hmmm, I just tested this. I created a project with a VST loaded. I recorded some Midi and added an effect to the instrument track. Saved, closed, re-opened in "Safe Mode", saying "No to All" when it asked to load VSTs. Saved and closed Safe Mode version. Re-opened. The effect was missing, the VST was still present but not loaded. It loaded fine when I selected "Synth Connected" (AFAIK that's the only way to load a VST that is not loaded, right? I've always wanted to ask this - seems like there would be a more obvious way...)
 
So, saving in Safe Mode does indeed lose your effects. Doesn't just turn them off -- they're gone. Beware!

A work around might be to -open in safe mode -Work on your midi -export your midi tracks to the browser.
 
I always, ALWAYS back up midi when saving projects for the simple fact that if a project goes corrupt, you can always salvage the audio tracks (they are in the work folder) but the Midi is saved with the project.
If something goes array and Project Ducky wont open.. "Poof" there goes the midi !
 

jkoseattle
So, saving in Safe Mode does indeed lose your effects. Doesn't just turn them off -- they're gone. Beware!

As the documentation says...
 
To use File Recovery mode
 
Do one of the following: 

• If you are opening a file from the Most Recently Used files list in the File menu, hold down the SHIFT key while selecting file name.
• If you are opening the file from the Open dialog box, select the file in the dialog box and hold down the SHIFT key while clicking the OK button. 

 
What does File Recovery mode do?
 
File Recovery Mode applies the following behavior when opening a project file: 

• Opens only the Track view, skipping all other opened views in the project including effects windows, Console View etc.
• Prompts you to open the plug-ins saved with your project. Each plug-in gets a prompt, so you can open some and not open others.
• Important: If you choose to not open a plug-in, that plug-in is stripped out of the project, so resaving the file will cause a loss of any project specific settings for that plug-in.

Thanks!
 
So here's a feature request: If you go to save a project you opened in File Recovery Mode, Sonar should warn us of this "You opened this project in File Recovery Mode. If you save it you may lose stuff permanently. Are you sure?"

jkoseattle
Thanks!
 
So here's a feature request: If you go to save a project you opened in File Recovery Mode, Sonar should warn us of this "You opened this project in File Recovery Mode. If you save it you may lose stuff permanently. Are you sure?"

Last time I opened in "Safe Mode", it actually did give me a alert and or warning about this. So it seems that this feature is already there. Maybe you missed it (overlooked the info in the opening of "Safe Mode" process).

Interesting. It has never even occurred to me to save a project I've opened in safe mode. That's always a troubleshooting step, to see if a problem is being caused by a plugin or not. And because the next step is usually to remove plugins one-by-one, I always start by saving the project under a new name.
 
At any rate, safe mode isn't your best solution. If projects are taking a long time to load, first make sure you're not doing an automatic plugin scan - that can add an extra minute right there. More likely, it's just large sample libraries that are slowing you down.
 
I do have some large projects that take up to two minutes to load. 5-6 minutes is pretty extreme, and might indicate memory exhaustion. I say might because 8 GB will hold a bunch of medium-sized libraries and a couple monster ones. After they've completely loaded, check your memory usage. If they're Kontakt instruments, it'll show you right there in the header how many mega/gigabytes each instrument has loaded. Other samplers have other ways to show you how much RAM they're consuming, and each has its own tricks for deferring loading or minimizing memory usage.
 
If you've got one or two monster libraries (e.g. OTS Rick Bass, the reason I was compelled to give up XP and go 64-bit in the first place), consider freezing them. Then they'll pop right up, no loading required. Even if your template has no MIDI data you can still freeze the tracks to avoid loading the library on start up. Un-freezing is a one-click operation. Freeze them all and save that as your template. When you start a new project, just un-freeze the ones you want to use.
 
It works for food, too.

Curious why we say "unfreeze" instead of "thaw". You don't unfreeze frozen food, you thaw it.

Just create a copy of the project before you open it in safe mode if you're going to save that file.