HELP! Project Won't Render Anymore... :(

Soniclight wrote on 3/22/2011, 2:44 PM
Something really weird is going on...

No matter what codec I use (avi, wmv), the render in this project stays stuck on 0% and the real Twilight Zone part is this:

--- I mute all tracks, create a 1-second loop region as a test render area, move it to totally empty space to the end of the project far beyond any events, Render As... and it starts showing and rendering some event way, way back in the time line but still shows 0% and never finishes.

--- I move the 1-second loop to another totally empty area and the same "ghost" or non-existent event shows in Preview while the supposed render happens.

Yes, I tried another project and the problem doesn't occur. This smells like file corruption but it's a large and complex project (400+ clips and text media events listed in Project Manager) and I'm on a deadline...

Any way to fix this?
Probably not, but I hope so.
Thanks.

** LATER EDIT **

I was wrong about it working in other projects for I just tried another one and the same weird thing where a 1-second render take forever and renders non-existent events. Ergo must be some corruption in Vegas's render engine.

So I'm going to have go the un-install/re-install route.
I sure hope that fixes this.

Comments

farss wrote on 3/22/2011, 3:05 PM
" This smells like file corruption "

Sounds to me like your project file is corrupted.
Hopefully you've got incremental versions of your project so go back to the previous version and see if that renders OK. If that's OK then you've probably lost whatever you've done since you made that backup.

Bob.
Soniclight wrote on 3/22/2011, 3:09 PM
Bob,

I just added an edit to the above whereby the situation is now different. I tried a backup from last night before I did the overnight render that had hiccupped in a spot or two that I wanted to fix today and re-render it. No-go on that project or any other now either.
rs170a wrote on 3/22/2011, 3:38 PM
Philip, have you tried doing a copy/paste of a few clips to a brand new project to see if it will work?

Mike
Dreamline wrote on 3/22/2011, 3:44 PM
In preferences video tab make sure the dynamic ram is set to 0 & maximize thread to 1. I had the same problem today and that fixed it for me. Thank god. If that works try setting the thread count incrementally higher for faster renders.

The real question is where is Vegas D?
farss wrote on 3/22/2011, 4:10 PM
I'd suggest starting a brand new project, add a few clips and see if that renders OK.

When I struck this kind of problem I found that the corruption had occured days before and I simply had not noticed it. In total I had to go back over 1 week to find an uncorrupted project file.
In my case and others reported by many here rendering wasn't the issue, the project would render but it was plain wrong, clips were swapped or clips that had nothing to do with the project were swapped for the correct ones. So Soniclight's problem maybe something different but it does have some of the same attributes.

I think it's really best to diagnose what is wrong before simply trying things at random. Doing a bare metal re-install of Vegas is not a trivial task by the time you clear out the registry etc. Doing that and not resolving the problem can be time wasting and frustrating.

Bob.
Soniclight wrote on 3/22/2011, 4:53 PM
Thanks for replies, but I was right: re-install of Vegas fixed the problem. Must have been some analog/celluloid gremlin unhappy with the new world order of digital film-making who came and messed with my Vegas during the wee hours of the morn... Ah, these Luddites:o)

For now, I just re-installed Vegas bare-bone, I'll get around to updating and re-installing scripts and stuff later. I just need to finish this video and get it out the door.
farss wrote on 3/22/2011, 5:04 PM
Certainly true that s**t happens. I've never once had a problemo fixed by re-installing Vegas which is why I'm very reluctant to recommend doing it. I also know how much effort it takes to get things back the way they were.
The only time I've had to re-install Vegas was when a HDD went south and I sincerely hope this problem was not caused by one tettering on the brink.

Bob.
Soniclight wrote on 3/22/2011, 10:36 PM
Well, I'm sure that for you (a pro in this field) your Vegas setup is probably far more complex and layered than what I have (I use some extensions but rarely any scripts, etc.) so no biggie to reconstitute really. Now...

My computer and XP, that's a whole other enchilada. I don't know what I'd do without my True Image. Rebuilding my 6 year-old OS would be a really freakin' ?!!@@!!? process for sure.

I bought Win7 and have a new drive for it but haven't really done much with it yet beside basic installation. I iseth miffed that one can't stretch the taskbar across dual monitors anymore (a non-improvement improvement by MS IMO) for it's basically a programs and files access command center for me.

So I still use my faithful XP for it serves my more limited needs (compared to most of you veteran editors here).
Soniclight wrote on 3/23/2011, 7:59 AM
Oh, and last...

I also think the problem may have been entwined with a dgx. Nvidia driver corruption issue. Started to get blue-screen-of-death occurrences even when not in Vegas. Maybe Vegas and nVidia had some under-the-hood marital spat of some sort, so I've also upgraded and reinstalled the video card drivers.

In process of long re-render right now.
So far, so good.

That said, it's sometimes hard to know what gltich causes what other glitch.