1.3333 (HDV 1080) "building peaks" Freeze at 86%

farss wrote on 4/17/2008, 5:12 PM

1) Revert to 7.0d
2) Turn OFF Thumbnails and Waveforms under View.

Bob.

JHendrix wrote on 4/17/2008, 5:26 PM

2.) Turn OFF Thumbnails and Waveforms under View.

OK thanks, I did that and now I can drag it in and play it.

It will be a pain to edit without waveform view as there is quite a bit of erratic audio that needs to be split out to different tracks.

1) Revert to 7.0d

Is 7e going to present other issues in this work flow as well?

Are the other issues I mentioned going to go away in 7d, like can I turn on waveform view in 7d?

bruceo wrote on 4/17/2008, 8:08 PM

I had this issue with locking up on peaksquite frequently in V7. V8 solved it and I havent seen it again and we have probably done at least 200+ tapes since then. Right now the only MAJOR problem we are having is with the m2ts from the DR60 and new CF recorder

Laurence wrote on 4/17/2008, 8:25 PM

I used to get lockups during waveform draws all the time. I finally figured out that it was errors in the clips that were acquired during capture. Now I'm a lot more careful to turn off background processes like virus checkers and adware blockers during hdv captures. Since I started doing this I've had no problems whatsoever.

What I would recommend is that you recapture the tape. Before you do though, turn off your virus checker, hit control-alt-delete and turn off any unneccessary background processes there as well. You may think you're getting good captures and your capture utility might be telling you that you got no dropped frames, but there are mpeg format errors that will creep into your clips if your CPU has to do anything else while you capture.

I always capture with HDVSplit and keep the preview function turned off when I capture. I believe this helps too.

I have had not one single error since I started doing this in maybe seven tapes. Before I would get at least one Vegas crashing clip per tape, sometimes two or three.

JJKizak wrote on 4/18/2008, 5:45 AM

Perhaps Vegas capture should freeze all applications and processes as it does during renders. Could solve a lot of anomolies.
JJK

John_Cline wrote on 4/18/2008, 8:48 AM

Run the clip through a freeware program called "mpeg2repair"

http://www.videohelp.com/tools/mpeg2repair

Laurence wrote on 4/18/2008, 8:56 AM

I have fixed problematic m2t clips with mpeg2repair, womble mpegVCR and MPEG Wizard. What I find is that although they don't crash anymore they aren't really fixed.

The problem is that while a tool like mpeg2repair supposedly goes through the mpeg file and repairs errors, that the real reason it works with Vegas is that it changes which playback codec Vegas uses to playback the clip.

This has two problems: First, the preview is much less smooth. Second and worse, is that if you try to smart-render this fixed clip into a bigger m2t clip, it will usually crash in the new render at the same problem spot. This is because it is folded into the new m2t clip and played back with the original codec since the common header is the newer Vegas m2t playback codec.

Because of this, if I have to fix a problem clip, I render it into Cineform rather than use mpeg2repair or a similar tool.

JHendrix wrote on 4/18/2008, 11:31 AM

thanks for all the tips!

anyone know if 7D is the way to go for issues other than this one if working with HDV is it the best bet?

cazeaux wrote on 5/2/2008, 11:36 AM

I had many issues with Canon HV20 and HDVSPLIT (crash when showing to many pictures and freeze when rendering when project to large i.e. above 10-15 files)
Mpegrepair didn't improve anything.

Last weekend, I used the internal Vegas capture, I replaced the vegas m2T file names whith the one issued with HDVSPLIT AND .... everything when fine with pictures and rendering
This quite a funny problem. I am still using my old Ulead media pro 8 and there are no issues using HDVSPLIT. Ulead translate m2T into mpg2 files. EVen the translated files do not work with vegas.

It seems that vegas is not tolerant to foreign captures..

Hope it will help

Laurence wrote on 5/2/2008, 11:44 AM

If you look around you'll find numerous posts accross several forums about this problem. You'll also find conflicting solutions. For example some people will get these crashes when they capture with HDVSplit but not the Vegas HDV capture. Others, like me get better results with HDVSplit.

For me, the biggest thing is to turn off the virus checker and anything else that might be running in the background before capturing. I also turn of the HDVSplit video preview which also seems to help.

Remember that none of these errors will show up as you're capturing. You may get a complete capture with the "No dropped frames" message and think everything is fine when in fact it is not. It is not until you drop the captured HDV clips on a Vegas (or other NLE) timeline that you will run into problems, and because of this, many people have assumed that the problem is something else rather than errors that were introduced when they captured the video from tape.

bruceo wrote on 5/6/2008, 10:13 PM

Your lockups during peak building with HDV will go away when you upgrade to V8
We used to have lots of problems on our machines with HDV on V7

V8 is fine with full captures from tape, but pretty much fails consistently with the new CF recorder m2t files. Horrible crashes. Also rendering an HDV timeline to Mpeg will cause black frames in the rendered output because of some sort of memory issue. However I found a temp workaround by slectively prerendering the timeline, which actually renders the project as a ton of small mpeg files. Then when you render the full file there is no memory issue because it is basically stitching the small files together instead of a big render. I usually just let DVDA do my conversions to SDmpeg but it literally takes 8-10 hours to do 2 hours of HDV. So when I am on a time crunch I can do it off the Vegas timeline MUCH faster, but selectively prerendering does add unnecessary time.

I have put in tickets on these problems with no answer from SCS. Hopefully their lack of support is because they are busy fixing these horrible issues.