media specs not important really as they are they are same I've used for last 4 or 5 years without a problem .48k, 24 bit, mp4. I've pretty much always deal with very large files as in hour or longer and never had a problem. Also bringing in new media will lock program up too at times.

Ok, suit yourself.
Crystal ball is at the cleaners.

Check for recent Windows updates or hardware updates.

Musicvid10, thanks for being an ass.
No hardware changes as stated plus computer is off line so no changes/updated to effect

There's no reason for abusive language. More info would have more people jumping in to help. Vegas can use system vfw codecs as well as those installed by Vegas, and third parties. If it's a Sony installed codec, a reinstallation may fix.

Can you render to anything at all? Audio only in wav or aif? Will a previously rendered clip (to the same codec you're trying to render to) play on the timeline?

Offer details of your workflow if you want help. Someone here has probably solved your problem before, but we don't even know what it is.

For the OP of this thread. I am sure you have a lot of experience and you have done the same thing a 1000 times. WE ALL HAVE! Now you have one event on your timeline that has corrupt frame from the video source. Don't blame the messenger here.

I just hate dinks. If you need more info just ask, not like music is where he just acts pompous. So atom, yes I can render. Like I said I'm used to rendering hour clips. No big deal. Now I seem to have to render shorter clips, like 20 minutes. I'll go to render a clip and nothing happens. Computer freezes. I then end program , open up Vegas again and try to tender shorter clips til it goes. Same settings I've used for years

Preview at best quality? Memory usage? Power supply hot? VegasPro app reset? Computer cold boot?

Not corrupt timeline. Happens on three separate projects so far

Yes I preview at best quality. Cpu usage low. Everything looks normal.dont need to cold boot just end non responsive program with task manager. I say no responsive but it never say" not responding "

At the risk of sounding like a dink, something has to have changed. If it used to work, and it doesn't now, then you have either installed new software, codec, update or hardware. Otherwise, it would still work.

Have you connected any new harddrives, disconnected drives, USB drives, added memory, new mouse, tablet, etc.

I dong know what Vegas pro app reset it however

DonaldT
No your not sounding like a dink.. Lol!! Your asking questions which are fine and I appreciate! To answer your question I I have not changed anything I can think of. Just new clips and new audio for new project. That's what's odd?? I know nothing of codes however

Are you rendering to a local (internal) drive or to an external RAID or USB?
Is your source media on an internal or external drive?
What format and bitrate are you rendering to?
Are you using the final build of Vegas 9, I believe it was released as 9.0e? 32 or 64 bit version?

I ask the last question because there were sporadic rendering issues with earlier builds that most everyone saw go away by the time 9.0e was released.

How many VegasPro app processes are now running in task manager?

Good heavens, man cold boot - come on get with it!

Lol! VideoIT guy, you said cold boot not me!! I assume by that you meant hold button in for 5 seconds? Note don't need to.

YOU NEED TO

YOU NEED TO

+1. It's really silly not to do a reboot--the one thing that often cures your PC ills--not just Vegas--that's part of PC 101. At most, it only takes a minute or two and if you have the same problem, at least you've ruled that out.. For ANY long render, it is always best to save your file, close Vegas and reopen. Even better to reboot before rendering.

Have you checked your CPU temps during render. If you could render hour long videos and then only 20 minutes, you may have an overheating problem. Install something like Speedfan and always have your temp showing in the taskbar. Rendering stresses any CPU. Again, it's another thing that you could easily rule out.

BTW, I agree with Musicvid10's initial response to you. All he asked was to be more specific, which others have done as well, and to date you have provided very little information--really very basic stuff like your source media (codec, frame size,frame rate, etc.), your Project settings, and finally render template information. There are render templates that I can use that will make Vegas crash every time. Without such information, everyone is really shooting in the dark. Taking a screenshot and posting it online is really pretty simple and can often be a big help to others trying to figure out your problem.

wwaag

No he did not ask , he was sarcastic and condescending. He did NOT ask a straight question

But once again, nothing I have done has changed. And YES I have restarted my computer , but a cold boot which is what you do when computer is froze which as I explained is NOT my case. The program froze not the computer hence no reason for "cold boot". And source media is on hard drive. Not C drive but secondary internal sshd

The man of few words can solve this problem.

No he did not ask , he was sarcastic and condescending. He did NOT ask a straight question

To quote:

"Good story.
With complete media and render properties (at the very least), someone might be able to help."

Nothing sarcastic or condescending that I can see--just the opposite. He's only asking you to provide your media and render properties. It's an implied question. In any case, good luck with YOUR problem.

wwaag