Sony Vegas 9 Creates Unplayable Video

#1 30 Oct 2010 @ 12:06
I'm working on a video for a game. The clips I'm using are encoded using Xvid with a quantizer of 3. They don't have sound, so I have to add sound in Sony Vegas 9. I want to render the project using the same Xvid format and the same quantizer. When I render the video, the preview window displays "No recompression needed" and Vegas just dubs the audio in and copies the video stream. This is fine, as the compression is no different from the source format. However, when I try to play the file, the image is severely distorted, as if it's not being decoded properly. The video data hasn't changed during rendering, as no recompression took place. This only happens when passing an Xvid stream through the renderer without re-encoding. According the the filesize, the video should be in the file in one piece, but it won't play back correctly, no matter what program I use. It seems a header byte or something is wrong. Is there any way I can fix this? I can upload a sample if needed. Thanks for the help.
AfterDawn Advertisement
#2 31 Oct 2010 @ 20:36
Upload a sample to MediaFire
#3 10 Nov 2010 @ 15:49
Whoops, forgot about this thread. I also noticed that it only happens when reducing the framerate from 59.94fps in the source to 29.97fps after processing for some reason.

http://www.mediafire.com/?uvrbaja2ajba40b
#4 10 Nov 2010 @ 19:12
I can add an audio to the original and change the frame rate without recompressing using VirtualDub, no problem.

It must be a Sony Vegas issue - and I don't have it.

If you post that link over at The VideoHelp site, the hotshots there could probably help.
#5 12 Nov 2010 @ 14:15
This only happens when taking interlaced video, deinterlacing it to Xvid in VirtualDub, then editing and adding sound in Vegas. I just need to figure out how to use Yadif 2x with a 30fps output. Although I can just use Yadif 1x, for some reason the results aren't as good as with 2x.
#6 02 Dec 2010 @ 9:09
Ah, forgot I always color correct the video in Vegas, so it has to re-encode frames. Crisis averted!
This discussion thread has been automatically closed, as it hasn't received any new posts during the last 180 days. This means that you can't post replies or new questions to this discussion thread.

If you have something to add to this topic, use this page to post your question or comments to a new discussion thread.

Subscribe to AfterDawn's weekly newsletter.