Vegas won't import uncompressed AVI

Matt_Reason wrote on 8/23/2005, 6:40 PM

I have a video file that I captured with an HD deck and when I drop it into Vegas, it only creates an audio track.

Windows media player plays the file fine. I was under the impression that Vegas and WMP used the same core so the incompatibility baffles me.

From a previous post, I read about GSpot... nice app. It says that the codec is YUY2 and no codec is needed to decompress it.

I've played around with the "ignore 3rd party codecc" and the related settings in the options to no avail.

Any help appreciated.

Comments

Coursedesign wrote on 8/23/2005, 8:05 PM
How did you capture the file? SDI through Decklink, or using a different computer even?

The term "uncompressed" is famously abused, what specifically do you think the specs were in this case?

What camera was it shot with?
Matt_Reason wrote on 8/24/2005, 12:35 AM

It was captured with a Sony HDCAM deck using Digital Rapids Stream. The tape is from a studio - orig film but mastered professionally.

By uncompressed, I mean that GSpot said it was simple enough that no decompressor was required. Right clicking the file, the comression says MS-YUV. That codec is on the machine.

Is there a way to direct Vegas to use a particular codec?
B_JM wrote on 8/24/2005, 8:06 AM
you will have to load the file into virtualdub , set it to direct stream copy , and resave the file out ..

this will re-write the headers and vegas should see it (you can do a short test)

you original file is untouched - it only re-writes the headers on the file ..
kentwolf wrote on 8/24/2005, 11:33 AM
This is a huge bug in Vegas 5 that has YET to be fixed.

Vegas 5 will also not accept output from Boris Red 3GL or even AVI out via the MainConcept (not Vegas) DV codec.

Vegas will only take Vegas-rendered DV.

It certainly seems that Sonic Foundry was much more expeditious in issuing program updates.
B_JM wrote on 8/24/2005, 12:49 PM
vegas (all versions) will import main concept render DV files just fine .. it is done all the time..



in almost all cases - it is the fault of the app writing the file - if they do not write proper header data or include meta data

Liam_Vegas wrote on 8/24/2005, 1:22 PM
It strikes me that some clever person could write a utility that will re-write the headers to comply. The direct-stream copy in Virtual-Dub sounds like it is really doing this - but at the added "cost" of needed to copy all the actual frame data to the new file.

Perhaps one oif the video-fx/plugin gurus out there might be asked to see if they can do this?

just an idea.
B_JM wrote on 8/24/2005, 2:00 PM
since it is every frame -- and you have to read and write to every frame - you could not rubber stamp the file ..

you can do it VERY quick with virtualdub but even quicker with avisynth

Liam_Vegas wrote on 8/24/2005, 2:08 PM
Aha... so this "header" data is actually on every frame... not just at the "head" of the AVI file.... I get it now.