Rendering in HD is the cause of system low on memory.

[Lee Hayward]

£540 excluding VAT, is this what you would now consider ideal. will it work and stop the memory/cpu issue ( is it powerfull enough to render a complex HD video as i dont want to buy it and get the same error. im gonna email the site to see if they do trials.

[John Rofrano]

> is it powerfull enough to render a complex HD video…

OK, I went to their web site and I see the next PSU above the 450W is 700W. I would get the 700W. You don’t want to skimp in the power supply. It can be the cause of numerous intermittent problems that are very hard to trace but all point back to the PSU being underpowered during a long render where the load is the most demanding. Don’t forget, when you render you are running a very power hungry CPU at or near 100% for hours at a time!!! That demands a good power supply that can provide sustained power.

Instead of two 500GB hard drives I would stay with the 250GB for the OS drive and maybe go with the 1TB drive for video editing. The reason I say the 1TB is because there is a £8 difference in price between 2x500MB and 250MB+1TB so it makes better sense for the money.

> so two hard drives? what you put each at, would this mean i wouldnt need to partion them and why two hard drives as im a little con fused. i presume you would have both at 500 gb? could you tell me why two hard drvies and why 500gb.

The purpose of having separate drives is so that the read/write heads of one do not conflict with the other. Windows is constantly managing virtual memory and reading and writing blocks of memory to it’s swap file. If you have only one drive, when Windows starts to write to the swap file, it will stop reading your video files. This is not good and can cause stuttering during playback or dropouts during capture.

By having two physically separate drives, windows can manage the swap file on one and load programs from one, while your videos are being read and written to simultaneously on the other. This is why most people recommend two physically separate drives. One for your OS and applications and the other for you video project media so that you have independent access via independent drive heads (which you don’t get by partitioning one drive). They don’t have to be the same size and, in fact, the 250GB is more than enough for the OS and applications. The media drive should be as big as you can afford. You can never have too much disc space.

> also is the video card strong enough of should i go with a radeon HD?

Vegas doesn’t use the video card for anything so unless you have other applications that require a powerful video card there is no sense in buying one. You might want to get a 9000 series like the 9400GT with is only £6 more but it won’t matter to Vegas.

> …i dont want to buy it and get the same error.

Lee, You are assuming that a faster PC with more memory is going to solve your problem. Unless Sony Tech Support told you this, you may be very disappointed with the results.

In a 32-bit OS Vegas will never get more than 2GB of memory and your current PC has 3GB. I have been rendering hour+ long HD projects since 2005 with Vegas 6 on my XP32 PC with 4GB of memory (and XP can only see 3.25GB). I don’t believe that you are running out of memory or that adding more memory will solve your problem. Your original error is with with a Microsoft runtime library MSVCR90.dll. An Exception (0xc0000005) is a illegal access of memory usually caused by a bug in the code. So it could very well be a bug in Vegas Pro 9.0a, and you are buying a new computer because of it.

Having said that, the new computer might fix the problem only because it’s a new install of Windows. The illegal access could be a conflict in versions of libraries which a new install might fix. You may get the exact same results simply by re-installing Windows on your existing PC (which you can do without buying any new hardware).

The first thing I would do is work with Sony Technical Support and determine what the real problem is unless you really want to buy a new PC anyway.

~jr

http://www.johnrofrano.com
http://www.vasst.com

[Lee Hayward]

hi,
so far ive been working with sony support no soloution yet.

i see you mentioned on a 32bit os vegas will not use more than 2gb, well im using CFF explorer to alow vegas run on more than 2gb still no results, in a 64bit will vegas have more memory than 2gb?

i have put buying a new pc on hold at the moment.

i cant render this project in draft dvd resoution let alone best in 1280 x 720.

i split it again and still no luck.

i made a random project , wmv HD split the movie into clips add some Fxs and pics and it was at 2 mins length. and it rendered in 1280×720 HD wmv.and while it was open it was only at 300,000K unlike my main project at 1,000,000K (which is just under a GIG)

so its either a fault/corrution in my main project or is too complex for my laptop.( also my frames go red or black but a simple restart fixes this.

picture of the succesfull render of the other project.

picture of my main project which was unsucessfull

[Matt Cohn]

wow, its wierd to see this thread -on how to stop Vegas crashing- be mostly about how to get a better machine that will have enough memory etc to not crash. but as a couple of people pointed out, thats NOT THE PROBLEM. I have 3 top end machines, each with quad or 8 core, 32 and 64 bit, 4-8gig ram, and still Vegas cannot manage a render of a 20min section 1648×768 res project without falling over.

I got the 9.0b release, its the same.

One commentator pointed out that Vegas6 works fine for HD, much better than 9 by the look of it.

One step forward, 3 steps back. and imho thinking that a better machine will solve things WILL NOT HELP.

Come on, Sony, the program is not fit for professional use currently, it cannot even give a proper error message when it falls over. so sort it out please.

thanks
Matt

[Nhat Nguyen]

Thank you Matt for sharing. I have the same issue about “system is low on Memory…” when rendering HD Proj in Vegas 9.0b ,my poject is 1Hr33min and takes several Hr to render to MPEG2 .m2t file (I had to pray everytime Vegas render, about 3,4 times failed w/the error)
Finally i got it (I had to render couple sections then reload into the project and offcourse Quality degrade a little..)I was thinking
to spend more money for RAM but according to your post i won’t and
now i’m about to install Vegas 6 i try render HD..Hopefully it’s work.Thanks again Matt.
Nhat

[Lee Hayward]

i have just recived my new pc -2.83 ghz quad core 8gb ram, opened up projects it froze for 2 mins then when i started render it completed the full render 100% with in 40 mins. so i am extremely happy now i have managed to render and in such good time for HD video in wmv format, thanks to all what helped

[Kiraz Makrz]

Hi ,
i tried render on almous same PC ,
just lil bit less Ram was , and same error 🙁

[Lee Hayward]

mines a 64 bit version so it can use more than 3 gb ram, also has better memmory issues thers alot of topics about it, try a 64 bit pc rather than 32 bit, as it can handles b4 bits of info over 32 bits of info at the given time

[Jake Sedge]

Hi! A bit of an old thread, but I may have a breakthrough! I have a quad core @ 2.3Ghz+ 4Gb RAM and am having the same problem.

My idea is to use the network render feature, but not using other computers on your network. It renders the project in segments and stitches them back together, I will let you know if it works!

[Shaun Yee]

I have Windows 7 Ultimate 64 bit with 4GB RAM and Core 2 Duo 2.66 GHZ.

I have the same problem in Vegas Pro 9.0e in the 32 bit version. In Vegas 64 bit, I do not have that problem. Sony should really fix this.