Glad to see there is some interest in my program.
I'm not sure if I can go into much detail regarding 169time errors because I signed an NDA with them while helping to debug their new software. But I can explain the mpeg2repair error logs in more detail so maybe you can reach your own conclusions.
Most errors are accompanied by an MBA (Macroblock address) and/or Slice number. An mpeg2 picture is made up of 16x16 pixel squares called macroblocks. Macroblocks are then grouped into horizontal strips/slices that cover a single row of the picture. For satellite, there seems to always be a single slice per macroblock row, but for OTA you often have 2-3 slices per row. To give some real-world examples, here's how things look for a typical 1920x1080i Dish satellite file:
1) Picture is made of 68 slices. Slice number 1 is follow by slice 2 below it, etc. Each horizontal slice contains 120 Macroblocks of 16x16 pixels each for a total of 1920x16 pixels. If you add up the slices, you will see they cover 1920x1088 total pixels. Because the macroblocks must be a multiple of 16 pixels, there is an unused 8 pixels at the bottom of the picture. On some players, it's visible as a small gray border at the bottom of the image.
2) To convert an MBA address to a pixel location, use this formula:
x = 16*(MBA%120); - here '%' stands for mod operator (remainder of a division)
y = 16*(MBA/120); - here you divide and drop the remainder.
For example, MBA=8155, would mean you have an error in a 16x16 macroblock where the top/left pixel is at 1840,1072. Maybe you can find something interesting by looking at the picture locations of 169time errors.
When my tool repairs a file, it basically plays the entire file just like a software mpeg2 decoder would. This allows it to catch all errors in the video steam but makes the process very slow, especially for high resolution, high bitrate files. When the mpeg2 decoder finds a macroblock that it can't decode, it overwrites it with a solid-colored black macroblock. If there are more macroblocks until the next slice, it either skips them (leaving behind whatever was there from the previous frame) or also replaces them with black macroblocks. Skipping is never allowed in I-Pictures so repaired errors on those will show up as black horizontal lines.
A proper mpeg2 decoder (like the JVC 30K) will do the above automatically while playing your file (so repair is not needed). I wrote this tool because most PC decoders designed for DVD playback simply can't cope with errors. They will either crash or skip the entire frame(s) causing noticeable pauses during playback. Due to the way MPEG2 is defined, it's pretty much impossible to really fix errors. Best you can do is try to recover from them. I chose to use black macroblocks to mask the errors because they seemed least noticeable to me (especially when they occur near the black border of the screen). There's other repair options which I may explore in the future (borrowing macroblocks from previous frames, etc.).
You may also like to know that the program does continuity checks on both video and audio packets. So you may skip running the EC utility if you like. If you're recording from cable, it also has the advantage of doing continuity checks in a way that won't report false errors like TSReader, etc.