Description
Hi - I'm currently working with HDV rips using DVHScap as the capture tool. This creates mpeg transport streams, and decoding the file with ffmpeg is an amazing way of being told where glitches are. However - using the ffmprovisr recipe - https://amiaopensource.github.io/ffmprovisr/index.html#check_decoder_errors , it's pretty difficult to find the timestamps for the errors, so I've found that adding -loglevel debug -report is really useful ,as the -report gives you a text log file in your current working directory, and -loglevel debug logs at the appropriate level to catch these errors.
For example this is a snippet from the text logfile gives you a rough area (00:30:51.44) to check in a video player and you can see where the glitch is:
frame=46281 fps=369 q=-0.0 size=N/A time=00:30:51.44 bitrate=N/A speed=14.8x
[mpegts @ 00000225457b34c0] Continuity check failed for pid 31 expected 10 got 5
[mpegts @ 00000225457b34c0] Continuity check failed for pid 0 expected 8 got 5
[mpegts @ 00000225457b34c0] Continuity check failed for pid 129 expected 7 got 4
[mpegts @ 00000225457b34c0] Continuity check failed for pid 2065 expected 8 got 0
[mpegts @ 00000225457b34c0] Continuity check failed for pid 2069 expected 6 got 0
[mpegts @ 00000225457b34c0] Continuity check failed for pid 2068 expected 13 got 11
[mpegts @ 00000225457b34c0] Continuity check failed for pid 2064 expected 12 got 5
[mpegts @ 00000225457b34c0] Packet corrupt (stream = 0, dts = 166788000).
[mpeg2video @ 00000225457ba080] ac-tex damaged at 8 3
[mpeg2video @ 00000225457ba080] Warning MVs not available
[mpeg2video @ 00000225457ba080] concealing 5850 DC, 5850 AC, 5850 MV errors in I frame
C:\Users\kieran.oleary\Downloads\wwwspecialistav-a49d80\MV8805\MV8805.m2t: corrupt decoded frame in stream 0
frame=46442 fps=369 q=-0.0 size=N/A time=00:30:58.80 bitrate=N/A speed=14.8x
What do ye think - anyone have similar experiences or ways to refine this?
Activity