EWQL Spaces in X2

I do love the sound Spaces gives my tracks, but it also often crashes X2 Producer to the point of having to do some pretty creative computer trickery to fully recover project files. It's getting too scary to use unless I have a pretty low track count. Anyone else with similar experiences?
 
I'm running an i7 quad-core Rain system with 32GB RAM, so I don't think computer specs is the issue here. 

Bajan Blue


I run East west play and many libraries 64 bit on an i7 with no issues at all - however I have never used Spaces specifically - sorry - also I should say I have moved back to X1 at the moment as initially I had quite a few strange bugs (not unlike this) and have not had the time to try since the first patch for X2 released.
I take it you have the lastest versions of all the software?
Nigel

Thanks for your input, Nigel. I'm fairly diligent about keeping current with my software so, yes, it's all up to date. I run a pretty large number of EW libraries also, with no problems at all (I don't seem to have the issues with Play that many apparently do, thankfully). It's just the Spaces plug-in that fairly often wreaks havoc.
 
Danny

FWIW I've been running QL Spaces on X2 with no problems (W7x64, Q6600, 8GB).

wienryk
I just got the Spaces with Composer Clouds. Unfortunately I can't find it in my plugins. There is some particular way I should install it? I can't use it as regular plug in.

If you didn't install it to your Cakewalk/Vstplugins path then chances are it installed the VST in 
the Program Files\Steinberg\Vstplugins folder...and you just need to add that to the "scan" list
in Cakewalk.

Just search your drive for where it was installed and add that path to the "scan" criteria under
Plugin Manager and it should show up...

BTW ...it shows up as "QL Spaces", not just "Spaces" when it's installed

Works fine for me on Sonar Platinum...

If you downloaded from the CC, and you had an older version installed you will need to make
sure that you have uninstalled any previous version of Spaces completely.  The version with the CC is 1.1.23 and
the IR's in that version are encoded specifically for THAT version.  

Are you saying "it won't load at all" or that, when it loads, you can't load IR's and it tells
you you need a license?  This is the issue I had and had to completely uninstall and
then reinstall and it worked fine...just an FYI...

Launch the "Standalone" and look at the Version # under "Main Menu" and then "About"...
it HAS to 1.1.23.  If it's anything else you won't be able to load the IR's.

wienryk
I have the latest version 1.1.23. However in my system QL Spaces is installed as an application not as a plugin.
 

The Application is a "Stand Alone" version, why this exists I have no idea...
and is completely separate from the VST and AAX versions...those will show
up in the Browser if you select "effects" and then type "QL Spaces" in the search
window...if it doesn't show up then you might not have installed the VST's by 
accident and I'd recommend and uninstall and reinstall..

Glad to try to help.  Hope you get it resolved...

g_randybrown
FWIW I too had the standalone load IR's no problem but Sonar not allowing the IR's.
 
The default installation goes to "common files" so scanned that folder but still no joy.
I uninstalled (and deleted the references the uninstall missed) and reinstalled to the CW VST folder and everything is hunkey dorey.

This is the same problem I had.  

The problem stems from having 1.1.22 installed prior to downloading the new version
from the Cloud.  It leaves the 1.1.22 Vst's, which will not load the 1.1.23 IR's, which are encoded 
specifically to the 1.1.23 VST's.  So if you have installed from the cloud, open your VST and check
the version # from the "About" menu.  If it says 1.1.22, it will NOT load the IR's and tell you you
need a license. You will need to completely uninstall, and then reinstall.   If it says 1.1.23 then it
WILL load and all will be fine....just an FYI for those who use the Cloud and Spaces...

I've been using Spaces as my primary verb since it first came out, several years ago... it has worked flawlessly thru all versions of Sonar and I've had every update since Sonar 6.