Rendering Issues

[Chris Young]

Need more than that Ii am afraid. What is your source format/s? What format are you trying to render to? What PC processor power/speed are you using and how much ram does it have. The more info you can supply the more people can suggest possible solutions.

Chris Young
CYV Productions
Sydney

[Chelsea Volz]

All of the clips are in .avi or .wmv format.
I’m trying to render to a wmv format.

These are the specs I got from the system part of the “computer” tab:

Processor: Intel Core 2 Duo T5250 @ 1.50 GHz
RAM: 2038
And I’m operating on a 32 bit system with Windows Vista Home Premium.

And, I’m not sure if this matters but all of my projects get saved onto an external hard drive.

[Chris Young]

Hmm! 2 Gig of ram is right on the borderline of functionality. Vista 32 requires the best part of a gig to run correctly. I would suggest running out of ram could be one of the issues. The first one I would be looking at.

When you do a render open Task Manager (Ctrl, Alt, Delete) and watch under the Performance tab to see if running out of ram is an issue. If it is and seeing that you get to around about 70% through before it falls over try this work-around.

Create a timeline selection for about 65% or less of the timeline duration and render out a DV avi, that’s if DV is suitable for your needs, let’s call it Segment #1. Then render out the remaining timeline section as Segment #2.

Now on a new timeline put the two segments together and you will probably be able to get to a 100% WMV render. In your case the WMV files you are creating shouldn’t be too ram hungry so you might be okay.

Re the drives. Again a single USB drive is a bit marginal. A good option is to go with a dedicated video Raid configuration. Not that this suggestion is much help to you at the moment but it’s worth aiming to go that way if you will be doing a lot of editing in the future.

Actually there is one thing you could try before tackling the above. Try rendering out a short segment of the timeline. An area from 60~65% of the timeline to 75~80% of the timeline. If that falls over during a render you may have a corrupt file or image on the timeline in that vicinity. If it does fall over due to a corrupt file then it requires a bit of detective work to weed it out or fix it.

Chris Young
CYV Productions
Sydney

[Chelsea Volz]

Thanks for the response! 🙂

I’m definitely beginning to think that’s its a corrupted clip. In fact, it stops at a specific clip every single time and won’t go past it.
I’m not sure how it was corrupted though because it was ripped just like all of the other clips I’m using and it’s the same file type, etc. I’m quite confused, but I’m almost positive that it’s that clip that is causing the issues.

Any information I can give that could possibly solve this issue? 🙂

Thanks, again! 🙂

[Mike Kujbida]

What kind of clip is it?
File format, size?

[Chelsea Volz]

Alright, so I don’t think that that clip was the issue anymore. I replaced it with a different version of the clip (the one I was using before was a .wmv format and ripped from a DVD. It is 78.4 MB. This new one is also a .wmv format but it was downloaded from the internet. It is 90.8 MB.) Anyway, after I replaced the clip and tried rendering it again, it froze right around the same spot.
I just tried rendering the rest of the project right after that clip, but it froze and shut down at 3%. Then I went forward one more clip and tried rendering again and I got this message:

Error.
Process ID = 0x4dc (1244)
Threat ID = 0x-04(3844)
Program must be terminated.

There are 5 clips after the one that I originally thought was the issue.
They are all in .wmv format and are all around the same size as the other clip. All except for one were ripped from DVDs.

All of the clips show up in the timeline and they all also play on external VLC Player, Windows Media Player and BSPlayer.

Any ideas?

[Chris Young]

Process ID = 0x4dc (1244). This rings a bell in the back of my memory. I think this is a .Net Framework related ID. Believe me there are a number of issues related to later versions of .Net under Vista. Been there myself.

There is a possible .Net fix but before going down that bumpy road try and do the following.

Create a new Vegas project and load the half dozen or so files that appear to be causing the problem. Edit them the way you want them and try rendering them out as say DV files. This may work and give you files to use in your problem project by replacing the suspect WMVs with the DV versions.

See how you go.

Chris Young
CYV Productions
Sydney