This is a 32-bit limitation and moving to both a 64-bit OS and 64-bit Vegas should work around it.although whatever Vegas is doing is probably less than efficient as well.Earlier this year, Red Giant updated several plugins in the Magic Bullet Suite for its version 12 update. There is also a new film simulation tool in the suite, aptly called Magic Bullet Film. If you see Virtual Size go above 1800mb for the Vegas process, lack of virtual address space is the cause of this error. It will show up on the far right, so you may need to drag it closer to the left or just slide the slider bar to the right to see it. Right-click on the column headers, click the "Select Columns." link, then "Process Memory" tab, then check "Virtual Size". Use Process Explorer from Sysinternals (now MSFT) at. More than likely the process is running out of virtual address space - 32-bit processes can only address 2GB maximum of private RAM, and that includes loading all binary images, movies, data, etc. Also, you would be seeing the problem in other things as well - like web browsing, sound editing, etc - unless the bad RAM has a grudge exclusively against Vegas (which is technically speaking VERY unlikely) :-) The memory manager would never show "bad" ram at a user-mode processes as it simply doesn't need to know or deal with that kind of low-level hardware issue. It is unlikely it is physically bad RAM as the OS will mark those pages as Bad and not use them if it detects problems with the data in that page. This MAY be being boiled up from a malloc() call or similar from the operating system, or Vegas could just be smoking crack. The screenshot of the error message (thank you!!) indicates the process cannot address any more memory. They flush standby pages so you have more "free" memory, but free simply means unused, and therefore wasted RAM that could be being used as cache. First of all, "RAM Optimizers" are garbage pure and simple, don't use them. I work for MSFT and can advise based on the data gathered so far. Sorry I did not read your whole post so sorry if I missed something. If so search for Eugenia's Vegas info on Vimeo (settings for hd render for Vimeo) - there is a note about a similar issue. See if this helps it render without a crash. This is assuming you have a multiple core chip. Please help me any idea ! I need to make some wedding clips for my sister but it has been already 2 weeks that I could not complete any.Find the setting in the preferences or options and select use ONE cpu to render. Please help me any idea ! I need to make some wedding clips for my sister but it has been already 2 weeks that I could not complete any. I searched around on the internet and so many people got the same problem as mine. What is the problem with my poor PC ? Because Radeon HD 5770 is not compatible with Sony Vegas Pro 9.0 ? That must be crazy because this is among the high-end cards these days. Then I borrowed from my friend his Vegas Pro 10.0. I updated (free) Vegas 9.0e from the homepage. Thinking that my PC might got some virus or some errors, I restored the Ghost Image of the hard disk like before (except that I had to install new driver for the lately newly installed Radeon card). I cannot understand this ! Really crazy ! It always crashed during rendering like what you can see from the following print-screen. I added more 2 Gb RAM To have 4 Gb RAM and replace the Geforce 8600GT with Radeon HD 5770 512 Mb.Īnd lately, I found that my Vegas could never render successfully a clip, even when the clip was just less than 30 seconds long. Originally, it was an AMD Phenom II X4 920, 2Gb RAM and Geforce 8600GT 512Mb. With this software, my PC rendered hundreds of short clips with variable lengths from one to ten minutes. I have used to using Sony Vegas Pro 9.0c for months.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |