you may also want to check that the hard drive you are rendering to is ntfs format and not fat32.

L.t.

Thanks for your reply Laurence. So if the HDV media in the timeline has errors what do I do to find the errors and how do I fix it.

Thanks.

I would think that would be at the 20 minute mark, but with the generated temporary files, maybe it is the 10 minute mark.

Yeah, make sure your working hard disc is formated NTFS. If it is an external drive and you didn't reformat it, it is almost certain that it is FAT32. They usually come that way so that they have broad compatibility with Macs and older Windows systems.

Thanks for your reply LongTallTezan. Yes, my Western Digital TB external Harddrive is Formatted as NTFS. What elso could be the problem. I know it's not a compatibility situation because it is rendering but for only 10 minutes at a time.

Thanks.

As a test, use the same render template you have been using but cut out the 10 minute to 10.30 portion of the timeline and see if it will continue to encode past 10 minutes.

You could also try other footage (another project) to see if it will work for longer than 10 minutes.

Another idea would be to encode to Cineform Avi as you can keep the footage up to the point where it stops rendering and replace that portion of your timeline with the cineform avi. Of course, that doesn't get rid of the problem footage or error but it does save you from having to render 9 minutes and 59 seconds worth of footage again. If it is a bad clip, Laurence (I think) has recommended a gop fix in the past but I don't remember what it was- maybe Womble? I am sure he will let you know.

j razz

If it is an HDV clip with errors, what you will find is that the render gets up to the part of the clip where there is an error and stop right there, likely crashing at that point.

What I do then is to render the clip into Cineform using the HDLink utility which is a part of the Cineform NeoHDV program, but that is a paid program which costs a couple of hundred dollars. It is well worth it, but not everyone wants to spend this money.

What most people do in this case is to fix it using Mpeg2Repar which you can download http://www.videohelp.com/tools/MPEG2Repairhere.[/link] This will get you up and running again with one caveat. That is that if you smart-render the repaired clip into an m2t master, the error will surface again in the smart-rendered master (which is why I fix it by rendering into Cineform instead of with Mpeg2Repair)

If this is indeed your problem (and I strongly suspect that it is), where you acquired this error is when you captured the HDV from tape. There are two ways to capture HDV from tape. One is to use Vegas's HDV capture function, the other is to use a free program called http://strony.aster.pl/paviko/hdvsplit.htmHDVSplit[/link]. People on this forum are quite divided about which option is better (HDVSPlit or Vegas's capture). For me HDVSplit works better, but there are quite a few people here who get better results with the Vegas capture. I suggest you try both and see which gives you better results.

Now here is the really important thing: When you capture HDV, you really should really turn of f your virus protection first. Hitting control/alt/delete and cancelling any other background processes you don't need during capture is also a good idea. I used to get an average of about one of these errors per tape. Sometimes I would get two or three on a tape, and other times I wouldn't get any, but I would get them often enough that it was a real problem. Knock on wood, but I haven't had one single bad captured HDV clip since I started turning the virus protection off during capture. IMHO it is really important to do this. You will find that a number of people here don't even use virus protection at all on their editing systems. I can't afford a separate computer just for editing, so for me this really isn't an option.


By the way, if you re-captured the tape with the problem clip, the chances are it would be fine on the recapture.

This is a major problem with Vegas right now and has been since version 7e. Vegas 7d has more robust error correction which unfortunately is at the expense of video previewing efficiency. But for many here, this is a worthwhile tradeoff, especially if you have a really fast quad-core that can blaze through projects with our without the extra efficiency of the newer versions.

Are you trying to use 32bit mode? Vegas almost almost always shuts down when I try to render in 32bit.

32bit mode is for all practical purposes, hopelessly broken. The fact he's making it to the ten minute mark makes me suspect however that he isn't using this mode. Plus rendering ten minutes of HDV video would take something like six hours (on my system at least). The fact that he hasn't complained about extraordinary render times also makes me think that he's using a plain old 8 bit render.