hmm... there were registry changes for premiere a while back but if you check now its just "cs3 will solve it in this way....blah blah blah"
Don't know if this helps....if your trying to render your work area and it says out of memory maybe have a look here.
http://www.ittvis.com/services/techtip.asp?ttid=3346
Also if your just wanting to export your stuff set up a frame server to something that will handle your memory better.
If you figure it out leave a note on here so we know in the future.
Limit RAM used by Premiere Pro?
-
lister007
- Joined: Fri Jan 21, 2005 2:50 pm
- Location: Great Britain, um the country with the best flag;)
Spatchcock..........A dressed and split chicken for roasting or grilling on a spit.
Bring it
Berserk or crazy...??? (image shack sucks will have a banner for this too when it doesn't!)
Bring it
Berserk or crazy...??? (image shack sucks will have a banner for this too when it doesn't!)
-
Bauzi
- Joined: Fri May 21, 2004 12:48 pm
- Status: Under High Voltage
- Location: Austria (uhm the other country without kangaroos^^)
- Contact:
I didn´t test it, because it won´t work. It´s a too big (overall) process and it would give me only a few more minutes. It´s not a limitation at all.Out of link wrote:Solution
The Microsoft developer tool Visual C++ includes a utility called editbin.exe, which can potentially win an IDL process a couple of 100 MB additional contiguous virtual memory space at process start. This utility, run at the DOS command line, has a parameter option "/rebase", which enables end-users to force any application DLL to move from its default address to an address of the user's choice. With this utility, one can "pack" DLL'S, which are loading at too high a starting address, down in the lowest virtual memory addresses that the system will allow. This is not likely to be a good solution for an IDL application that has to run frequently with very large array allocation, but rather is a utility you might use when you have a one-time IDL process you want to test, you think it is failing by just 100-200 MB of malloc() capability, and you have exhausted the other options we have suggested above.
I wonder how the PROs work at Windows. I mean... it limits the RAM used by a progress to 2GB. I don´t know if Macs give them more.
To the frameserving stuff... ok is a good solution for exporting that I forgot. I already have it on my system, but it didn´t work (even with the whole help files) so I gave up. I should pick it up again!
Let´s upgrade?!hmm... there were registry changes for premiere a while back but if you check now its just "cs3 will solve it in this way....blah blah blah"
You can find me on YT under "Bauzi514". Subscribe to never miss my AMV releases. 