Vegas 9 REFUSES to recognize a 3

Robert Gould · November 20th, 2009, 03:37 PM

Wow, this is a disturbing one.

As I said in another thread, I recently reformatted my drive, put all my files back on it and upgraded from Vegas 7 to Vegas 9.

So far, everything's been pretty good. All my video files were preserved on backup. I've opened all of my important .VEG files, and had good luck rendering out AVIs and MPEGs using all the .veg files created in Vegas 7 and hdv ingested with 7.

HOWEVER, there is one patch of video, literally 4 minutes within a larger chunk of HDV, that Vegas 9 will NOT recognize. Onscreen it shows half an image, with the bottom half a big GREEN blank. A big chunk of sound in that section is also missing.

First I thought, "Okay, this file just must have gotten corrupted in the backup and restore process. I'll just re-ingest from the exact same in and out points on the original HDV tape, and then use the Replace function to sub the new footage in on all the timelines."

So I re-ingest it, and as it comes it it looks and sounds PERFECT. Except that when I look at the new file that's been created, nearly the SAME problem occurs -- I get some moving image, except it WILL NOT give me any sound for that 3 - 4 minutes.

Now bear in mind, I have literally over 50 hours of ingested footage on my HDDs, and all of it seems to be working fine, in and out of Vegas 9.

WHY would this one particular chunk of tape (which plays back perfectly fine on the camera and during capture) NOT be recognized by Vegas 9?

Any advice to fix this, or a workaround?

Thanks much for any help, this is driving me nuts.

RG

Robert Gould · November 22nd, 2009, 10:59 AM

Update: I was able to fix this by re-ingesting the video a second time. No idea what caused this bizarre problem, but I have to think it had something to do with corrupted data.

Terry Esslinger · November 23rd, 2009, 12:49 PM

By 'reingesting' do you mean that you 'recaptured' from the original HDV tape?

November 20th, 2009, 03:37 PM	#1
Robert Gould Regular Crew Join Date: Sep 2007 Location: Chicago, IL Posts: 28	Vegas 9 REFUSES to recognize a 3 - 4 minute patch of HDV Wow, this is a disturbing one. As I said in another thread, I recently reformatted my drive, put all my files back on it and upgraded from Vegas 7 to Vegas 9. So far, everything's been pretty good. All my video files were preserved on backup. I've opened all of my important .VEG files, and had good luck rendering out AVIs and MPEGs using all the .veg files created in Vegas 7 and hdv ingested with 7. HOWEVER, there is one patch of video, literally 4 minutes within a larger chunk of HDV, that Vegas 9 will NOT recognize. Onscreen it shows half an image, with the bottom half a big GREEN blank. A big chunk of sound in that section is also missing. First I thought, "Okay, this file just must have gotten corrupted in the backup and restore process. I'll just re-ingest from the exact same in and out points on the original HDV tape, and then use the Replace function to sub the new footage in on all the timelines." So I re-ingest it, and as it comes it it looks and sounds PERFECT. Except that when I look at the new file that's been created, nearly the SAME problem occurs -- I get some moving image, except it WILL NOT give me any sound for that 3 - 4 minutes. Now bear in mind, I have literally over 50 hours of ingested footage on my HDDs, and all of it seems to be working fine, in and out of Vegas 9. WHY would this one particular chunk of tape (which plays back perfectly fine on the camera and during capture) NOT be recognized by Vegas 9? Any advice to fix this, or a workaround? Thanks much for any help, this is driving me nuts. RG

November 23rd, 2009, 12:49 PM	#3
Terry Esslinger Major Player Join Date: Oct 2002 Location: Sacramento, Elk Grove. Calif Posts: 306	By 'reingesting' do you mean that you 'recaptured' from the original HDV tape? __________________ Puttin the wet stuff on the red stuff!

November 22nd, 2009, 10:59 AM	#2
Robert Gould Regular Crew Join Date: Sep 2007 Location: Chicago, IL Posts: 28	Update: I was able to fix this by re-ingesting the video a second time. No idea what caused this bizarre problem, but I have to think it had something to do with corrupted data.