I am running into a virtual memory wall with windows XP 64 bit. This isn't a Usine specific problem but I am running Usine VST in Live 7 32 bit in a 64 bit OS with 8GB of physical ram.
The problem Is that the project I am building, despite only using about 2GB of physical ram has maxed out the 32 bit 4GB virtual memory address limit (not to be confused with pagefile).
I am wondering if there is any technique for forcing an application to use more physical ram before virtual memory is utilized as I should in theory be fine using up to about 3.7GB of physical memory per 32 bit large address aware application?
Worst case I rewire Bidule with an instance of Usine into Live but I would rather not have to do this...
memory question for tech heads
I m quite sure you already tried but couldn't the /3gb swich help ? I had 3dsmax crashing when reaching memories limits on complex scenes that were extended in 3gb mode..that way appz get 3gb and 1gb for sytem, rather than 2-2. but if i well remember it's seems not possible to give more than 3gb to apps in 32 bit.
I don't think the 3GB switch is applicable in a 64 bit OS. Also, I know that Live is Able to address easily up to 3.7GB as I have done tests to check this but I am running multitudes of other vst's (including Usine) which claim large amounts of virtual memory space.
I actually had no idea this was my issue untill research I did suggested that what you see in page file useage in the xp task manager has little to do with how much actual virtual memory is being used. I then downloaded Process Explorer http://technet.microsoft.com/en-us/sysi ... 96653.aspx which can show the virtual memory size per process and it is here that I determined that Live is using just a bit under 4GB of virtual memory when I hit the wall.
I actually had no idea this was my issue untill research I did suggested that what you see in page file useage in the xp task manager has little to do with how much actual virtual memory is being used. I then downloaded Process Explorer http://technet.microsoft.com/en-us/sysi ... 96653.aspx which can show the virtual memory size per process and it is here that I determined that Live is using just a bit under 4GB of virtual memory when I hit the wall.
hehe so you 're often right to the max from what I see.. cool to know that live 32 can access nearly 4gb on 64bit os, didn't knew that..
and cool for process xplore.
and cool for process xplore.
If I can't find a way to force more memory to physical locations I suppose I could always drop some virtual memory hogging dirty synthedit plugins from the project...
I could seriously write a book on the perils, pitfalls and tribulations of pushing your system to the limits..what I am trying to accomplish has been a deep learning experience so far.
I could seriously write a book on the perils, pitfalls and tribulations of pushing your system to the limits..what I am trying to accomplish has been a deep learning experience so far.
fighting computers limits lol , may sound stupid but if you need horse power you could build a nodal with fx teleport kind software and win over memory... not the best solution, I reckon.
sadly this seems a pb i might face soon so i any master as a solution im really interested too
sadly this seems a pb i might face soon so i any master as a solution im really interested too
So far so good on the raw horsepower...quad 3.5Ghz seems to go a long ways when core load is balanced. Most of my hardware battles so far have been with figuring out the poorly documented 32bit memory limitations. I have spent a lot of time trying to figure out why I run out of memory before I should. Realizing that I have been exhausting my virtual memory allowed per 32 bit application is a huge revelation...
keep on chatting 
so you mean 32 bit apps still have 4gb virtual memorylimit on 64 bit os? do ya know how would allow a live 64?
edit: self answer 2^64 ouch that's far more than i thought. make sense that take so song to go to that....
so you mean 32 bit apps still have 4gb virtual memorylimit on 64 bit os? do ya know how would allow a live 64?edit: self answer 2^64 ouch that's far more than i thought. make sense that take so song to go to that....
tried to understand the issue and found this:
http://www.xpfree.org/os_system_ram_lim ... _guide.htm
u both already know about I guess.
http://www.xpfree.org/os_system_ram_lim ... _guide.htm
u both already know about I guess.
Yea, there's tons of reference like that on the web. Few references seem to really clarify the relationship between physical memory, virtiual memory and paging, at least in an easy to digest format.
I sure am suprised to figure out that even though a 32 bit application can use up to 4GB of physical ram for it's own needs, that entirely depends on what the virtual memory requirements of the application are. In my case, by the time I have used 2.1-2.2GB of
physical memory, I have reached the 4GB per app virtual memory limit.
After playing around with rewiring a second app into the Live project and running two concurrent instances of Live (2x4GB) I found I could not get my multicore cpu use balanced again so I dropped a couple VM hungry synthedit vst instances and reconfigured some 'inneficient' use of jsoundbus instances and Live routing and have managed to free up close to 500MB of VM for headroom..hopefully this willl hold me off untill I have all my midi mapping and 'pass if changed' modules in place...
I sure am suprised to figure out that even though a 32 bit application can use up to 4GB of physical ram for it's own needs, that entirely depends on what the virtual memory requirements of the application are. In my case, by the time I have used 2.1-2.2GB of
physical memory, I have reached the 4GB per app virtual memory limit.
After playing around with rewiring a second app into the Live project and running two concurrent instances of Live (2x4GB) I found I could not get my multicore cpu use balanced again so I dropped a couple VM hungry synthedit vst instances and reconfigured some 'inneficient' use of jsoundbus instances and Live routing and have managed to free up close to 500MB of VM for headroom..hopefully this willl hold me off untill I have all my midi mapping and 'pass if changed' modules in place...
Hmmm...still difficult with even 500MB of VM free. What I'm seeing happen is that every time I do something in Usine vst (add a fader, vu meter, cable etc.) another 5-15MB gets tagged into VM and so after X amount of operations I have to exit the host or reload the workspace to clear the VM. I wonder if this has anything to do with Usine's undo features? If so I would like to request an option to turn undo off.
Who is online
Users browsing this forum: No registered users and 21 guests