-
Vegas Pro 8.0c crashes rendering large project
I feel like this is an old subject, but I’m hoping someone is figuring out a way to deal with Vegas Pro problems rendering large projects. I had a deadline last night and just made it by breaking my project up into pieces, but don’t much like that as a long term solution. I’m pondering rebuilding my PC with 64 bit Windows and loading up on RAM, but am not sure from other forum posts whether that helps or not.
Some notes on my specific problem:
1. My project includes a couple hundred subclips of basketball video from different sources. It’s in three formats: MPEG2, MTS and MOD. All import and work in Vegas Pro 8.0c, at least for editing.
2. In addition to video clips, I’m also using stills with keyframed pans/zooms. I batch processed all of these (JPGs and some PNGs) in Photoshop to reduce them to 720 vertical pixels for video use.
3. I did some bumper sections and transition elements in After Effects, and output them as WMVs or Quicktime if I needed RGB+Alpha. This included border elements to put behind SD video content and stills that don’t fill the screen.
4. I’m rendering to MPEG-2 DVD Architect NTSC Widecreen and Dolby Digital Pro so that the files don’t require re-compression when I burn them to DVD.
5. Total project is about 35 minutes long.What I know about my crashes:
1. I’m running on a Vista 32 bit Dell XPS 410 with Core 2 duo 2.7 GHz processor and 3 GBytes of RAM.
2. Vegas is running on my system drive, and my content and output is on a second internal drive. Both have 200 GBytes or so of free space.
3. With just about any setting, Vegas crashes within the first few minutes of rendering.
4. I’ve seen three types of crashes:
a. I usually get a “Sony Vegas has encountered an unknown error”
b. I’ve seen Vegas just disappear without any trace
c. I’ve once seen a warning about low memory
5. I’ve tried turning down my preview RAM to 16 MB, setting 1 thread of execution, and purging unused content from the project before rendering. I’ve also turned off Vista transparency and shut down any startup tasks. And I’ve tried changing my output file destination to a drive different than the content.I’m pretty sure memory is playing a part in this problem because I get big delays returning to Vegas if I open another Window or application. I also had some problems with Vegas crashing during editing as the project got large.
I met my deadline by breaking the project into three sub-projects. They rendered fine. I had to kludge my DVD with three separate start controls just because I was running to a team function and didn’t have time to do anything else. For my final version, I plan to import the pre-rendered elements and produce one complete one. Based on other posts, I hope this will work.
Long term, I need to be able to render large projects directly. For sports videos, I really value Vegas tracking which clips are used and which aren’t, and I lose that if I work in sub-projects. Have people found that running 64 bit Windows and Vegas 8.1 with more RAM (say 8 GBytes) helps with problems like mine?