Solve : Windows 7 Memory Again?

1.	Solve : Windows 7 Memory Again?
Answer» So I posted a few weeks ago about Windows 7 using up all my memory eventually. Well I ran into a huge problem. My music software is 32bit and can only use the FIRST 4GB of my memory. I could swap to a 64bit program but I don't know if that would solve the problem as most of my VST instruments are 32bit as well. Once I get to 51% usage, Cubase stops loading everything dead in its tracks. I had to do away with RAIDXpert because I honestly can't use my music software anymore if it's eating up all the RAM but now Windows still is using 1.46GB of memory with Firefox open and nothing else with the exception of the background programs. I've turned off the Aero theme and switched to classic hoping that would reduce memory usage as well. Are there any other things I can do to reduce the used memory? My VST instruments require a lot of RAM to work and I mainly use the computer for producing my music. Maybe I'm asking for too much for the usage to be reduced further? I'm desperate and willing to deal with system SLOW down or minor instability or anything of that nature to be able to have access to more memory in Cubase, if need be.Why don't you try using another operating system other than Win 7 for your music software?I don't have the money to buy a different operating system, this one came with the computer and the computer has 8GB of RAM so downgrading to a 32bit OS is also probably a no go for me.a 32-bit program isn't LIMITED to the first 4GB of memory. all 32-bit processes have a 4GB address space, 2GB for the program itself, and 2GB for kernel space. This is address space not necessarily physical RAM. That is to say, the "32-bit limit" application wise is for allocated memory by that program; for example, in order for firefox to start having problems related to that, it would need to allocate 2GB of RAM (to fill the user portion of the address space) at that point no doubt a well designed program will actually give out of memory errors. My point is, your application stopping dead in it's tracks is not a result of windows using up memory that the application could use. Worst case scenario is simply that it is hitting the 2GB address space limit, which is also highly doubtful. You also appear to be confused about what "used" memory is. memory Available to be used by applications is not necessarily free memory; for example, although Vista/7 allocate memory for Superfetch, it is still considered "available" memory; Superfetch gives up portions of it's cache if an application needs memory and there aren't any other unused blocks available (which is common, since generally superfetch uses up as much free memory as possible). As a result, there isn't a inkling of a possibility that your application is having trouble simply because the memory is being used by Vista/7 (Almost certainly by superfetch). This sounds more to me LIKE a design oversight or error on the part of the application developers (or perhaps one of the plugins or VST's). It might be an oversight or design flaw, I have an early version of Cubase.I was paying attention to how much ram is allocated to Cubase as I load my instruments and it gets close to 2GB before it starts doing the I CAN'T LOAD! stuff. Quote from: corlenbelspar on January 20, 2011, 12:40:34 AM I was paying attention to how much ram is allocated to Cubase as I load my instruments and it gets close to 2GB before it starts doing the I CAN'T LOAD! stuff. Yep, then it's allocating to much memory. How much windows 7 or any other programs are using has nothing to do with it; it would hit that 2GB Address space ceiling either way. There is, however, a way you can force an application to use more memory, but it will probably not work; you would need to set a flag inside the executable for the program; you can do this with something like PE Explorer; however, you would need to repeat this for every single DLL (such as the various Plugins) that the application uses; and there is a very high chance this will cause the application to become more likely to hang crash, not less, but it might be worth a shot if you are as desperate as you say. PE Explorer is commercial software, but you could use the trial for this- it can be found Here Then, for every single DLL or EXE that the program uses, you would need to: Open it. in the left-hand PANE you should see a "characteristics" item. Click the hand holding a sheet icon there to open a dialog full of checkboxes. Here you would check off the "The Application can handle addresses larger then 2GB"; then save, and load the next one. make sure to back up them all first! Also: I'd check for official patches- no matter if they say anything about memory issues in the changelog or fix list. Thanks for the info. I learned something today. I will look into it if I still need more memory allocated to the program after the following: I just stumbled on to a technique by accident that for some reason when I load the WAV file data of the VSTs in the Kontakt player VST instead of using their intended VST interface, Symphonic Choirs for example uses 300,000kb instead of 1,200,000kb for one choir set. Why this is, I don't know, it's a bit disorganized and messy, but it works. I wasn't sure if Symphonic Choir's wordbuilder would work with Symphonic Choirs loaded in Kontakt player that allows you to dictate what the choir sings, but it does.Great going, i'll try it out myself.

Answer»

