Long Render – Now NO RENDER!

[Stephen Mann]

“1.Are you using separate drives for rendering? Is there sufficient space? Do not forget that Vegas uses a default for the Temp folder. So that you might have sufficient room on the destination drive but not enough on the primary. Also please allow at least 10 gigs of space on any drive you are using to render as windows does not accurately report the remaining disk space. For example it does not redeem anything in the trash until you empty the recycle bin. ”

I have run out of room on the temp drive and Vegas just stopped. This was a while ago, like V6, and I have added a check for temp space to my workflow.

But I would look at core temps in this case. BTW, Windows XP and Vista default to automatically restart on errors so you never get the BSOD. You can uncheck the “Automatically Restart” in System/Advanced/Start and Recovery-Settings. Now, you too can experience the famous BSOD.

Oh, one more thing. Do NOT upload the screen dump of your error log or BSOD screen. The information is worthless to everyone but the original programmer. All you need to know is what application triggered the BSOD, and why.

Steve Mann

Steve Mann
MannMade Digital Video
http://www.mmdv.com

[Stephen Mann]

One more thing….

Remove any unused media from your project. I’ve experienced some rendering stops at 99% that was solved by clicking on the lightning icon in the project media window.

Steve Mann
MannMade Digital Video
http://www.mmdv.com

[Joe Mantaratz]

Like I had said before you just never know what will fix the problem and freeing up resources is the biggest. That being said let me address the BSOD issue. It is commonly thought that the restart on failure option will avoid that window, actually it does not. Why would you want a reboot to never be able to see the fault anyway? This was microsoft’s way of dealing with a buggy program. Out of sigt out of mind thing. Otherwise it makes little sense.

OK here is it directly from Microsoft concerning Page File and BSOD
Most crashes are due to memory allocation errors and then drivers conflicts. In that order most of the time.
Here’s a good link to better explain it, not from Micorsoft.

https://www.datarecovery.com.sg/data_recovery/hard_disk_symptons_blue_screen.htm

Another workaround may be necessary if the minimum size of the paging file is set to a value less than the amount of physical memory. Windows requires a paging file on the system drive large enough to hold all of physical memory, plus 1 megabyte (MB), to write debugging information. You can modify the PagingFiles value of the original installation so that the dump file can be created by the STOP error message. Enough free disk space must be available on the system drive for the paging file.

All this being said without being there with you it is tough to diagnose. But a good understanding of the basic can perhaps help you find a solution that works.

[Charles Biddle]

I’ve been doing several HD projects (Final output for web and BD in both 720P and 1080i) and Vegas crashes over and over. My fix/work around was to render to HDV (my source was XH-A1 in 30f) 1080i progressive template as an AVI (cineform codec 2.8 or 3.3). The part that matters is the following.
#1 Resave your project with a new title and call it ????RenderSections
in it’s own folder.
#2 Attempt to render the the AVI (other wrappers won’t work for this AFIK)
#3 When the render stops open your render folder and place the rendered portion of the timeline on to a new top track (to the frame of source material)
#4 Repeat rendering from end of rendered material to end numbering 1,2,3,until timeline is rendered.
#5 Render final project from the intermediates.
#6 Send hate mail to Sony for making simple task PITA.
#7 Finish project and start on next.

AVI files will crash, but they close themselves (unlike MPG or MP4) and the rendered portion will be fine to use. This is my current work flow until sony gets off their behind.

So when is the Scarlett coming out again 2009, 2010, 2011…

[Joe Mantaratz]

Was curious as to what the final outcome was. We’d all like to learn from your experience so if you can please pass the info along. Hope it all worked out.
Joe

[Corey Whitley]

WOW!

Sorry it has taken me so long to get back to you fine and now lifelong friends, but the deadline was demanding.

First of all thanks! To everyone for all of your input. If it wasn’t for a combination of suggestions I don’t know that I would have been able to figure things out.

Not sure if I mentioned this in the original post but on Friday I was attempting to render at home. All of the renders from work had crashed and I figured something was wrong with the system there, so why not attempt at home. If it takes longer who cares as long as it renders. Well it wouldn’t.

Thanks to Don, I unchecked the enable no-recompress long-GOP rendering at the bottom of the Options>Preferences>General Tab. Not sure why this helped but I think it has.

Then under the Video Preferences Tab I lowered Dynamic RAM Preview to 24
and the Maximun Number of Rendering Threads to 1

Then upon everyone’s advice I stopped almost all of my startup programs, unhooked the internet, and changed the power options and gave it another go. Fully expecting to break my computer. But an hour and a half later I was still rendering with no hick ups. I called my boss and had him perform the same functions with the work machine and give it a go.

When I got in on Monday we had a fully rendered 30 minute piece to show to the client. Unfortunately it looked like crap. Using the default DV NTSC codec for .avi produced a ton of ghosting, blur and no definition in any of the Vegas, Photoshop or AE text and graphic elements.

Then I tried a straight print to tape using Decklink HD for the Beta Deck. This produced a very crisp result. Not perfect! But easily the best quality I have seen out of Vegas. As I am typing this the work computer is rendering for a straight print to tape again with 3 nested elements dropped into the time line to see if it will work. Here’s to experimentation under the gun!

It is still taking a long time. 30 minutes is running about 9 to 10 hours on the quad core. A 3 minute element took an hour and 40 minutes today. But the video looks really good.

Now I realize most people, myself included, do not have the luxury to print to Beta, so any and all rendering templates people have found that work should be displayed on the COW somewhere. It would be awesome to have a quick reference to some settings that really work for people. I hope the simple hints people here have given me over the last couple of days helps others out. And thanks again to all.

Keep this thread going if there are any other questions, or better yet answers.

Corey Whitley

[Joe Mantaratz]

There is wealth of knowledge out there to be learned and shared. Very glad this worked for you. Did you ever get the chance to check those temps? It is all part of the system health. Take care.
] Joe