Building Peaks stops at 46%, render error low mem

cynicl12000 wrote on 3/31/2011, 1:51 PM

Hello all,

I just installed Vegas 10 a few days ago, and have been having a heck of a time with it.

First of all, I have a few videos that are HD and use 5.1 sound. When trying to build the peaks, the process consistently hangs at 46% (it also displays 2 of 3). In the task manager, I see that the Vegas process is utilizing a small amount of processor (6-8%), but I have left this for hours and the progress goes no further. I have cancelled the process when I first open Vegas, and this seems to allow me to continue, but I'm worried this may affect the render I'm trying later.

I am currently trying to render a 1 hour, HD 6.8 GB mpg file to wmv HD. My processer is a Second Gen i7 2630QM (4 core & hyperthreading) with Turbo Boost allowing it to jump to clock cycles at 2.9 gHz. I have 8 GB DDR3 RAM, and have manually set my paging file to allow for up to 12 GB's (it was originally 8GB).

The video file I am rendering, and the output from the render are both going on to a secondary (non-OS) internal 7200 rpm hard drive with 100's of GB free space.

By these specs, I am baffled that I get an "Out of Memory" error. Has anyone run into this before and fixed it that can give me some advice?

Thanks in advance,
Tim

Comments

Steve Grisetti wrote on 3/31/2011, 2:03 PM

First, make sure your drives are both defragmented and clear of spyware and tmp files. Video editors not only need lots of scratch disc space, but they need it in large, contiguous chunks.

Also ensure that your second hard drive is formatted NTFS rather than FAT32, as they come from the factory. FAT32 drives have a file size limitation that can also choke video editing.

cynicl12000 wrote on 3/31/2011, 2:50 PM

Hi Steve,

Thanks for responding.

Both of my drives are indeed NTFS. After an analysis, both are showing as 0% fragmented in the Windows 7 defrag utility.
OS disk shows 475 GB free space and secondary drive shows 329 GB free, so there should be lots of contiguous space to write to.

I run NOD32 as my AV, and it's showing everything as hunky dorey.

I haven't tried doing a disk cleanup, but I would imagine that there's plenty of room for it to play in - would having a temp file cause the issue regardless of space, or were you just mentioning that as a way to clear up contiguous blocks?

Steve Grisetti wrote on 3/31/2011, 5:02 PM

It could, but it's not terribly likely.

I think there must be going on than can be quickly diagnosed. Sorry I can't be of more help.

cynicl12000 wrote on 3/31/2011, 5:19 PM

Thanks for trying, anyway, they were good suggestions.

philRmonic wrote on 4/1/2011, 12:37 AM

I had the same problem when I upgraded my computer to a similar spec to yours. After I applied the "2gb memory cap" fix outlined in other posts on this forum I haven't had any problems of that nature. Look at "Possible easier fix for 2GB Memory cap problem?" and see if that helps.

cynicl12000 wrote on 4/1/2011, 9:56 AM

Thanks Phil!

I have downloaded and run the LAA program, but won't have a chance to try it until this evening. I'll post back my results.

cynicl12000 wrote on 4/2/2011, 3:53 AM

Phil,

Thanks, that worked perfectly!

I have now been able to successfully complete the video render - it made it all the way through render to expose an issue with audio! I assume this is the same problem that causes the issue with the peak building. Through trying different video files of different format, I have discovered that if I edit 2.0 sound, it works just fine, but so far 5.1 fails every time with no exposure as to why (the error log that you can send to Sony shows an unhandled exception - so it may be code related).