Currupt .MTS File [ Working And on Working Attached ]

[Amarbir[CDR-Labs]]

Hello Friends ,
I got one case where the customer is able to play His .MTS Files Till Serial No 0052.MTS No File After That Works .I have examined the And i See Differences ,But i am Not Sure Why Patient File From Serial No 0053.MTS Till End Are Not Working .Both Working and Non Working Files Are Attached

Working File -> https://drive.google.com/file/d/0B_ZE6- ... sp=sharing
Non Working File -> https://drive.google.com/file/d/0B_ZE6- ... sp=sharing

[jermy]

it looks to me a partial file

[Amarbir[CDR-Labs]]

it looks to me a partial file

Jermy ,
The Customer Says He Copied All The Data To This Folder And Then Only Files Till 0052.mts works not the once after this and they have formateed and overwritten the card they used for the shot .I could see some differences in the headers of both .Is there a link or something that describes the Header of The .MTS files

[hdd_sand]

it looks to me a partial file

Jermy ,
The Customer Says He Copied All The Data To This Folder And Then Only Files Till 0052.mts works not the once after this and they have formateed and overwritten the card they used for the shot .I could see some differences in the headers of both .Is there a link or something that describes the Header of The .MTS files

Amarbir, looking at the first sector of both files 00048.MTS has the correct header and meta data, 00053.MTS to me seems it was overwritten because no correct header for MTS and no metadata.
The header I search when looking for MTS is as follow

\x00\x00\x00\9C\x47\x40\x00\x10\x00\x00\xB0\x11\x00\x00\xC1\x00

*****************
MTS is a file extension for an AVCHD (Advanced Video Coding High Definition) video clip format for high-definition video.
The MTS file format supports 1080i (a high definition video format with 1080 horizontal scan lines, interlaced) and 720p (720 horizontal scan lines, progressive scan, rather than interlaced) in a relatively small file size.
AVCHD video files can be burned to Blu-ray discs and played in compatible devices. Sony and some Panasonic video cameras have software to open and edit MTS files. Other players convert the files. AVCHD files are based on the MPEG 4 codec.
Programs that can open MTS files include Roxio Popcorn and Creator, Flash CS5, and various Cyberlink players.


Good luck

Attachments

[rogfanther]

Seems like the valid bytes in the 53 file had the value of 22 added to them ? I didn´t try with all of them, neither wrote a script , but it seems that subtracting 22 from the non-FF bytes their values would be similar to what I believe to be the header of the other file

[fzabkar]

Seems like the valid bytes in the 53 file had the value of 22 added to them ? I didn´t try with all of them, neither wrote a script , but it seems that subtracting 22 from the non-FF bytes their values would be similar to what I believe to be the header of the other file

It looks more like the data were OR-ed with 0x22, for the most part. Perhaps that's a symptom of stuck bits?

[fzabkar]

ISTM that, for the most part, the corruption is consistent with a stuck data bit in a memory card operating in 4-bit (nibble) mode.

[fzabkar]

Why not take the damaged file and OR it with 0x22? Then compare the output with the damaged file. If there is a consistently stuck bit, then the two files should be identical.

[pepe]

I vote for stuck bit too. Which is pretty bad, because u can't just clear those bits everywhere for obvious reasons.
I guess the problem might have been caused by bad contact between camera and card.
I can't see a solution for such corruption.

[fzabkar]

One could visually compare the good and bad files by performing bitwise Boolean operations on them.

Here is a trialware hex editor that has some nice features:

http://www.flexhex.com/docs/help/editing/bitwise.phtml

I would AND the files with 0x22. The good file will then consist of 0x00, 0x02, 0x20 and 0x22. The bad file (with the stuck bits) will be filled with 0x22.

Now XOR the files with 0x22. The good file will still consist of 0x00, 0x02, 0x20 and 0x22, but the bad file will now be zero filled.

To confirm that the bad file is full of zeros, compute a 32-bit checksum over its contents.