• VEGAS Pro

  Encoding corrupt. Stops at 96%. Need way to identify or eliminate corrupt footage.

  Posted by Odd Mathisen on January 30, 2013 at 8:19 am

  Hello!

  I’ve been having a problem with my video pipeline recently.
  So far I have tried a few things which didn’t work out.

  Before I go about rambling let’s take things from the start.

  I create video captured in games, using a program called DXtory.
  This program give me high quality source footage, at the cost of immense disk space – using the XTOR codec.
  At times there are “hickups” and a few frames are dropped/lost in the source feed.
  This isn’t a problem when viewing the source material – It just shows the last rendered frame and keeps that in view until a new non-corrupt frame is found.

  When editing this in Vegas the same can be seen. Whenever the feed gets corrupt, the previous non-corrupt frame is shown until it recovers.

  The problem occurs when I try to encode the completed film.
  I have tried SONY AVC(MP4), Main Concept AVC(MP4) and Windows Media Video 9(WMV).
  For SONY AVC and WMV the render goes all the way to 96%, then the progress stops.
  A 30 minute video took approximately 1 hour to get to 96% then another 8 hours without any progress.
  For MC AVC the video renders the first 3 minutes, but the progress is still stuck on 0%(this was only attempted once – so it might be a random error).

  What I am looking for is either:
  1. A way to identify corrupt footage in the source feed without having to look through each segment of the video looking for duplicate frames(meaning one of the frames is corrupt), so that I can edit out those parts manually(a “corruption-highlighter” for the source footage).
  2. Same as above, but instead attempt to “repair” corrupt segments, and actually replace them with a screen of the previous non-corrupt footage.
  3. A way to highlight corrupt segments in Vegas itself. This would be similar to point 1, but done within Vegas itself.

  The source footage is normally anywhere from 1 hour to 4 hours long. Scanning through that manually, looking for duplicate frames, is a tedious task at best.

  A finished movie is anywhere from 15 minutes to 1 hour long. Scanning through that is a whole lot less time consuming.
  I have done it a few times so far, but it normally takes several passes to weed out all the corrupt parts.
  I feel there must be something out there that can help mitigate some of the time-sink.

  I have tried running various repair utilities on the footage, but since XTOR is a proprietary codec none of the utilities have had any effect(they all say the footage is ok).

  If anyone has had any similar problems earlier any tips and help would be greatly appreciated.

  Odd Mathisen replied 13 years, 7 months ago 1 Member · 0 Replies
• 0 Replies

Reply to this Discussion! Login or Sign Up