Vegas 9 Demo does not render but crashes

Perrone Ford · August 12th, 2009, 09:18 AM

These threads amaze me.

Rule 1. Install a clean OS. There is no telling what garbage on your system is causing issues.

Rule 2. Install adequate RAM. Most of the issues I see with people seeing Vegas freezing up, failing to render HD, etc., have simply run out of RAM. Open Task manager with your HD project on the timeline and note how much RAM is left. Then start the render and watch your RAM decrease. Eventually, it will get critically low, and you'll see Vegas freeze. HD rendering demands a LOT more RAM than SD.

Rule 3. Keep your codecs in order. Vegas 9 does not include Cineform. So if you've been using Cineform in V8 or V7, you'll need to download the Cineform reader to use those older files in Vegas 9. If you want to render Cineform files in V9, then you'll need to buy Cineform software.

Rule 4. Keep garbage off your editing system. Don't put a bunch of web browsers, games, and other crap on your editing machine. If you install Vegas, DVDA, and your necessary codecs onto a clean OS, and you have adequate memory, 99% of these "issues" will disappear.

My primary editing machine has Vegas 9.0a 32 and 64 bit on it. Runs like clockwork on Windows7 RC. It has 8GB of RAM. My laptop has Vegas 8.0c, 8.1, 9.0a 32/64 on it, and it's running XP64. It has 4GB of RAM. No issues whatsoever. Zero.

I've used both machines to render 1-4 hour HD projects. However, I don't use long GOP stuff on the timeline usually, as that will SLAUGHTER most machines because of the RAM requirements. I do render the occasional AVCHD project for friends, but keep the durations under 20 minutes usually.

Jim Snow · August 12th, 2009, 09:49 AM

Lots of good points Perrone. Unfortunately some people get more out of arguing than fixing the problems they are having. For example - "Install a clean OS" is for everyone else, not them. Sounds harsh, but their problems are richly deserved.

William Ellwood · February 4th, 2010, 09:46 AM

I built an i7 920, 6GB ram 2 x 1TB HDD's, 9600GT rig for a friend. Win7 64bit. He's editing 1920 AVCHD, and as yet, can't export to 1920 - and 1440 seems its limit.

There is a CFF explorer fix originally for v8, that changes flags on the app to let it use more that 2GB of memory. On the trial version of Vegas Movie Studio 9 in my rig, that fix does speed up rendering by around 10%. But I've only got 1440 res HDV to play with.

Bruce Phung · February 4th, 2010, 12:18 PM

Quote:

Originally Posted by Jim Snow

Lots of good points Perrone. Unfortunately some people get more out of arguing than fixing the problems they are having. For example - "Install a clean OS" is for everyone else, not them. Sounds harsh, but their problems are richly deserved.

Agree. Why wasting all times trying to fix and got no where. Install a clean OS is the best bet. I never ever have any rendering crash problem; avchd. No problem with 32 bit Vista latop and my new desktop Windows 7 64 bit.

August 12th, 2009, 09:18 AM	#31
Perrone Ford Inner Circle Join Date: Nov 2006 Location: Tallahassee, FL Posts: 4,100	These threads amaze me. Rule 1. Install a clean OS. There is no telling what garbage on your system is causing issues. Rule 2. Install adequate RAM. Most of the issues I see with people seeing Vegas freezing up, failing to render HD, etc., have simply run out of RAM. Open Task manager with your HD project on the timeline and note how much RAM is left. Then start the render and watch your RAM decrease. Eventually, it will get critically low, and you'll see Vegas freeze. HD rendering demands a LOT more RAM than SD. Rule 3. Keep your codecs in order. Vegas 9 does not include Cineform. So if you've been using Cineform in V8 or V7, you'll need to download the Cineform reader to use those older files in Vegas 9. If you want to render Cineform files in V9, then you'll need to buy Cineform software. Rule 4. Keep garbage off your editing system. Don't put a bunch of web browsers, games, and other crap on your editing machine. If you install Vegas, DVDA, and your necessary codecs onto a clean OS, and you have adequate memory, 99% of these "issues" will disappear. My primary editing machine has Vegas 9.0a 32 and 64 bit on it. Runs like clockwork on Windows7 RC. It has 8GB of RAM. My laptop has Vegas 8.0c, 8.1, 9.0a 32/64 on it, and it's running XP64. It has 4GB of RAM. No issues whatsoever. Zero. I've used both machines to render 1-4 hour HD projects. However, I don't use long GOP stuff on the timeline usually, as that will SLAUGHTER most machines because of the RAM requirements. I do render the occasional AVCHD project for friends, but keep the durations under 20 minutes usually. __________________ DVX100, PMW-EX1, Canon 550D, FigRig, Dell Octocore, Avid MC4/5, MB Looks, RedCineX, Matrox MX02 mini, GTech RAID, Edirol R-4, Senn. G2 Evo, Countryman, Moles and Lowels.

February 4th, 2010, 09:46 AM	#33
William Ellwood Regular Crew Join Date: Dec 2008 Location: Consett UK Posts: 110	Editing AVCHD on Movie Studio 9 Platinum I built an i7 920, 6GB ram 2 x 1TB HDD's, 9600GT rig for a friend. Win7 64bit. He's editing 1920 AVCHD, and as yet, can't export to 1920 - and 1440 seems its limit. There is a CFF explorer fix originally for v8, that changes flags on the app to let it use more that 2GB of memory. On the trial version of Vegas Movie Studio 9 in my rig, that fix does speed up rendering by around 10%. But I've only got 1440 res HDV to play with. __________________ Billy Ellwood is on Vimeo. Film club www.newcastleaca.co.uk i7 7700k, Asus z270f, 32gb ram, Windows 10, Premiere CS6.

August 12th, 2009, 09:49 AM	#32
Jim Snow Trustee Join Date: Mar 2009 Location: Santa Clara, CA Posts: 1,104	Lots of good points Perrone. Unfortunately some people get more out of arguing than fixing the problems they are having. For example - "Install a clean OS" is for everyone else, not them. Sounds harsh, but their problems are richly deserved.