Hi all -
 
I wonder if anyone has thoughts on a problem I just experienced. I have a project that has been loading fine for 2 weeks and yesterday it decided to load extremely slowly (after an hour it had not finished). It appeared to be hanging or loading EW Play VERY slowly. I've had larger, similar projects and have never encountered this before. I rebooted and had the same issue. I finally loaded the project in Safe Mode and loaded every VST. The project loaded fine. I saved a copy of the project from safe mode and it loads every time.
 
The only difference I see is that the console view was open and minimized in the version with the bad behavior. I am running Pro and have not yet upgraded to Foxboro. I guess I'm OK since the project saved from safe mode seems fine, but I hate not knowing why something went "BOOM!" in case I can prevent it from happening again. Maybe the project file just got corrupted.
 
Has anyone had a similar problem? Any thoughts?
 
Thanks,
 
Dave

Hi. What happens if you take the EW Play out of the equation? Is the issue still there?
Best of luck.

Thanks Ken. I can't test because I had to load it in Safemode. The Safemode save has all of the Play instances active (about 20) and loads fine so there's no reason to disable anything. I have other projects with the same number of Play instances that load without issue. The one thing that IS new in this project is Alloy 2, but again it loads fine in the Safemode save.
 
One more bit of info, the Safemode project file has all of the same VSTs loaded but is is about 300 MB smaller in size than the one that won't load.

Just to close the loop on this - I haven't "solved" the bad file, but the save made while in safe mode is working perfectly. I can only surmise that the file got corrupted in some manner. Could have been almost anything. If it happens again, I'll try to find commonalities.
 
One more reminder for me to backup regularly.

The cwp was 300MB smaller? If so, that is a massive cwp... Were there active region FX saved with that file?

cwp bloat could be due excessive audio snap data. One repair for this condition is running the project through the bundling process.

Oops. My apologies! Um, 300 KILObytes, not MEGAbytes. How embarrassing!
 
Bugs Bunny would say this to me: https://www.youtube.com/watch?v=hxGgnI6kCrs 
 
 

I have a similar situation in which long-stable projects start failing to load and I am forced to load them in safe mode with no plugins before they will work again.  At this point, I am forced to remix which isn't great.
 
I think that there is a plugin I am using that is compatible for the most part and then one day it corrupts my project.  Perhaps you are having a similar issue?  Lately I have found the VST3 versions of my plugins to be completely unstable and have had to carefully reinstall all VST 2.4 versions.  Are you running VST3 plugins?
 

Scott -
 
Thanks for the info. I don't think it's a VST in my case and in this project there were no VST3 plugs. I use almost the same template for most pieces. The only new VST that I had not used before was an instance of Alloy 2. I never even had to delete the VSTs - I loaded every one the first time in safe mode. I haven't had a problem since I loaded in safe mode. I tend to think it had nothing to do with Sonar and was just a messed up file. If it happens again, I'll be concerned.