Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Compression Techniques Fixing damage to .mts files

  • Fixing damage to .mts files

    Posted by Paul Levering on January 23, 2018 at 9:20 pm

    I have a ton of card backups for the Panasonic AF100 (SD) and Canon C300 (CF) that were damaged by a faulty memory buffer in a Drobo storage drive.

    The footage can still be accessed, played back, edited (occasional crashing), but will have intermittent visual glitches like the example below.

    These last a couple of frames and always occur randomly throughout clips. Searching the net for video repair software offers a minefield of malware, I was curious if there was something trustworthy I could turn to.

    We have run an error check through FFMPEG with the following results –

    [h264 @ 0x7fe6c0007a00] left block unavailable for requested intra mode
    [h264 @ 0x7fe6c0007a00] error while decoding MB 0 48, bytestream 3116
    [h264 @ 0x7fe6c0073800] left block unavailable for requested intra mode
    [h264 @ 0x7fe6c0073800] error while decoding MB 0 21, bytestream 41670
    [h264 @ 0x7fe6c0073800] top block unavailable for requested intra mode -1
    [h264 @ 0x7fe6c0073800] error while decoding MB 64 0, bytestream 74417
    [h264 @ 0x7fe6c0009200] top block unavailable for requested intra mode -1
    [h264 @ 0x7fe6c0009200] error while decoding MB 68 0, bytestream 74175
    [h264 @ 0x7fe6c0009200] left block unavailable for requested intra4x4 mode -1
    [h264 @ 0x7fe6c0009200] error while decoding MB 0 67, bytestream 12608
    [h264 @ 0x7fe6c0008000] top block unavailable for requested intra mode
    [h264 @ 0x7fe6c0008000] error while decoding MB 56 17, bytestream 7824
    [h264 @ 0x7fe6c0009200] left block unavailable for requested intra mode
    [h264 @ 0x7fe6c0009200] error while decoding MB 0 14, bytestream 19459
    [h264 @ 0x7fe6c0073800] top block unavailable for requested intra mode -1
    [h264 @ 0x7fe6c0073800] error while decoding MB 87 34, bytestream 108781
    [h264 @ 0x7fe6c0073800] left block unavailable for requested intra mode
    [h264 @ 0x7fe6c0073800] error while decoding MB 0 8, bytestream 60634
    [h264 @ 0x7fe6c0073800] left block unavailable for requested intra4x4 mode -1
    [h264 @ 0x7fe6c0073800] error while decoding MB 0 20, bytestream 90784
    [h264 @ 0x7fe6c0073800] left block unavailable for requested intra4x4 mode -1
    [h264 @ 0x7fe6c0073800] error while decoding MB 0 51, bytestream 495
    [h264 @ 0x7fe6c0007a00] left block unavailable for requested intra mode
    [h264 @ 0x7fe6c0007a00] error while decoding MB 0 41, bytestream 37314
    [pcm_bluray @ 0x7fe6c0002c00] PCM packet too small
    Error while decoding stream #0:1: Invalid data found when processing input

    Martin Belleau replied 8 years, 3 months ago 3 Members · 5 Replies
  • 5 Replies
  • Craig Seeman

    January 23, 2018 at 11:15 pm

    Aeorquartet specializes in repairing various camera card files

    DVCProHD on P2 cards for example.

    They have a free Mac based utility that will check the files for reparability and then charge a fee for service based the repair.

  • Paul Levering

    January 24, 2018 at 12:47 am

    Paths like this are what i’m afraid of. I have literally days of footage that is damaged, it would cost a fortune. I may be too hopeful to think a tool exists to fix the issue.

  • Craig Seeman

    January 24, 2018 at 3:46 am

    There’s stuff like this.

    But I wouldn’t trust it. Perhaps you can copy the file and test with a copy using their free trial.
    Programs like that might just fix simple EOF issues. File damage can be very complex though.
    Companies like Aeroquartet find patterns in the problem and implement repair based on the patterns of damage found. Alas if there were cheap good and reliable methods than companies like Aeorquartet wouldn’t be able to survive.

  • Craig Seeman

    January 24, 2018 at 3:47 am

    There’s stuff like Wonder Share
    Their reputation is shady enough that COW prevents me from including the link.

    But I wouldn’t trust it. Perhaps you can copy the file and test with a copy using their free trial.
    Programs like that might just fix simple EOF issues. File damage can be very complex though.
    Companies like Aeroquartet find patterns in the problem and implement repair based on the patterns of damage found. Alas if there were cheap good and reliable methods than companies like Aeorquartet wouldn’t be able to survive.

  • Martin Belleau

    February 1, 2018 at 6:41 am

    Sounds like it’s long GOP encoding since many frames in a row look bad. If it’s I-frame only encoding, a tool could just re-use the previous good frame so you get a freeze frame instead of a bad frame. If you could upload a short sample somewhere I could confirm if it’s long GOP or I-frame encoding.

    Have you been able to find anything that helps?

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy