Captured footage came out strange


ReneH wrote on 6/5/2010, 1:56 PM

I try both methods and I get repeatable crashes.

I'm thinking that I will uninstall Vegas and einstall? Ill check if there are any leftover files, perhaps delete them before I reinstall?

This is bugging me to no end!
Paul C wrote on 6/5/2010, 2:25 PM
In my otherwise stable 9.0e install it locks up Vegas when I add the file to the timeline, no error message at all - whichever way I match media. However, I can also generate an error message every time when I try to load it into the trimmer, so I don't think reinstalling Vegas will help.

Also, I played the file back in Windows Media Player, where it plays back too fast, but I noticed there are dropouts visible in the clip for a couple of frames at around 8 seconds. I'd suggest the captured file is no good.
Tom Pauncz wrote on 6/5/2010, 2:57 PM
I also get a crash adding file to trimmer. Repeatable.
musicvid10 wrote on 6/5/2010, 3:23 PM
There are possibly corrupt frames at 00:08.13 and 00:08.17, maybe others.
Scenealyzer has a built-in repair utility. It won't fix the dropouts, but it may fix the structure.
ReneH wrote on 6/5/2010, 5:27 PM
Thank you all.

I'm thinking that the footage is perhaps corrupted all around, perhaps the tape was too old. Also, it was very humid and hot outside, about 95 F.

I did let the camera acclimate for about 10 mins prior to use. I'll shoot some more video, perhaps with another tape and see if Vegas can handle it. Also, there were too many drop frames so I'm thinking the video tape was damaged, or tape head needs cleaning.

Thanks for your help, I gave up on the the footage altogether.
ReneH wrote on 6/7/2010, 8:34 PM
Hello! All,

I found the cause of my capture problem!

It was my fault and not Vegas Pro. Apparently, I thought I was being slick when I decided to make some changes in bios which I thought would bring something extra to my computer's performance.

What I did was change the hard drive settings and enabled 32 bit date transfer rates. Like I said, I thought I was being slick and in the process screwed with my system's integrity. I backtracked exactly what I did that could have caused this misery and everythig came together when I disabled 32 bit transfer.

My hard drive's manual says it can do 32 bit transfer but bios said it couldn't. Don't believe every hype these hard drive manufactuers tell you.

Thank you all for assisting me through out this ordeal and I'll keep saying that most of the time, Vegas may not be the contributor of the problem you may be experiencing. Many times, it comes from our own end.