Pro Tools Users - www.ProToolsUsers.Org - Home of the Pro Tools Community

Anybody else getting this error in Strike? Something like "Unable to load, not enough physical memory. Choose smaller size" I forget exactly how it goes but thats the jist of it. BASICALLY it loads the kit you selected but it doesnt load a random sound, somtimes snare, kick, ride ect... And you go in change the size to Medium or Eco and usually it will load. I dont understand why this happens though, cause sometimes you can use it flawlessly. There have been times I have had multiple other plugins loaded and Strike works fine and other times Strike is the only plugin loaded and I get the error message. I dont see how I could not have enough physical memory, I have 4GB, of course only 3.24 shows up in Windows XP Pro 32 bit.
I have even tryed changing the options in Windows from Programs to System cash as it says to try in the Pro Tools Book. Should i change Processer Schudueling to programs insted of Background Services, even though it says to use Background services in the book.

I am Running Pro Tools 7.4 LE
003 Rack
Windows XP Professional
3 Hard drives
C: 10,000rpm Raptor 75GB internal 44% free. Strike is on this drive, i use to keep the sounds on my External, but it took longer to load kits.
D: Recording drive 7200rpm 250GB internal 97% free
J: WD Mybook 7200rpm 500GB External firewire 85% free.I keep most of my samples and sound libraries here.
4GB Ram only 3.24 shows
Pentium D(dual core) 3.0

My Virtual Ram is set to what windows recommends 4GB i have that set as Minimum and Maximum

Here are all the Digi recommended tweaks to windows XP

I'm not positive, but your virtual memory settings seem a little suspect

Ive change everything, even virtual memory. I still get the error, not every time, just sometimes. Its not real important, because all you have to do is change the size on the content and you aree good, its not like its freezing and cant be used.

Its strange, sometimes I get the error, and I actually have to INCREASE the size of the sample for it to load, so i know its not a problem of not enough Ram.

Hi,
In July and August when I was using my Win XP Pro based ProTools LE 7.4.2 system at home
a bit with Strike I would get this problem from time to time. My experience was that it would have this problem after I:
a) either auditioned by loading 4 or more drum kits or main presets.
b) when I had really heavy sessions with lots of plug-ins.

About 80% of the time, if I rebooted and use the Medium sample size in Strike and didn't fully audition more than 1 or 2 patterns per session, the problem didn't manafest itself.
I conjected that there was some sort of memory leak associated with STRIKE and emailed
a bug report that I saw it both on my Win-XP home system, as well as on a 7.4 Mac LE 002 system that I also work on.

Never heard any response or seen notice of a new Strike patch.

-Jay-