Hey guys,
 
I put a post up on EWQL which is still awaiting approval from a moderator, so isn't visibal on their forum yet.
 
My problem is that when I use the Play engine for my EWQL instruments, the time it takes to save a project increases to a crazy amount.
I created an orchestral template that uses 12 instances of Play. When using this template it takes over 9 minutes to save my progress.
I have got into the habit of pressing (alt+f+s) quite often to save my progress as i go, which is fine usualy, but doing it with Play and then having to take an almost 10 minute break each time to allow it to save is getting frustrating.
 
I even inserted 1 instance of Play into a blank project and loaded 1 articulation of a violin and when i hit save, it took 12 seconds to save.
My large projects with many other VST's, plugins and effects only takes 2 or 3 seconds to save.
 
Also loading my orchestral template into a project take almost 5 minutes. 
 
Is anyone else having this problem?
 
Im using Sonar X1 producer expanded
 
My system is:
Win 7 pro 64bit
Intel Quad Core i7 950 @3.07GHz
12GB RAM
 
The EWQL samples are installed on the original HDD that shipped with Complete Composer's Collection
 
Running a project with this template is no problem to my system, the CPU metre seems to be hitting around the 40 percent mark.
 
Thanks for any help guys,
 
Glen

I use EWQL projects alot and yes, they do seem to cause slow save times. The load times are to be expected as Play does not have a background load option and if you are loading a template then you should expect it to take a while depending on how big it is. I have not seen it take 9 minutes to save but the more instances of play I add the longer it does take to save on my DAW. I find that adding Kontakt also causes my projects to save or load slower so I don't think it is just play that affects load/save times but play does seem to be the biggest offender. For me, I try to plan ahead by either leaving projects open that I plan on coming back to shortly or loading a project a few minutes before I am actually ready to begin working. The big one is the save times as all of us have had that masterpiece get lost because we forgot to save and lost power or had a crash before closing.

You should be able to improve things by adding SSD's and streaming the samples from them, adding mega amounts of ram and loading everything into ram or using something like VEPRO to run your template from but these take a more $$$. I would love a more simple solution though.