|
Author
|
Unable to save, Out of memory? SX3
|
A.Rosengren
Solid Snake
Started Topics :
266
Posts :
4139
Posted : Dec 24, 2008 14:53:24
|
Hello dear isratrancers, first of all merry x-mas and happy hanukkah!
As for the topic:
Im on a copy paste from EVEREST:
Type:
ACPI Multiprocessor PC
Operativsystem:
Microsoft Windows XP Professional
OS Servicepack Service Pack 2
Internet Explorer
6.0.2900.2180 (IE 6.0 SP2)
DirectX 4.09.00.0904 (DirectX 9.0c)
Motherboard:
CPU typ DualCore AMD Athlon 64 X2, 2600 MHz (13 x 200) 5000+
Motherboardname:
Gigabyte GA-M52L-S3 (4 PCI, 2 PCI-E x1, 1 PCI-E x16, 4 DDR2 DIMM, Audio, LAN)
Motherboardchipset:
nVIDIA nForce 6100-4xx, AMD Hammer
Systemmemory:
3584 MB (DDR2-800 DDR2 SDRAM)
DIMM1: Samsung M3 78T2953EZ3-CF7 1 GB DDR2-800 DDR2 SDRAM (6-6-6-18 @ 400 MHz) (5-5-5-15 @ 333 MHz) (4-4-4-12 @ 266 MHz)
DIMM2: Samsung M3 78T2953EZ3-CF7 1 GB DDR2-800 DDR2 SDRAM (6-6-6-18 @ 400 MHz) (5-5-5-15 @ 333 MHz) (4-4-4-12 @ 266 MHz)
DIMM3: Samsung M3 78T2953EZ3-CF7 1 GB DDR2-800 DDR2 SDRAM (6-6-6-18 @ 400 MHz) (5-5-5-15 @ 333 MHz) (4-4-4-12 @ 266 MHz)
DIMM4: Samsung M3 78T2953EZ3-CF7 1 GB DDR2-800 DDR2 SDRAM (6-6-6-18 @ 400 MHz) (5-5-5-15 @ 333 MHz) (4-4-4-12 @ 266 MHz)
Graphiccard:
GeForce 8400 GS (512 MB)
NVIDIA GeForce 8400 GS (512 MB)
3D accelerator nVIDIA GeForce 8400 GS
Multimedia
Ljudkort IC Ensemble Delta-44
Storage:
IDE controller NVIDIA MCP61 Serial ATA Controller
IDE controller Standard-Dual Channel PCI
Harddrive:
SAMSUNG HD501LJ (500 GB, 7200 RPM, SATA-II)
Harddrive:
WDC WD3200AAKS-00SBA0 (298 GB, IDE)
SMART hardrive status: OK
Partitions
C: (NTFS) 298.1 GB (87.7 GB free)
E: (NTFS) 465.8 GB (200.1 GB free)
Total size 763.8 GB (287.8 GB free)
In software i am running:
Cubase SX3, Avira Antivirus, Comodo Firewall.
When i try to save my project in cubase i get a popup saying i am out of memory, and when i ctrl+alt+del and check the systemperformance i see that im using about 50% of my CPU, not even close to 4gb of ram (around 1.7gb of ram used)
Am i missing something, can i change the priority of memoryusage in sx3´s favour?
Any help is much appreciated.
A
|
|
|
0hz
IsraTrance Junior Member
Started Topics :
10
Posts :
261
Posted : Dec 25, 2008 12:43
|
on 32bit system one process can use up to 2gb of memory.
cubase can use only 1.5gb of memory because it reserves 500mb for exports. usually most people will see that cubase starts to run out of memory after it hits the 1.2gb mem usage. all the /3gb ,/pea switches in most cases make the problem only worse since it makes less pte's available.
anyway check how much cubase process uses memory and if its in the range of 1.5gb then in most cases there is nothing u can do, other then export tracks and free up some memory.
also if you dont have page file, then create one, or better yet 2 on different drives.
|
|
|
naga
IsraTrance Junior Member
Started Topics :
40
Posts :
204
Posted : Dec 25, 2008 13:29
|
time to turn on vista and it's 4gb memory support. your xp extension declined
but actually i've same kind of problem using native instruments.. i overclocked my cpu from 2,2 -> 3,3ghz but guitar rig and absynth 4 cannot fucking get it.. i'm less than 5% cpu usageand these two retards inform cpu to be overloaded!
happy fucking christmas NI team
  "" |
|
|
A.Rosengren
Solid Snake
Started Topics :
266
Posts :
4139
Posted : Dec 25, 2008 15:49
|
Quote:
|
On 2008-12-25 12:43, 0hz wrote:
on 32bit system one process can use up to 2gb of memory.
cubase can use only 1.5gb of memory because it reserves 500mb for exports. usually most people will see that cubase starts to run out of memory after it hits the 1.2gb mem usage. all the /3gb ,/pea switches in most cases make the problem only worse since it makes less pte's available.
anyway check how much cubase process uses memory and if its in the range of 1.5gb then in most cases there is nothing u can do, other then export tracks and free up some memory.
also if you dont have page file, then create one, or better yet 2 on different drives.
|
|
Wow thats pretty bad, yep cubase uses around 1.5gb and problem is found. But impossible to solve?
Except for bouncing? I dont realy like to lock myself like that, i want to be able to change stuff for diversity.
And while talking about it, what uses the most memory, vst plugs, vsti´s? Romplers, synths. What munches my ram?
:(
A
|
|
|
Tryptagon
Started Topics :
0
Posts :
95
Posted : Dec 25, 2008 18:47
|
I've had problems like that in cubase and ableton,definately sucks,in the end i had to bounce them down.
Nothing worked even took the project to my m8 with better ram ,same problem |
|
|
A.Rosengren
Solid Snake
Started Topics :
266
Posts :
4139
Posted : Dec 25, 2008 22:03
|
Well i found a solution, its pretty boring and time consuming but i noticed that some of the tracks had a high "hissing" sound and i was pretty sure a complete system failure was near. I have a sixth sense for those things haha.
Anyways the crash came, and it pretty much fucked the whole track up, which is sad because ive been working on the freaking sketch for weeks. So i decided to try and move the most important elements into a new project folder & cpr file.
Voila, instead of using 1.1gb of ram, i use 600mb of ram and the elements i chose to remove was not necessary for the tracks "soul", just makeup and hairgel ^^
Allthou i do have to add similar elements, i can now work free without having to check the RAM before another virtual runtime error comes to haunt my project.
Peace
A
|
|
|
0hz
IsraTrance Junior Member
Started Topics :
10
Posts :
261
Posted : Dec 26, 2008 12:51
|
Quote:
|
On 2008-12-25 15:49, A.Rosengren wrote:
And while talking about it, what uses the most memory, vst plugs, vsti´s? Romplers, synths. What munches my ram?
A
|
|
samplers use alot of memory, and all kinds of sample based synths.but any plugin uses memory, some use less some use more. also tracks use memory, every track you create in cubase, it takes up some memory.
the freeze function is very useful in cubase, since you can select the option "unload instrument and effects after freeze"
when you unfreeze the track, cubase loads all the parameters and plugins as they where.
vista 32bit wont help your problem much since its a 32bit environment, and vista32 by it self uses more memory then XP.
if you want your memory problem to go away the only way to go is 64bit system. but then you will have issues with plugin compatibility, some plugins wont install on 64bit systems because they are not made for 64bit systems. |
|
|
|
|