Welp...got new drive installed and doubled my memory.  And got Omni/Trilian and Keyscape installed on the new SSD drive...BUT...so far Keyscape is totally unusable.  It takes forver...and I mean forever...to get a patch to load up and then, if I try and select another patch, Keyscape just shuts down altogether and goes silent.  Perhaps it's the new drive...but then Omnishpere and Trilian are working fast and smooth and better than ever.  Is any one else having troubles with Keyscape??
 

Even using the machine Jim R. built for me with multiple internal ssd sample drives Keyscape is one Slow loading mofo. It is even worse if you load a 'Duo' patch.
 
It performs fine if it is the only vsti in the project but as you start adding other plugs the latency becomes unusable for me running an RME FF @128 samples.
 
It sounds great but is a resource hog to the point of killing its usefulness for me. I hope they get this resolved somehow as I'm currently stuck with about a grand and two days of work to get this on the laptop and the desk. Not a real happy camper here with the entire experience including the elusive launch/release...
 
If I was using the machine to synthesize the sounds I could understand but I am just using the standard patches to play their sound sources. (samples) I don't understand why it would slam a new, fast, multicore machine just to play processed samples...  Perhaps I had set my expectations too high.
 
I have not experienced it shutting down while trying to load a new patch.

Now if only I could buy it from BS and not have to deal with Long & McQuade's awful prices on everything. :(

yorolpal
Welp...got new drive installed and doubled my memory.  And got Omni/Trilian and Keyscape installed on the new SSD drive...BUT...so far Keyscape is totally unusable.  It takes forver...and I mean forever...to get a patch to load up and then, if I try and select another patch, Keyscape just shuts down altogether and goes silent.  Perhaps it's the new drive...but then Omnishpere and Trilian are working fast and smooth and better than ever.  Is any one else having troubles with Keyscape??
 

I'm not seeing that. Slow loads, yes, but I can switch patches in the middle of loading without problems.  I haven't had Keyscape crash at all. Nor have I had Omni crash loading Keyscape patches.  I have had issues with certain Omni 2 patches causing "crackling", but loading a separate instance with that particular patch usually solves it.  Spectrasonics recently released an update for Omni 2 that seems to have helped slow loading in Omni, so I would hope that eventually they will address this in Keyscape.  I, for one, am loving Keyscape, but I would be pissed too if it wasn't working for me.  
 
Regards,
Dan

Have got a support email in to Spectrasonics. Hope there is a sensible workaround. This is totally unacceptable. My DAW was also built by Jim and is still a great machine. With the new addition of memory and the SSD drive should be running Keyscape fine. As I said, Omni and Trilian are running better than ever on the new drive...but Keyscape, for all its great sounds, is a complete no go.

I hope they get back to you with a work around or a solution. Would seriously like to hear what they have to say.
 
Dan mentioned something, above, about loading Keyscape patches/sounds in Omni2 and I have not tried that yet. I will give that a try tomorrow and see if I experience any difference from using the Omni2 vsti with the Keyscape sounds/patches vs. the Keyscape vsti. A long shot is better than no shot...

yorolpal
Have got a support email in to Spectrasonics. Hope there is a sensible workaround. This is totally unacceptable. My DAW was also built by Jim and is still a great machine. With the new addition of memory and the SSD drive should be running Keyscape fine. As I said, Omni and Trilian are running better than ever on the new drive...but Keyscape, for all its great sounds, is a complete no go.

I will say that you have changed a lot on your machine all at once. You might see if removing the new RAM makes a difference. 
 
Regards,
Dan

They've requested some further info about my setup and the install, which I'll forward to them today. But based on the details I've already sent they say Keyscape should be rockin on my DAW. I'm sure we'll find out where the problem is and fix it. I hope.

I'm going to do some further sleuthing this weekend.

Feeling for you 'olpal. Sure hope this gets solved by the time I getz my 'Cape 
 
Edith: 
Anyone compared the C7 to the Cinematic Studio Series piano?
http://www.cinematicstudioseries.com/piano.html

Here are some specifics on how Keyscape performs on my system.
 
I have an i7-3770 with 16GB RAM. C: is an Samsung 850, but I had to load the STEAM folder on D:, which is a 2TB 7200RPM Toshiba drive. (Spectrasonics recommends putting it on an SSD.) In Keyscape, I have Mode=Streamed (the default) and Pre-Load Memory Size=50,000 samples, which is about 1/3 from the bottom of the range (also the default). I've left Stream Brake (which "balances system resources between streaming and other operations") at the default 0.16 secs.
 
The first Yamaha C7 model takes 44-56 secs to load. With Thinning turned on, that's 17-40 secs.
The first Rhodes takes 41 model secs to load. With Thinning on, that's 28 secs.
 
Notes:
In each case during loading, the progress bar changes from "Please Wait" to "Preview Ready" in 1-3 seconds. I can start playing at that point.
CPU usage is low -- lower than most of my soft synths.