Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums VEGAS Pro Rendering stops and freezes Vegas at one hour?

  • Rendering stops and freezes Vegas at one hour?

    Posted by Kent Clark on November 22, 2009 at 10:42 pm

    I’m trying to finish a project for Thanksgiving. It is standard DV. The whole project is 61 minutes long. I’m rendering with Main Concept mpg2 template and ac3 sound. Based on advice here I’m using CBR of 8,000,000. Rendering takes about 5 hours on my Q6600 quad core cpu with Win XP pro, 4 gb RAM.

    I’ve run the render twice now. The first time it got to 60 minutes and stopped rendering. The clock kept running in the render dialogue box but no frames were being processed.

    The second time I left it running and came back to find that Vegas Pro 8 had closed. The video file that was compiled shows it stopped again at 60 minutes.

    This is about the 20th DVD I’ve made with this setup, all the others finished fine but they were VBR and each disc was about 75 minutes.

    Any suggestions about what is happening? I’ve got to finish this by Wednesday and burn 20 copies so I’m getting pressed for time (this is not my job, just doing it in my spare time for family).

    Marilyn Palacol replied 16 years, 5 months ago 5 Members · 13 Replies
  • 13 Replies
  • Scott Francis

    November 23, 2009 at 12:30 am

    I;m not sure why you are using a CBR, VBR should be fine and if you have enough room on a DVD for that. If you are planning on using menus and such, download a bitrate calculator to find out your settings. There will be a minimum, average and top setting in the video settings. Good luck!

    gotscottgreen

  • Mike Kujbida

    November 23, 2009 at 12:48 am

    Scott, for anything under 70 min., I always use the same CBR setting Kent did.

    Kent, 5 hr. to render a 1 hr. project with a quad core?
    I don’t remember the last time I had a render take that long and I do projects longer than that all the time.

    Do you have a lot of FX and large stills in this project?

    If you want to use VBR settings, try 8,000,000 / 8,000,000 / 4,800,000.

    If all else fails, do a render to AVI (use Best mode) first and then encode that file for DVDA.

  • Kent Clark

    November 23, 2009 at 2:59 am

    I have about 3 dozen large stills and I did a color correction and a sharpen on the whole video track. I’m rendering in VBR with your settings right now. It finishes in about 50 minutes, I hope.

    Thanks as always for quick responses and help.

  • Kent Clark

    November 23, 2009 at 3:43 am

    Well I just sat and watched Vegas crash again at the same place in the render, on one picture 40 seconds from the end of the project.

    It got to the picture and then stopped running frames for a few seconds, then I got a Microsoft error message saying that Vegas.exe had encountered a problem and had to close.

    I ran a test of this project a few days ago, with this picture included, and it rendered fine. I made a few corrections in places and now it crashes every time it gets to the picture. It is a png, nothing special about it.

  • Mike Kujbida

    November 23, 2009 at 10:32 am

    Kent, I’m not sure if this will help or not but give it a try.
    Resave the image from Photoshop or whatever image processing program you’re using but give it a new name.
    If the image is larger than project size and doesn’t need to be, resize it to project resolution.
    In Vegas, delete the original image from the project and substitute the new one.
    Save the project, reboot the computer and try it again.

    If all else fails, try my “render to avi” suggestion.

  • John Rofrano

    November 23, 2009 at 11:09 am

    I would also make a timeline selection of the end of the project and try and render that alone to see if it’s something about the picture or section of the timeline. If that renders fine then you may be running out of memory or resources at that point after rendering for so long.

    If it is that picture, resize it down to 1440×960. That’s twice DV resolution and should be plenty big enough. If your other pictures are too large they may be using up too much memory as well. Resize them too.

    Since this is DV and you are up against a deadline, I would definitely render this out in two sections as an AVI file and then drop the two AVI files into a new project and render as MPEG2.

    My Quadcore renders DV to MPEG2 at 3x! So an hour of straight DV AVI files takes only 20 min to render to MPEG2. What are you doing to make it take 5 hrs? (rhetorical question, BTW) Wow, that’s a lot of color correcting.

    ~jr

    http://www.johnrofrano.com
    http://www.vasst.com

  • Kent Clark

    November 23, 2009 at 2:43 pm

    I ran it again last night after removing the sharpening FX. The color correction is on the whole video track, it was blueish and I warmed it up. That is the only FX.

    All of the pictures are 2x DV resolution.

    Yesterday I rendered the last five minutes of the project, no problem.

    One week ago I rendered a preliminary version on another computer, dual core, it took 10 hours and it had all of the pictures and the same length. The whole thing rendered.

    The strange thing is that the quad core system has been used to render about 20 projects in the last year, all of them more than an hour.

    Thanks so much for the help. I’ll let you know what happens today.

  • Kent Clark

    November 24, 2009 at 3:34 pm

    It looks like there is some problem with my pc or the software on that pc. I rendered the whole project on a second computer. Right now I think I’ll reinstall Vegas and then do a test render. The only major change on this pc since the last time I used it for rendering was installing adobe photoshop CS4 and Lightroom. No hardware changes at all.

    Thanks again for all of the responses and help.

  • Marilyn Palacol

    November 26, 2009 at 8:50 pm

    This conversation is fascinating as I thought all renders for projects 20 minutes or over take no less than 8-10 hours to complete which has been my experience. I’m having the same problem right now as my Vegas Movie Studio 9 Platinum project is stuck at 84% and 30 minutes has passed with no movement. Total elapsed time has been 9 hours. Approximate time left is 0:00.

    I’m tempted to reinstall Vegas as I’m at the end of my rope. Will the .vf file still open with all it’s respective tracks after reinstalling? My fear is I have to start at ground zero. Or I may render in blocks which I havent’t tried yet and reconnect the mini renders in DVD Architect. Is the latter a better solution?

    I thought Vegas Movie Studio was the end all complete package but from what I’m hearing from all these discussions, ift’s apparently deficient in many respects. Is it considered a watered down Vegas?

    Thanks for any tips!

    Marilyn

  • Mike Kujbida

    November 26, 2009 at 9:18 pm

    Marilyn, render times are dependent on a wide variety of factors including, but not limited to, your computer, the length of the project, the type of files used, the number, size and format of still images and the number of FX you have in the project.
    That’s why it’s almost impossible to say how long a render should take.
    For example, a project I did a few years ago took 3 hr. to render and it was only a 10 min. video.
    This was because it had a lot of FX on it and the computer I had was a lowly P4 3.4 GHz machine.
    When I upgraded to a quad core, the render time dropped to 27 min.

    Movie Studio is the little brother to Vegas Pro.
    The Pro version offers features such as unlimited tracks (both audio and video), more color correction options and the big one (for me at least) is scripting.

    To troubleshoot the problems you’re having, we need as much detail as you can provide us.
    CPU type;
    Operating system;
    amount of RAM;
    number & size of hard drives;
    what types of files are in the project;
    if you’re suing images, what type and size (in pixels) are they;
    what types of FX you’re using.

Page 1 of 2

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy