Yes, I know you may be able to import xvid files into Vegas but there is a very good reason why experienced editors will tell you not to use xvid files.
Xvid uses B-frames and P-frames in addition to I-frames.
I-frames (keyframes) contain all of the picture information.
B-frames and P-frames only contain part of the picture information.
P-frames look at the previous frame to get all the information, and B-frames can use the previous frame as well as the next frame. That means that they rely on I-frames to give you the entire picture.
Now if you cut your clips so that the first and last frames are I-frames you won't run into any problems. The thing is, it's practically impossible to tell if a frame is an I-frame just by looking at the video.
Eventually, you will make a cut that contains no I-frames...and that's when you start losing the work that you've done. Kevmaster can attest to this, and you can
read the thread where everyone warned him about what was going to happen if you're still not convinced.
+ninja mod edit:
If you know how to import a file using DirectShowSource() (it sounds like you do) then it's pretty simple.
-Download ffmpegsource2 from
here
-Unzip, and place the folder "doc" and FFMS2.avsi and ffms2.dll into C:\program files\avisynth 2.5\plugins
-create an avisynth script and use ffvideosource() where you would use directshowsource
-save as a .avs file and open in vdub
so instead of
Code: Select all
directshowsource("C:\documents and settings\someguy\desktop\animu.mkv")
you'd use
Code: Select all
ffvideosource("C:\documents and settings\someguy\desktop\animu.mkv")
the reason you want ffmpegsource2 is that it (should be) frame accurate, whereas directshowsource() isn't. Frame accuracy is kinda important when making clips in vdub.