• VEGAS Pro

  Long render problems

  Posted by Jerry Waters on March 19, 2008 at 2:22 pm

  Can anyone explain why Vegas 8 is having trouble with long render problems? I can’t get it to do a long render of a WMV that it previously did. The only difference could be a few short (about 3 frame) stills added.

  I searched the forum and found someone had a “work around” of rendering back to m2t and taking that back to Vegas 7. I don’t find that acceptable in my case.

  Thanks for any help.

  JerryW

  Alex Werner replied 18 years, 1 month ago 3 Members · 3 Replies
• 3 Replies

• 

  Douglas Spotted eagle

  March 19, 2008 at 3:05 pm

  What is the failure message, Jerry?

  Douglas Spotted Eagle
  VASST

  Certified Sony Vegas Trainer
  Aerial Camera/Instructor
• 

  Jerry Waters

  March 20, 2008 at 8:49 pm

  No message, the programs just hangs and stops – at 45%, at 75%. I was using a standard template – HD 24p 1440×1080 1.333px 6.4 bitrate. I think it was a few stills dropped on tracks and/or some looks from a program I’m beta testing. So I rendered out the CineForm file. This time it hung at about 65% – very odd. I cut that one off, went in and rendered the end of the file without problem and then put those two CF files on the timeline. It then rendered the template file. Now I’m trying a WMV at 1920×1080 sq pixels, 7.4 bitrate. (I can show my movie HD this way on my JVC ProHD box.) I’ll report the problem to the beta people.

  JerryW
• 

  Alex Werner

  April 8, 2008 at 2:57 pm

  I actually have the same problem with the renderer just stopping after some time, if the whole video is either too long or quite big (like 720p at 12 minutes or more). One specific project always stops at 24% on one pc, at a different % on another one. I try to get around with a distributed rendering, but this is much more work as the video is uncompressed, and has to be compressed afterwards, so its one more step of calculation.
  It seems to me Vegas doesnt handle the memory very well, as the used memory grows bigger and bigger – is it keeping the whole video file in the memory? My machines have both 4GB of RAM, lots of more space on the HDD and as virtual memory allocated. So the problem could be that Vegas isnt actually frozen, but extremely slowed down to almost standstill due to the extensive file swapping. But these are just wild guesses… any more info on this from someone?

  alex.

Reply to this Discussion! Login or Sign Up