No one can solve this...

KatKat wrote on 2/9/2003, 2:40 AM
I hate to post this again, but I can't seem to get the answer to this problem. No response from tech support at SoFo either. Thanks to all that have replied, but I am still dead in the water on this project! This has got to be something simple and I just can't figure it out.

Again - I put a clip on the timeline, I click and drag at the top of the timeline to select a small portion of it to render out to a new file then delete the original file to save space. This works fine. Then I do the exact same thing - boing! It doesn't work. I get the progress box showing the estimated and elapsed time running, but progress stays at 0% no matter how long I wait. Clicking cancel hangs up the program completely and I have to ctl-alt-del to shut Vegas down.

I need to do this hundreds of times for the video I'm making. It's so sporatic - it will work one or 5 times then not. It will not work a bunch of times, then start working again. It's driving me crazy! I'm doing the same thing - click and drag a section, file- render as- name it- OK- poof- program hangs up.

I have P4-2.8ghz, 1gb ram, XP Home, VV3.0c, amd a headache.
I've shut down all background programs, reinstalled the 3.0c update, checked and tried changing a bunch of settings, (which was stupid because it works half the time). My clips have audio too - someone said it might be that. I'm starting with regular DV and rendering to the same at best setting. Each time it hangs up, it makes a 129kb file with the name I gave it which doesn't play. It's the darndest thing....Someone please help!!

Comments

Spirit wrote on 2/9/2003, 3:15 AM
How about bad RAM ? Do you get any other odd errors with any other apps ?
Erk wrote on 2/9/2003, 3:27 AM
Katkat,

You've probably tried, but do you have any problems with other methods of rendering out portions of your timeline? Can you do something simple like putting a single short clip on the timeline, and rendering it out to DV?

I'm also wondering if you've got problems in other apps. Was Vegas ever working correctly?

Here's something else: since you've got XP, try rendering a file in Windows Movie Maker. That might help narrow it down.

Then maybe its time to think about your RAM as was suggested or weird stuff like video drivers etc.

Good luck.

G
TorS wrote on 2/9/2003, 5:11 AM
Here's a wild guess.
Try this: Do not click and drag. Put proper markers on the timeline (press m at the start and end of your clips). Doubleclick above the track to select the loop region. Render with "Render loop region only" selected.
Repeat the procedure for the next clip, and the next ...

The assumption is that your rendering process seems OK because it works once. There might be something fishy in your selection process, or the way Vegas interprets it. Changing the way you go about it may possibly make a difference.

Another thing you can do - especially if you take many clips out from the same footage - do an edit. Cut away the parts you don't want, stitch the whole thing up and save the veg with media. Be aware though, that the audio clips are not saved individually in this process.

A third thing came to mind: Open the master footage in Trimmer, mark out the first clip and drag it to the timeline. Then you can select and render the whole project, delete it (or save it iff you will) and repeat the process for the second clip etc.

Tor
AlexB wrote on 2/9/2003, 5:21 AM
Katkat
when your vegas freezes, is the rest of the computer still alive? Have a look at the system monitor in task manager, you might be able to see what your computer does instead of rendering. Have you considered a thermic or voltage problem? The P4 2,8 needs a lot of energy and gets pretty hot at 100%, if not sufficiently cooled it switches off to survive. The 12V supply is essential, if lots of HDs and other gear in the computer bring it down below 10,5V CPU freezes.
Hope it helps
A.
KatKat wrote on 2/9/2003, 1:15 PM
Thanks at least for the replies. This fourum is a great resourse.

When vegas hangs up, the rest of the computer is fine. In fact, I can restart vegas right then without restarting the computer and the 'render to' will work, once or five times whatever then fail again, or maybe fail immediately. Ctl-alt-del shows only vegas running and cpu usage comes on as 8% or 10% and quickly drops and stays at 2%-4%. I can render whole projects with multiple tracks etc just fine. It's just this render selection thing that keeps hanging up.

I've been using vegas since April and it's worked flawlessly. In fact, this problem has only showed up since I downloaded the v4 demo. I can't imagine that being a problem, plus I've already uninstalled v4 trying to fix this.

Ironically, I tried doing these renders in v4 demo and it didn't hang up like v3, but then I got a whole different error. It would render the file, but then when I move to a different portion of the big file to renderout a small section, it wouldn't play. I mean I hit play and it wouldn't advance, wouldn't play, and gave me an error. I think the problem is connected somehow, but I don't know how.

I've tried most of these other suggestions but no help. It doesn't seem to matter how the portion is selected. But even at that, a bad or wrong selection shouldn't hang the whole program up. I hope someone can shed some light on this.

Mark
DataMeister wrote on 2/9/2003, 10:41 PM
Wow! This is a strange one.

JBJones