So I posted a few weeks ago about Windows 7 using up all my memory eventually. Well I ran into a huge problem. My music software is 32bit and can only use the FIRST 4GB of my memory. I could swap to a 64bit program but I don't know if that would solve the problem as most of my VST instruments are 32bit as well. Once I get to 51% usage, Cubase stops loading everything dead in its tracks. I had to do away with RAIDXpert because I honestly can't use my music software anymore if it's eating up all the RAM but now Windows still is using 1.46GB of memory with Firefox open and nothing else with the exception of the background programs. I've turned off the Aero theme and switched to classic hoping that would reduce memory usage as well. Are there any other things I can do to reduce the used memory? My VST instruments require a lot of RAM to work and I mainly use the computer for producing my music. Maybe I'm asking for too much for the usage to be reduced further? I'm desperate and willing to deal with system SLOW down or minor instability or anything of that nature to be able to have access to more memory in Cubase, if need be.Why don't you try using another operating system other than Win 7 for your music software?I don't have the money to buy a different operating system, this one came with the computer and the computer has 8GB of RAM so downgrading to a 32bit OS is also probably a no go for me.a 32-bit program isn't LIMITED to the first 4GB of memory. all 32-bit processes have a 4GB address space, 2GB for the program itself, and 2GB for kernel space. This is address space not necessarily physical RAM.

That is to say, the "32-bit limit" application wise is for allocated memory by that program; for example, in order for firefox to start having problems related to that, it would need to allocate 2GB of RAM (to fill the user portion of the address space) at that point no doubt a well designed program will actually give out of memory errors.

My point is, your application stopping dead in it's tracks is not a result of windows using up memory that the application could use. Worst case scenario is simply that it is hitting the 2GB address space limit, which is also highly doubtful.

You also appear to be confused about what "used" memory is. memory Available to be used by applications is not necessarily free memory; for example, although Vista/7 allocate memory for Superfetch, it is still considered "available" memory; Superfetch gives up portions of it's cache if an application needs memory and there aren't any other unused blocks available (which is common, since generally superfetch uses up as much free memory as possible). As a result, there isn't a inkling of a possibility that your application is having trouble simply because the memory is being used by Vista/7 (Almost certainly by superfetch).

This sounds more to me LIKE a design oversight or error on the part of the application developers (or perhaps one of the plugins or VST's).

It might be an oversight or design flaw, I have an early version of Cubase.I was paying attention to how much ram is allocated to Cubase as I load my instruments and it gets close to 2GB before it starts doing the I CAN'T LOAD! stuff. Quote from: corlenbelspar on January 20, 2011, 12:40:34 AM

I was paying attention to how much ram is allocated to Cubase as I load my instruments and it gets close to 2GB before it starts doing the I CAN'T LOAD! stuff.

Yep, then it's allocating to much memory. How much windows 7 or any other programs are using has nothing to do with it; it would hit that 2GB Address space ceiling either way.

There is, however, a way you can force an application to use more memory, but it will probably not work; you would need to set a flag inside the executable for the program; you can do this with something like PE Explorer; however, you would need to repeat this for every single DLL (such as the various Plugins) that the application uses; and there is a very high chance this will cause the application to become more likely to hang crash, not less, but it might be worth a shot if you are as desperate as you say.

PE Explorer is commercial software, but you could use the trial for this- it can be found Here

Then, for every single DLL or EXE that the program uses, you would need to:

Open it. in the left-hand PANE you should see a "characteristics" item. Click the hand holding a sheet icon there to open a dialog full of checkboxes. Here you would check off the "The Application can handle addresses larger then 2GB"; then save, and load the next one.

make sure to back up them all first!

Also: I'd check for official patches- no matter if they say anything about memory issues in the changelog or fix list.

Thanks for the info. I learned something today. I will look into it if I still need more memory allocated to the program after the following: I just stumbled on to a technique by accident that for some reason when I load the WAV file data of the VSTs in the Kontakt player VST instead of using their intended VST interface, Symphonic Choirs for example uses 300,000kb instead of 1,200,000kb for one choir set. Why this is, I don't know, it's a bit disorganized and messy, but it works. I wasn't sure if Symphonic Choir's wordbuilder would work with Symphonic Choirs loaded in Kontakt player that allows you to dictate what the choir sings, but it does.Great going, i'll try it out myself.

Solve : Windows 7 Memory Again?

Discussion

No Comment Found

Related InterviewSolutions

Reply to Comment