PlanetZ forums - scopeusers.com

Got my new XITE-1. When trying to load any sample or library into any instance of the STS (3000, 4000 or 5000) it says

low memory error

Even when i try to create a new one ??????!!!!!

Running Windows XP SP3 @ ASUS P7P55D-E, 4 G RAM, 150 G WD Raptor, Intel Core i5 @ 2.6

In my old PC (also Win XP SP3 but other board and CPU) using the LUNA + Pulsar SRB (9 DSP) configuration, the STS 5000 worked perfectly.

Is there any trick? All forum posts regarding that problem didn't help.

There is definetely enough memory free. damn

THX

You may have to assign the STS to a lower-numbered DSP, such as #6 (or something).

I doubt the STS's are optimized for the Xite DSP cascade.

Greg

cascade,

I've seen this as well. I can usually restore it by closing out scope (and my DAW first if it's already started), and re-starting scope. I have to do this most of the time, but once it's up, it's solid. Sometimes I need to shut down the entire system and power-cycle the XITE, but that is very rare.

I have experimented with assigning the STS to one of the first six DSPs, but haven't seen much benefit from it, but it's worth a try on your system to see if it helps.

Cheers,
Cory

Hi @all

None of the suggestion helped. When trying to assign DSP 1 - 6 (one of them) to the STS, i get a error message asking if i want to optimize whatever (do not have exact notation available). When i use DSP 7 - 18 it works (from the assignment point of view) but still get lowmemory error. Even restarting machine or XITE does not help.

Damn :-/

are you using the latest release of Scope?

ftp://sonic-core.net/software/scope5/SO ... 617_EN.exe

Sure !!

Installation was on 26th of December using actual Version of Scope.

Find a screenshot of the STS 5000 message when trying to create a new sample.

HI There,
I am getting the same thing on my XITE with all of the STS samplers.
reassigning DSP does not seem to help
I have 3.5 GB of RAM (I assume its RAM its reporting on) and in STS 5000 it reports 2Gb available with 0 used.
When I first tried the samplers they worked fine, but as soon as I went to use them in a project - LOW MEMORY and they have'nt worked since.
I might try the reboot trick mentioned here and see what that does.
any other thoughts?
maus

I just tried closing SCOPE and then restarting and it works.
It looks like there must be some residual memory allocations that don't get cleared or something
maus

try to remove scope from auto- startup and load scope manually after reboot windows, be shure that scope is running "as administrator"