Vidoe Error

[Drake264]

I'm not even finished, I just wanted to get started on post production of my vid early. Know what I would have to deal with and get it out of the way. I rendered a video from Sony Vegas 8, and for some reason despite playing normally in VLC Virtual Dub gives me the error.

May be corrupt data (error code -100) I have no clue what to do, tried to change the four cc codes. But that didn't work. Can someone help me please. I really want to get this out of the way before I finish the video.

[bobbias]

The error code doesn't help us unless we know what program is giving that error code.
What are you trying to use it in that is saying it might be corrupt?
VDub and VLC were sorta built to be able to open almost every sort of video file out there, damaged or not, so they indicate that it isn't completely hopeless, but that also means that most players won't act the same way they will when you hand them a damaged or weird file.

[Scott Green]

@bobbias:

Virtual Dub gives me the error.

@Drake: Try open the file in Vdub via .avs or...
it could be a codec problem, did you install CCCP

[bobbias]

:/ Whoops. I guess staying up all hours of the day can be a problem once in a while.

While doing a quick google search I saw someone say to try running AuxSetup.exe in the VirtualDub folder.

The VirtualDub website has this to say:

http://www.virtualdub.org/docs_errors.html

"VideoSourceAVI error: unspecified error (-100)"

This error actually means exactly what it says -- unspecified -- but the usual cause of the error is a corrupted frame in your AVI file that the decompression codec rejected. Such errors are particularly apt to happen with MPEG-4 V3 (DivX) files, since those files tend to be transferred across multiple machines, each of which can introduce errors. There is no fix for the problem except to reobtain a clean copy.

[post-it]

:/ Whoops. I guess staying up all hours of the day can be a problem once in a while.

While doing a quick google search I saw someone say to try running AuxSetup.exe in the VirtualDub folder.

The VirtualDub website has this to say:

http://www.virtualdub.org/docs_errors.html

"VideoSourceAVI error: unspecified error (-100)"

This error actually means exactly what it says -- unspecified -- but the usual cause of the error is a corrupted frame in your AVI file that the decompression codec rejected. Such errors are particularly apt to happen with MPEG-4 V3 (DivX) files, since those files tend to be transferred across multiple machines, each of which can introduce errors. There is no fix for the problem except to reobtain a clean copy.

the -100 usually means that the first frame is invalid "not a key frame" .. I can't remember the last time Mpeg-4 V3 had that error but it is quite common on Xvid encodes.
.. simply try using a different Codec and you should be fine ^_^

[Drake264]

I just exported using Sony Vegas 8, automatically encoded the video to the dvsd codec. I have no clue how to convert, I was actually trying to figure that out to no avail last night. Any suggestions, I can't open the file type in AVS or Vdub so I have no way to encode, and I dunno what program to use to convert.

[Drake264]

I have older versions of the program as well, so I was thinking about trying to export using Sony Vegas 7 unless someone else can come up with another solution since this is the first time I've used 8, and also the first time I had this problem with vdub and Avs

[post-it]

then, somehow, your Export Settings have changed! .. is there a "Restore Default" button on the Export Location Panel ? .. most Codec's also have one; a "Restore Defaults Button"

[Drake264]

Not exporting out of VDub, because that's the screen you have up. Exporting from Sony Vegas 8. I'm trying to get the program into AVS and Vdub, not out. I need to figure out either how to change the settings in Vegas, or convert the file in some third party program.

[Drake264]

Okay I finally figured out the issue and it's a little embarrassing since it's a stupid mistake on my part. Vegas was automatically compressing the file, after figuring this out I simply left it uncompressed and the problem was solved.