Solutions

Dan Sherman wrote on 12/2/2009, 8:33 AM

Tried to render small clip about 23 seconds long.
Seventy-precent into the render preview went red, render stopped and window popped up telling me I don't have enough virtual memory.
Machine is Intel Core Duo CPU, 2.53 GHz, 1.96 GB of RAM.
Footage is 720p 30.
Running Raylight Ultra with Vegas 9.0c.
I have had successful renders with these MXF files previously.
My "C" drive crashed recenlty. It was 10,000 RPM.
It was replaced with a 7200 RPM.
I was told I wouldn't see much difference in speed.
Now I wonder if that is part of the issue.
Likley not all of it though, i think.
OR, and I just asking too much of my computer?
Don't want to build new computer if I don't have to.

Comments

MacVista wrote on 12/2/2009, 12:31 PM
I wouldn't have thought that the speed of the hard disk would cause the render to stop. Might slow it down a little but thats all.

I am curious that you list the amount of RAM as 1.96GB
Is this a laptop computer? Is the RAM being shared with the graphics card?

Running out of virtual memory is usually caused by running out of space on the disk which windows is using for it's page file.

You can check this by going to: My computer> properties> advanced> performance> advanced> Virtual memory: Change (in windows XP that is :-)

Personally I would add some more RAM :-)

You could also try selecting the area of your edit where it crashes say 10 seconds either side and rendering loop region only.

If it still crashes the problem is the material at that point in the edit.

Hope this helps,

Otherwise post more details about your setup and I'm sure you will get many willing helpers.
Dan Sherman wrote on 12/2/2009, 1:06 PM
This is a desktop built to Johnny Roy's specs a year or so ago.
The only deviation is the 7200 RPM "C" drive, original was 10,000 RPM.
Resintalled Vegas 9.0c, tried a couple more renders with no success.
One ended in a red preview screen the other not red.
Page file was set to 5000 max and 3500 min.
Max available was listed as 3120, so dialed it back to 2 and 3100.
Still no luck.
Another failed render.
Was going to up the RAM to 4 GB, but I have an audio recording session in a while and I don't want to have things torn apart for that.
Keep in mind this issue is a problem when rendering 720p 60 HD to uncompressed .avi.
Let me try mp4, right back.
Chews it up good!
Same with MPEG 2.
Another success.
Wonder of wonders, just rendered an .avi with no interuption.
Two more, one regular and one prerender. Both successful.
I slap 4 GB in it tomorrow.
Maybe it was the virtual memory settings?
Do the new ones take a while to kick in?

Whoops!
Spoke too soon.
Render fail a short time in. Red Screen.
So we have what appears to be an intermittent issue.

Dan Sherman wrote on 12/2/2009, 1:14 PM
So to the material itself.
Shot with a Pansonic HPX 170.
From P2 card to field laptop,---then to 320 GB external HDD, saved to desktop HDD back at the editing suite, and pulled onto the timeline for editing and rendering.
Followed by failed renders.
Raw footage shot in 720p 1280 X 720 60fps.
Rendered with 7209 30fps template as there is not one for 60fps.
fldave wrote on 12/2/2009, 2:28 PM
Using a Fat32 file system on the target hard drive?
fldave wrote on 12/2/2009, 3:58 PM
Fat32 shouldn't be it. 23 seconds should be about 4.9 GB, and 70% of that is 3.4 GB.
John_Cline wrote on 12/2/2009, 4:03 PM
"23 seconds should be about 4.9 GB"

Don't you mean minutes?
fldave wrote on 12/2/2009, 5:56 PM
"23 seconds should be about 4.9 GB"

"Don't you mean minutes?"



No, 23 seconds. He is rendering uncompressed 720 ad 60fps:
"Keep in mind this issue is a problem when rendering 720p 60 HD to uncompressed .avi."
Jay Gladwell wrote on 12/3/2009, 4:03 AM

Dan, may I ask why you're renderning out HD to uncompressed. avi?

Coursedesign wrote on 12/3/2009, 8:04 AM
2GB RAM doesn't cut it for working with uncompressed HD.

Spend the $50 or whatever and put in as much as you can.

Or don't bother with uncompressed, especially when there are near-lossless codecs that are so good that you won't need anything else even for all but the most heavy compositing.
Grazie wrote on 12/3/2009, 10:48 PM
Lagarith, great CODEC. And you get an ALPHA channel too.

Grazie
fldave wrote on 12/4/2009, 6:53 AM
The render shouldn't freeze for any codec. The codec shouldn't matter unless he only has 3.4 GB left on his target drive.
Dan Sherman wrote on 12/4/2009, 7:26 AM
All of the drives, external and on board have plenty of room.

Not using FAT32.

Where to we get Lagarith, Grazie? Buy?

Rendering to .avi is a workflow carried over from SD.
Complete a segment, render to .avi, lossless file saved.

Machine handles mp4 fine.

Defraged the OS drive. It was quite framgmented.
Reinstalled Vegas Pro 9c.

Something may be running in the BG?

Am adding another 2GB of RAM before I go to a quad core.
Don't want to do that right now or Mrs. Santa will brain me.
Jay Gladwell wrote on 12/4/2009, 7:40 AM

"Rendering to .avi is a workflow carried over from SD."

Consider Avid's DNxHD Codec. Works great in Vegas and it's free.

Be sure to download and read the whitepaper.